Candidate specification
Candidate specificationOperational object

Falsification Receipt.

A signed replay object for challenging, corroborating, and preserving a decision before action.

Falsification Receipt is a public candidate spec. Final wording remains gated on the first external corroboration landing.

What this object isExact role

What this object is.

A Falsification Receipt is the signed replay object used to preserve what a verifier resolved under a declared state, verifier, and policy version.

Why it existsReview-grade

Why it exists.

High-stakes review should not depend on screenshots, prose, or implied trust. A receipt should preserve the decision, the reason path, and enough context for another reviewer to replay or challenge the same outcome.

Core fieldsMinimal top-level object

Core fields.

Identityreceipt_type · receipt_version · mode
Observed outcomeobserved_verdict · observed_reason_code
Binding digestsstate_digest · bundle_digest · dsse_digest
Verifier pathverifier_digest · policy_version
Replay contextreplayed_at · timestamp_ref · transparency_ref
Subjectsubject_uri · signature
ModesChallenge · corroboration · public state

Modes.

  • Challenge receiptA public fixture reproduced HOLD or FAIL under the published verifier path.
  • Corroboration receiptAn independent witness replayed the same signed bundle and recorded whether the verdict matched.
  • Public-state receiptA system-published decision record tied to the current public state.
Minimal verification requirementsNo implied trust

Minimal verification requirements.

A valid Falsification Receipt is only meaningful if the referenced state, verifier, and policy can be independently checked. Pages explain. Signed state decides. Receipts preserve.

Candidate status remains in force until the first witnessed HOLD is publicly archived.