Vouch Receipt Reference

A native differential receipt binds a declared checked rule, input context, lowering/evaluation observations, hashes, and contract version in csk.differential-receipt/v0.

Current guarantees

  • Structural inspection validates schema and recomputable bindings without re-running policy. Signed-envelope authentication additionally checks consumer trust and pinned context, but still does not re-run policy.
  • Native vouch verify --reexecute emits csk.native-reexecution-report/v0: authentication is reported first, then current Native execution under fixed complete-transcript scope, then the current-versus-signed comparison.
  • Native vouch gate --require-decision emits unsigned diagnostic csk.native-gate-report/v0; the report records whether a live grant was minted but is never itself a capability or accepted gate input.
  • Replay compares an explicit corpus and records agree, mismatch, and not-comparable outcomes.
  • Receipt type tags and required fields are disjoint from Bridge-report tags and fields.

Receipt field groups

GroupBinds or recordsDoes not establish
contract/typecsk.differential-receipt/v0 and schema versionfuture-schema compatibility
source/inputexact checked rule and pinned datum bytes/hashescorrectness or completeness of host data conversion
executionlowering/evaluation transcript and observed resultsemantic equivalence outside the checked profile
identitydeclared generator/version and artifact hashesauthenticity, issuer identity, or timestamp truth
verificationschema and recomputable byte bindingshonest generation or policy correctness
authenticationauthorized signature plus exact source, input, profile, and issuer-engine contexthistorical execution, freshness, identity, or honest deployment
native re-executionboth current Native evaluators agree and their complete canonical transcript equals both signed observationsindependent witnessing, authorization, policy correctness, or whole-language equivalence
local decision gatelive re-executed evidence exactly matches one required decision in the current Native invocationtransferable authority, freshness, replay prevention, identity, deployment safety, or permission for an external action

Boundaries

  • Hashes establish byte binding and internal consistency, not authenticity or honest generation. Re-execution agreement does not establish freshness, historical execution, independent witnessing, policy correctness, or whole-language equivalence.