An interactive demonstration of cryptographic separation in prior authorization. The Separation Predicate™ is construction-independent — it can be instantiated using any sound succinct proof system. This demo uses Groth16 on BN254, the most compact and fastest-verifying option currently available. Each determination is accompanied by a certificate proving — to any third party in milliseconds — that the decision was structurally independent of cost features. You will verify a real certificate in your browser, and you will watch an adversarial prover get rejected by the mathematics.
This demo uses Groth16 / BN254. The Separation Predicate™ is construction-independent — PLONK, Halo2, and STARK instantiations are available for deployments requiring transparent or post-quantum setup.
The Separation Predicate™ is construction-independent: any sound succinct proof system (Groth16, PLONK, Halo2, STARKs) can instantiate it. This demo uses Groth16 on BN254 — the smallest proof size and fastest verification currently available. Certificates are produced by a real trusted-setup ceremony and verified in your browser via snarkjs. No backend, no telemetry, no signup.
The verification ran in your browser, with no access to our infrastructure, our model, or the patient record. Anyone holding the public verification key can verify any certificate the system produces. The trust never moves.
Modifying a single byte of the public record invalidates the certificate. A common allegation in prior-authorization litigation — that records were edited after the fact — is structurally refuted: the certificate either verifies on the original record, or it does not.
This is the structural distinction between policy and physics. Policy can be revised under pressure or worked around by a sufficiently motivated insider. The cryptographic constraint cannot. When separation is violated, no witness satisfies the circuit, and no proof can be generated.
The code is open and self-contained. A prospect's engineering team can clone the repository, install the toolchain, and reproduce every claim on their own laptop in under an hour. For a deployment scoping discussion, we are reachable directly.