ChoiceProof Protocol v0.1

Independent verification

Reproduce a result from its evidence and approved verification rules.

Cloud reports and delivery evidence

Export a result from ChoiceProof Cloud and obtain its authenticated offline verifier. The verifier checks report integrity and recomputes the stored conclusion from the bound inputs, approved profile, policy and historical evaluation time. Each report selects its recorded verifier generation.

The connector export checker validates signatures and evidence bindings against the approved profile and recorded evaluation context.

Cloud report verification · Connector export verification

Observation-engine evidence

Each enterprise uses an observation engine configured for its tasks and operating environment. Its checker compares the exported evidence bundle with the task contract, model version and recorded decision context.

Independent checks reproduce observation assessments and recovery results using the engine's versioned evidence formats and application-specific verification procedures.

Explore the observation engine

Technical reference

Current layered verifier

Core verification is deterministic and runs offline on the supplied artifacts. It cross-binds the evidence history and reports each verification dimension separately. Network collection and readback are available as explicit verification steps.

Assertion and correction verification

Recompute evidence and answer commitments, check exact quoted spans and integer arithmetic, validate approved profiles, and replay local corrections. Empirical support assessments remain separate from deterministic results.

Completion certificate verification

Recompute the profile certificate for the admitted nonnegative integer-coordinate model. Validate signatures, profiles and source coverage against the recorded fault and omission budgets.

Semantic binding and dispatch evidence

Derive K from enterprise scope and a stable operation lineage, validate F and binding hashes, and identify retries, conflicts, forks and declared supersessions. A repeated historical fingerprint such as F1 → F2 → F1 remains a conflict.

The enterprise-local guardrail records pre-dispatch evidence, consumes a single-use permit and retains the adapter binding for subsequent readback. Durable storage and fencing preserve the dispatch history across retries and recovery.

Formats and fixed vectors