Implementer guide
Falsification ReceiptCandidate implementer guide

Implementer guide.

Use the candidate object as a replay-grade output of the existing Meridian state, challenge, and corroboration workflow. Keep candidate wording until the first witnessed HOLD is publicly archived.

Open schema See examples Open Verify
Generation pathOperational order

Generation path.

  1. Resolve a decision under a declared state, verifier, and policy version.
  2. Preserve the outcome as a candidate Falsification Receipt with observed verdict, reason code, and digests.
  3. Bind replay context with replay timestamp, timestamp reference, transparency reference, subject URI, and signature envelope.
  4. Archive before latest if the receipt is going to be published as part of a live authority path.
Validation pathNo implied trust

Validation path.

  1. Check schema compliance against the candidate schema.
  2. Confirm referenced state and bundle digests can be independently resolved.
  3. Confirm verifier path and policy version match the declared replay context.
  4. Treat receipts as candidate objects until the first witnessed HOLD is publicly archived.
Release postureCandidate wording

Candidate wording policy.

Use candidate specification, candidate object, public now subject to revision, and finalized after first witnessed HOLD is archived. Avoid any wording that implies stabilized or sector-wide finality before that milestone is live.

Open changelog Open Witness Quorum Import live state