Skip to content
The Instrument

Paradigm.

The instrument we operate on your data. It builds datasets, checks them, and documents what it did. Every claim it makes can be checked with tools we do not maintain.

Why It Exists

Most AI failures are data failures.

Schemas drift. Shards vanish. Teams retrain without knowing exactly which data the model learned from.

None of that arrives as an error. It arrives months later as behaviour nobody can account for, in a system somebody is now being asked to justify. Paradigm makes dataset quality an enforced stage rather than an assumption: a build that fails validation stops, and the refusal is written down.

The Register

Nineteen numbers can reject your data.

19
gating constants in the register. Each carries a verdict: calibrated, backstop, or configuration.

A gate is a constant. Nineteen constants in Paradigm can cause a sample or a build to be rejected, and each one is registered with a verdict: calibrated against a measured gap on a named corpus, placed as a backstop outside everything measured, or plain configuration. Findings that rest on configuration are marked uncalibrated in the report you receive.

None is non-discriminating. When a check was measured and found unable to separate good input from bad, it was demoted rather than kept. And the register polices itself: the build fails when a gate-shaped constant appears in the source without an entry.

Focus thresholds: two calibrated bounds and one global constantGeometry A is sharp from 47.7 upward; geometry B from 108.9 upward. A global threshold at 100.0 would reject sharp frames from A between 47.7 and 100, and pass blurred frames from B between 100 and 108.9.47.7GEOMETRY A108.9GEOMETRY B100.0GLOBAL CONSTANTsharp framesrejectedblurred framespassed

Two corpus geometries derive focus bounds of 47.7 and 108.9. A single global threshold of 100.0 would pass blurred frames from one and reject sharp frames from the other. Thresholds calibrate per geometry, and anything still derived from a global constant says so where you can see it.

Capabilities

What it does.

In the order they are applied

Provenance, layer by layer.

Security

A deployed model can be stopped by revoking a certificate.

Agent trust is mutual TLS against our PKI, so revocation is the kill-switch: no redeploy, and no coordination with whoever is hosting it. The controls beneath are in production rather than on a roadmap, and none of them is interesting until you need the sentence above to be true.

  • Authenticationin production
  • Role-based accessin production
  • Multi-tenant isolationin production
  • Audit trailsin production

Operated, not sold.

Paradigm runs on a control plane that gates every mutation, keeps a hash-chained event log, and composes attestations for each engagement. We operate it and deliver its output. There is no licence, and no version of this you install.

This site does not list release numbers. Every engagement scope pins the exact instrument versions used, and every evidence bundle records them; if you need a version claim, it will be in a document we signed. Next: ARCHON, a sealed execution environment for heavy compute, is in development, alongside transparency-log inclusion proofs and erasure attestations. We ship when it is real.

Paradigm builds, verifies, and documents datasets for regulated AI. In production use on live engagements.

Start an engagement