Protocol specification

ChoiceProof Protocol v0.1

A common foundation for binding execution evidence, checking it against an approved model, and independently reproducing the result.

A shared foundation

The protocol connects tasks, approved rules and execution evidence so results can be checked and traced.

Observation engines use versioned contracts, evidence bundles and application-specific checkers.

Observation engine · Independent verification

Bind the evidence

Connect observations to the expected task, source and verification profile. Canonical hashes and signatures preserve the identity of the records being checked.

Check authenticity and fault tolerance

Validate signatures and evidence relationships. For supported coordinate models, a mathematical certificate establishes the source coverage required to tolerate the approved false-report and omission budgets.

Reproduce the result

Retain the approved profile, evidence and verification result. Independent checks recompute the conclusion from the same artifacts, with the method and reasons recorded alongside it.

Cloud report verification · Research foundations

Verification profiles

Authenticated execution evidence

Receipts, signed checkpoints and inclusion proofs bind execution records. Optional cryptographic transparency, witness observations and signed service registration add independently reported checks. Core layered verification recomputes supplied artifacts locally and offline.

Coordinate completion

The implemented model uses independent nonnegative integer coordinates and fixed whole-source projections. Profile certification checks source coverage against approved false-report and omission budgets. Signed observations are bound to the profile, task, source domain, key, nonce and evaluation window.

This profile reports CONFIRMED or UNRESOLVED. Evidence checks report PASS, FAIL, INDETERMINATE or NOT_PROVIDED for each supplied layer.

Assertion and correction records

Scoped checks bind claims to evidence snapshots. Correction records preserve exact before-and-after hashes and affected spans.

Evidence result fields
FieldChecks
evidenceIntegritySchema, canonical hash and artifact consistency.
signerAuthenticityDeclared signing-key control under the approved policy.
lifecycleCausalLinkageLifecycle transitions and causal references.
sequenceContinuityStream, epoch, sequence and predecessor continuity.
checkpointInclusionEvidence inclusion in ordered checkpoints.
transparencyInclusionCheckpoint inclusion in a signed transparency log.
transparencyConsistencyAppend-only consistency between signed log states.
witnessMonitorAuthorized witness and monitor observations.
equivocationDetectionConflicting signed views in the supplied evidence.
externalFinalitySigned service registration under the selected trust policy.
readbackObservation from the selected result source.
reconciliationComparison of committed expected and observed results.
Formats and interoperability

Use the API contract, schemas and test vectors below to build compatible integrations and verify artifact formats.

Commitment construction

commitment = sha256(domain || canonicalize(privateValue))

Private values remain in the source environment. Canonical hashes bind their commitments to the evidence artifacts.