Dated repository-local command-output evidence captured from the named commit and tree. Reported hashes vary by execution; they are exact fields from this captured payload, not reproducible canonical constants.

Source commit: 5cec88069a5646c188079fab2c701c79b4941f34
Source tree: 7f9808af367d630265b2bb115a9f90d041e661e4
Captured payload bytes: receiz-docs/evidence/slice-6/trust-command-output.v1.json90f04e0d6aa4e29813f0ef54022b8fafdc21b8b1076429def82ae8cff13b44f3
Capture runtime: Node.js v24.15.0; pnpm 10; macOS arm64; repository-local commands

pass

Artifact conformance

sealed artifact

20/20requirements20/20checks0expected failures

20 executable artifact scenarios passed; this suite emitted a schema revision and no conformance hash.

Captured reported hash: No conformance hash emitted; the captured payload SHA-256 binds this result.
Captured reported revision: receiz.artifact_conformance_corpus.v108
Command: pnpm test:v108-artifact-conformance
Exact source: scripts/test_v108_artifact_conformance.ts51bf8686e40fbb0031f6245cff975ca6dcb13614fce2471793a2c723bac7bf65

pass

Economy conformance

proof-native economy

28/28requirements23/23checks0expected failures

28 requirements and 23 checks passed.

Captured reported hash: 0bebce3cc2afc399a879830c756d679f553ff063ea6ea2493f5715ff7f90405d
Captured reported revision: aac54136f7c5d24298847e5a22ea663c27aea2e9d8dfcee1fe3ea25d87988da8
Command: pnpm test:economy-conformance
Exact source: scripts/test_economy_conformance.ts58bbd2f7b5d79dccee1382da2c7719a42db637e4448dc6348efc472494a9d335

pass

Settlement conformance

settlement

28/28requirements23/23checks0expected failures

28 requirements and 23 checks passed.

Captured reported hash: 7d3f251ae34b7b3d02772c45f1ed6e5c5ddb71106956897aad39d1105214e3c1
Captured reported revision: aac54136f7c5d24298847e5a22ea663c27aea2e9d8dfcee1fe3ea25d87988da8
Command: pnpm test:settlement-conformance
Exact source: scripts/test_settlement_conformance.ts021f52595eaaa948337dbe5e01fd4d053a1bab161aea1cad7d053ee1886836ba

pass

Market conformance

market ownership

18/18requirements40/40checks0expected failures

18 requirements and 40 checks passed.

Captured reported hash: a2f89e3453eb6039e27e05689d22454ea04cba25bda49dccf63fcfc624d81a01
Captured reported revision: d97875497950a033a3cf6c04cc6942839fba80c924c3ea2ba476914424c18950
Command: pnpm test:market-conformance
Exact source: scripts/test_market_conformance.ts47c7ebb7eb9f3854f31dbc7266909f9e4c9726908930d236f3a76eaacae54eb7

pass

Identity conformance

identity continuity

26/26requirements47/50checks3expected failures

26 requirements passed. The report records 47 passing checks and 3 expected negative-path failures; overall status is pass.

Captured reported hash: a73eb9b3c12a727a7adfb191b1435734b3404753326a937c9a6af0328599fee1
Captured reported revision: 3dbc424d0d9ad2e49f181f0b5adb166756c9282095ba61abbde60f284a0aed38
Command: pnpm test:identity-conformance
Exact source: scripts/test_identity_conformance.ts699508b94d317a4d1ff1bae527b49e76e3dfda8f7e085316e9729b9afa23e36f

pass

Interoperability conformance

cross-system proof

23/23requirements29/29checks0expected failures

23 requirements and 29 checks passed.

Captured reported hash: 9a372292b2c169b7ef56f7ae57e250bf8be761303dc6f9d86aa7e789289ed827
Captured reported revision: aaf35d2c246f99f68b6a0966679630664c69fc61af2c447c423603687430285c
Command: pnpm test:interoperability-conformance
Exact source: scripts/test_interoperability_conformance.tsc09d81f36305004f7ee02c40070b3c9cd64d8f5572ce12d211c022f3e75dbf4e

pass

Issuance conformance

certificate and note issuance

28/28requirements47/47checks0expected failures

28 requirements and 47 checks passed.

Captured reported hash: fd340b244e4845e54034903ab76ed13fc1663284b55b7b1b07f43833347e8583
Captured reported revision: 512d1ebdca2d861f3dd9c3a5c3974150500a32b6301072b55a94bd60c8b2b0e7
Command: pnpm test:issuance-conformance
Exact source: scripts/test_issuance_conformance.ts0b3292c6212eeee7a74e203b456353cdd34a2dd91c88e469fe31e8cc58627690

pass

World conformance

world public witness

20/20requirements34/34checks0expected failures

20 requirements and 34 checks passed.

Captured reported hash: ff9239788b49be30b27260b09341d4fabd7bde944e21dce6d620627d46c5ca3d
Captured reported revision: 0e3fe492f48c271d30eabde28abe68b0441fc60f40ba8b57189174d70d966459
Command: pnpm test:world-conformance
Exact source: scripts/test_world_conformance.ts838b6388877ba79dfd2ebe447db80320b3445f5293c58c7db3f00a045b42e38e

pass

Sports conformance

sports settlement proof

24/24requirements57/57checks0expected failures

24 requirements and 57 checks passed.

Captured reported hash: e0ddfe9f96f234e15c3b69fcf837f16d1c4afddc78198e833853c2f97fad378e
Captured reported revision: d124ae5671dd40417a684debabdb4ea44fccd21326723ce35c86ba8b20c6dfb9
Command: pnpm test:sports-conformance
Exact source: scripts/test_sports_conformance.ts97497c0b1530728a737885ff36b397df6ec7565f91321a7b54018984ba978c06

pass

Signal Circuit conformance

signal-circuit proof

13/13requirements40/40checks0expected failures25/25route checks

13 suite requirements and 40 suite checks passed; the independent route contract passed 25 of 25 checks.

Captured reported hash: 7a7a49b2aeccd5ecd3d899824c94ed8b11e78b4fc43f9c250d3e078ecc37161d
Captured reported revision: 00e28bce3ddcafc011f61be4cf122adc7e05aff31266d5e3644d8888876f8005
Command: pnpm test:signal-circuit-conformance
Exact source: scripts/test_signal_circuit_conformance.tsee1b937f81ee157d264f912094e3528f02a047909004b3584dead8b086455cfe

pass

Verification conformance

artifact verification

26/26requirements36/36checks0expected failures

26 requirements and 36 checks passed.

Captured reported hash: 70511051ee084bcc0aae1ee4eed6902b52b62d50b8bcf366b5f5ec187131c9e8
Captured reported revision: bc6b3a53f7d709bab9e0462aab7c289fffdd854fcba5c86f6e756720609673c1
Command: pnpm test:verification-conformance
Exact source: scripts/test_verification_conformance.ts8832d6deab2b117bfaefce67285dd3da6247957d5674eff74514ed1f75cb6678

PASS

Governance controls

15 documents · 15 active families

8bba1dc326518c4de85a34de007219c04498457e150729245b4f959e5f6d4037b920acc795893361c66512017b29cc2f95ca66935ea5b2a97798dcfb57fdfef8receiz.governance.ed25519.2a7c4651102d1498

PASS

Governance evidence

4 controls

d08b41fe380fa07035f85d05520ca260d38e64043e90596d58501e79a8423354

PASS

Artifact signatures

7 artifacts · public/governance/artifact-manifest.v1.json

defeb9426855b8552b930bf1b1c790b15bb6479d2ac820ea2945b51fc347fb96receiz.governance.ed25519.2a7c4651102d1498

VERIFIED

Dated release attestation

artifacts/release-attestations/2026-06-30T18-43-21-460Z-617c943ad70e.json

Commit: 617c943ad70eae1c72ab6dda587636aa0dd32a03
Tree: f4df91467bb73f67bbb3767d45a70ceb7a238b9b
Build: Fy4kSk7jLG1YOIVrQP0BJ1ae616db02577495a4167cf383a54854d13d9b39d293d470263aa82bfa731785
Economy revision: 322edae1b449a2c0dfb3da34e0f72488df459ed852fdc972dafb8009799c9c7e
Verification revision: 4e230c6f125637a76c70dbef160e4eaa5defacc8cee114bc8bbbfcc2e2caec4b
Market revision: 15175c2566ca5e860d5538a2657c9ebe5818aff87f3982962ada3c35b670ba4c
Payload hash: c3c37fa46d27eec432a5ce8b4cf7c4d78d849e0002685f280aa2c85d61f7d5e8
Signing key: receiz.governance.ed25519.2a7c4651102d1498
Signature: sz1VpQXA_unmO6mS9Tmv-ZUwxlDJEVD5NUA4Yps31XE4kBxFLbj8qNdcjVD62APAYKJlrFBGR8rYwZP_JTbCAQ

Complete evidence matrix

Nothing is implied. Every boundary is stated.

normative-doctrine

Literal product law

Receiz product law is literal statute; code and tests yield when they conflict with it.

Exact source: docs/literal-product-law.mdSHA-2565548a8f32bbdf35f2ba5e4545cd31ef6e2842d2c3127a3e39e10e6eb6bc5efa1
Implemented primitive: proof-native artifact system
Source of truth: Receiz law → sealed artifact truth → deterministic proof object → verified durable/local/register truth → authenticated runtime views.
Guarantee: Implemented primitives are named directly, stronger truth remains above weaker projections, and a contradiction is release-blocking.
Executable check: pnpm test:primitive-binding-contract && pnpm test:repo-only-reasoning-boundary
Evidence output: A digest-matched normative source whose exact language governs implementation and review.
Failure meaning: The implementation, language, or authority order contradicts literal product law.
Recovery / escalation: Stop release, identify the exact violating path, restore the stronger primitive, and strengthen the regression contract.
Offline behavior: The law remains binding without network access.
External boundary: External conventions may supply mechanics only; they do not define Receiz product truth.
What this record does not prove: This record does not prove that every production route currently conforms; executable evidence is required.

normative-doctrine

Receiz reasoning kernel

Repository-local reasoning binds product decisions to implemented Receiz truth.

Exact source: docs/receiz-reasoning-kernel.mdSHA-256bbe2eeb58ef1487a84f3e128eaad16215c8aceecf30f3cdc5a68fa6316a844bd
Implemented primitive: authority reasoning
Source of truth: Receiz law, implemented primitives, sealed artifacts, and observed repository evidence.
Guarantee: Product ontology is decided inside the Receiz authority boundary.
Executable check: pnpm test:repo-only-reasoning-boundary
Evidence output: A digest-matched normative source whose exact language governs implementation and review.
Failure meaning: A weaker external convention has been allowed to define Receiz truth.
Recovery / escalation: Remove the external authority claim and bind the decision to exact repository law and implementation.
Offline behavior: Repository law remains inspectable and decisive offline.
External boundary: External conventions may supply mechanics only; they do not define Receiz product truth.
What this record does not prove: This record does not prove an external system is compatible with Receiz.

normative-doctrine

Invariant-first operation

Invariants define admissible state before interface or transport mechanics.

Exact source: docs/invariant-first-kernel.mdSHA-2560617593ee5e1a39d51ebd6ccd3d50453b2c717723edc4a1a5f3ed496872c347c
Implemented primitive: verified invariant
Source of truth: Receiz law → sealed artifact truth → deterministic proof object → verified durable/local/register truth → authenticated runtime views.
Guarantee: A weaker observation cannot rewrite an already verified stronger fact.
Executable check: pnpm test:deterministic-surfaces
Evidence output: A digest-matched normative source whose exact language governs implementation and review.
Failure meaning: A projection or refresh can alter settled truth.
Recovery / escalation: Restore append-only admission and reject the weaker replacement path.
Offline behavior: Verified local truth remains primary while offline.
External boundary: External conventions may supply mechanics only; they do not define Receiz product truth.
What this record does not prove: This record does not prove any unverified input is true.

normative-doctrine

Deterministic first paint

Known verified truth paints immediately; background work may append only.

Exact source: docs/truthful-speed-invariants.mdSHA-256ee1a4016184b12a06a6582a249bd74e6d7bd3169b82ec21c926deedf003aa18c
Implemented primitive: deterministic first paint
Source of truth: Known verified artifact or durable local truth available before hydration.
Guarantee: Background runtime work does not block or downgrade the settled evidence surface.
Executable check: pnpm test:page-first-paint
Evidence output: A digest-matched normative source whose exact language governs implementation and review.
Failure meaning: A weaker runtime dependency delays or redefines known truth.
Recovery / escalation: Paint the settled shell from stronger truth and move append-only discovery behind it.
Offline behavior: The settled surface remains available without network discovery.
External boundary: External conventions may supply mechanics only; they do not define Receiz product truth.
What this record does not prove: This record does not prove that background synchronization has completed.

normative-doctrine

Offline proof is the primitive

Offline verification is primary proof behavior, never a fallback mode.

Exact source: docs/offline-record-seal-frozen-invariants.mdSHA-256fce14006bd7f8da92a513423b28fd8e0a957d6c9f66cf2acc4068dda13343d7a
Implemented primitive: offline proof
Source of truth: Exact sealed artifact bytes and pinned verifier roots.
Guarantee: Record, seal, inspect, and local verification remain meaningful without depending on remote state.
Executable check: pnpm test:verification-conformance
Evidence output: A digest-matched normative source whose exact language governs implementation and review.
Failure meaning: The verifier path depends on weaker network or interface state.
Recovery / escalation: Restore exact-byte local verification and reject the network dependency.
Offline behavior: Full inspection and cryptographic verification execute offline.
External boundary: External conventions may supply mechanics only; they do not define Receiz product truth.
What this record does not prove: This record does not prove later publication or global append occurred.

normative-doctrine

Identity continuity boundary

Receiz ID and PBI carry identity continuity; authentication is subordinate mechanics.

Exact source: docs/pbi-recovery-receiz-id-binding.mdSHA-256f6e6e4177f6340924e59042d2f976dd4f6666340d80c0f1cee8b0f4180cea264
Implemented primitive: identity
Source of truth: Accepted Identity Record, Identity Seal, Receiz Key, or PBI/passkey recovery proof.
Guarantee: Binding appends identity continuity. Accepted identity proof remains intact.
Executable check: pnpm test:identity-conformance
Evidence output: A digest-matched normative source whose exact language governs implementation and review.
Failure meaning: Accepted identity proof has been displaced by weaker runtime state.
Recovery / escalation: Restore proof-first recovery and idempotent binding beneath the identity primitive.
Offline behavior: Accepted local identity proof projects immediately; remote binding and synchronized projections follow later, while only a separately verified identity-history successor is an Append.
External boundary: External conventions may supply mechanics only; they do not define Receiz product truth.
What this record does not prove: This record does not prove a specific person controls an identity artifact not presented for verification.

normative-doctrine

Settlement and consent boundary

Settlement, reserve, certificate, Note, and governed transfer state are proof-native value primitives.

Exact source: docs/perpetual-rollover-kernel.mdSHA-2564cad3f91ebae948610e1292fc18854351df65edeaeb03bbd12942b6e74c89b69
Implemented primitive: settlement
Source of truth: Verified append-only Settlement history and enclosing proof objects.
Guarantee: Value transition, consent, exit, and rollover remain auditable without renaming Settlement into a generic balance.
Executable check: pnpm test:settlement-conformance
Evidence output: A digest-matched normative source whose exact language governs implementation and review.
Failure meaning: Settlement law, value math, transfer authority, or consent boundary diverges.
Recovery / escalation: Stop value mutation, inspect the exact proof head and Settlement append, correct the transition, and rerun conformance.
Offline behavior: The verified receiz.account.state.v3 Receiz Key/Identity proof carries the Reserve source. Local issuance verifies one Reserve-debit account successor and one equal whole-value held-bound Note genesis, then activates that Note in qualified custody. Every later qualified transfer consumes its exact Note head once and activates the successor as local Settlement. Connected publication is a later optional distribution step.
External boundary: External conventions may supply mechanics only; they do not define Receiz product truth.
What this record does not prove: This record does not prove current production Reserve, account value, or an external provider's separate settlement state.

normative-doctrine

Public proof and ownership boundary

A public proof surface exposes proof, provenance, custody, and verification without an account gate.

Exact source: docs/literal-product-law.mdSHA-2565548a8f32bbdf35f2ba5e4545cd31ef6e2842d2c3127a3e39e10e6eb6bc5efa1
Implemented primitive: public proof, ownership, provenance, transfer
Source of truth: The enclosing sealed proof object and its verified ownership or custody history.
Guarantee: Public verification is account-free. Identity is optional and additive.
Executable check: pnpm test:verification-conformance && pnpm test:interoperability-conformance
Evidence output: A digest-matched normative source whose exact language governs implementation and review.
Failure meaning: Public inspection is gated, custody is blurred into possession, or stronger proof truth is displaced.
Recovery / escalation: Restore account-free verification and bind ownership actions to the enclosing verified artifact.
Offline behavior: Downloaded proof objects remain independently inspectable and verifiable offline.
External boundary: External conventions may supply mechanics only; they do not define Receiz product truth.
What this record does not prove: This record does not prove a displayed owner retains custody after an unverified external transfer.

implementation-verifier

Canonical artifact inspection

Verification begins with the enclosing sealed artifact and exact held bytes.

Exact source: packages/receiz-sdk/src/artifactVerification.tsSHA-256c10cdba92568fea273e1d9e7a3321083d52945378ab0cc83aee9720d44f0bba3
Implemented primitive: sealed proof object verification
Source of truth: Exact artifact bytes, declared integrity material, pinned canonical roots, and verified history.
Guarantee: The verifier classifies the supplied artifact. Embedded subpayloads and remote responses remain subordinate.
Executable check: pnpm --filter @receiz/sdk test
Evidence output: Typed verification result with exact accepted or rejected checks and authority classification.
Failure meaning: The artifact is not admitted as verified proof; inspection alone does not establish verification.
Recovery / escalation: Preserve the bytes, inspect the failing check, obtain the correct complete artifact or trusted roots, and verify again.
Offline behavior: Verification executes locally against exact bytes and pinned roots.
External boundary: Network publication and interface or database presence remain subordinate displays.
What this record does not prove: This record does not prove authorship, ownership, admission, or settlement for bytes that were not verified.

executable-conformance

Artifact conformance

Artifact conformance executes the repository-defined sealed artifact contract.

Exact source: scripts/test_v108_artifact_conformance.tsSHA-25651bf8686e40fbb0031f6245cff975ca6dcb13614fce2471793a2c723bac7bf65
Implemented primitive: sealed artifact
Source of truth: The implemented sealed artifact source and stronger proof state exercised by the suite; the suite is a check, not authority.
Guarantee: A passing execution confirms the checked sealed artifact invariants for the exact repository state exercised.
Executable check: pnpm test:v108-artifact-conformance
Evidence output: Artifact vectors, hashes, authority order, and rejection results.
Failure meaning: The checked sealed artifact contract is not conformant. Release is blocked; explanatory surfaces cannot alter the failure.
Recovery / escalation: Inspect the first failing assertion and its stronger source, correct the implementation, then rerun pnpm test:v108-artifact-conformance.
Offline behavior: The suite runs against repository-local implementation or deterministic fixtures unless its output explicitly declares a live external dependency.
External boundary: A local pass does not establish production deployment, live endpoint state, or third-party availability.
What this record does not prove: This record does not prove production sealed artifact state, deployment status, or the validity of an artifact not supplied to the suite.

executable-conformance

Economy conformance

Economy conformance executes the repository-defined proof-native economy contract.

Exact source: scripts/test_economy_conformance.tsSHA-25658bbd2f7b5d79dccee1382da2c7719a42db637e4448dc6348efc472494a9d335
Implemented primitive: proof-native economy
Source of truth: The implemented proof-native economy source and stronger proof state exercised by the suite; the suite is a check, not authority.
Guarantee: A passing execution confirms the checked proof-native economy invariants for the exact repository state exercised.
Executable check: pnpm test:economy-conformance
Evidence output: Economy invariants and deterministic conformance report.
Failure meaning: The checked proof-native economy contract is not conformant. Release is blocked; explanatory surfaces cannot alter the failure.
Recovery / escalation: Inspect the first failing assertion and its stronger source, correct the implementation, then rerun pnpm test:economy-conformance.
Offline behavior: The suite runs against repository-local implementation or deterministic fixtures unless its output explicitly declares a live external dependency.
External boundary: A local pass does not establish production deployment, live endpoint state, or third-party availability.
What this record does not prove: This record does not prove production proof-native economy state, deployment status, or the validity of an artifact not supplied to the suite.

executable-conformance

Settlement conformance

Settlement conformance executes the repository-defined settlement contract.

Exact source: scripts/test_settlement_conformance.tsSHA-256021f52595eaaa948337dbe5e01fd4d053a1bab161aea1cad7d053ee1886836ba
Implemented primitive: settlement
Source of truth: The implemented settlement source and stronger proof state exercised by the suite; the suite is a check, not authority.
Guarantee: A passing execution confirms the checked settlement invariants for the exact repository state exercised.
Executable check: pnpm test:settlement-conformance
Evidence output: Settlement report, revision, vectors, and failure codes.
Failure meaning: The checked settlement contract is not conformant. Release is blocked; explanatory surfaces cannot alter the failure.
Recovery / escalation: Inspect the first failing assertion and its stronger source, correct the implementation, then rerun pnpm test:settlement-conformance.
Offline behavior: The suite runs against repository-local implementation or deterministic fixtures unless its output explicitly declares a live external dependency.
External boundary: A local pass does not establish production deployment, live endpoint state, or third-party availability.
What this record does not prove: This record does not prove production settlement state, deployment status, or the validity of an artifact not supplied to the suite.

executable-conformance

Market conformance

Market conformance executes the repository-defined market ownership contract.

Exact source: scripts/test_market_conformance.tsSHA-25647c7ebb7eb9f3854f31dbc7266909f9e4c9726908930d236f3a76eaacae54eb7
Implemented primitive: market ownership
Source of truth: The implemented market ownership source and stronger proof state exercised by the suite; the suite is a check, not authority.
Guarantee: A passing execution confirms the checked market ownership invariants for the exact repository state exercised.
Executable check: pnpm test:market-conformance
Evidence output: Market custody boundaries and deterministic rendering checks.
Failure meaning: The checked market ownership contract is not conformant. Release is blocked; explanatory surfaces cannot alter the failure.
Recovery / escalation: Inspect the first failing assertion and its stronger source, correct the implementation, then rerun pnpm test:market-conformance.
Offline behavior: The suite runs against repository-local implementation or deterministic fixtures unless its output explicitly declares a live external dependency.
External boundary: A local pass does not establish production deployment, live endpoint state, or third-party availability.
What this record does not prove: This record does not prove production market ownership state, deployment status, or the validity of an artifact not supplied to the suite.

executable-conformance

Identity conformance

Identity conformance executes the repository-defined identity continuity contract.

Exact source: scripts/test_identity_conformance.tsSHA-256699508b94d317a4d1ff1bae527b49e76e3dfda8f7e085316e9729b9afa23e36f
Implemented primitive: identity continuity
Source of truth: The implemented identity continuity source and stronger proof state exercised by the suite; the suite is a check, not authority.
Guarantee: A passing execution confirms the checked identity continuity invariants for the exact repository state exercised.
Executable check: pnpm test:identity-conformance
Evidence output: Identity proof, recovery, and continuity results.
Failure meaning: The checked identity continuity contract is not conformant. Release is blocked; explanatory surfaces cannot alter the failure.
Recovery / escalation: Inspect the first failing assertion and its stronger source, correct the implementation, then rerun pnpm test:identity-conformance.
Offline behavior: The suite runs against repository-local implementation or deterministic fixtures unless its output explicitly declares a live external dependency.
External boundary: A local pass does not establish production deployment, live endpoint state, or third-party availability.
What this record does not prove: This record does not prove production identity continuity state, deployment status, or the validity of an artifact not supplied to the suite.

executable-conformance

Interoperability conformance

Interoperability conformance executes the repository-defined cross-system proof contract.

Exact source: scripts/test_interoperability_conformance.tsSHA-256c09d81f36305004f7ee02c40070b3c9cd64d8f5572ce12d211c022f3e75dbf4e
Implemented primitive: cross-system proof
Source of truth: The implemented cross-system proof source and stronger proof state exercised by the suite; the suite is a check, not authority.
Guarantee: A passing execution confirms the checked cross-system proof invariants for the exact repository state exercised.
Executable check: pnpm test:interoperability-conformance
Evidence output: Interop vectors and stronger-authority preservation results.
Failure meaning: The checked cross-system proof contract is not conformant. Release is blocked; explanatory surfaces cannot alter the failure.
Recovery / escalation: Inspect the first failing assertion and its stronger source, correct the implementation, then rerun pnpm test:interoperability-conformance.
Offline behavior: The suite runs against repository-local implementation or deterministic fixtures unless its output explicitly declares a live external dependency.
External boundary: A local pass does not establish production deployment, live endpoint state, or third-party availability.
What this record does not prove: This record does not prove production cross-system proof state, deployment status, or the validity of an artifact not supplied to the suite.

executable-conformance

Issuance conformance

Issuance conformance executes the repository-defined certificate and note issuance contract.

Exact source: scripts/test_issuance_conformance.tsSHA-2560b3292c6212eeee7a74e203b456353cdd34a2dd91c88e469fe31e8cc58627690
Implemented primitive: certificate and note issuance
Source of truth: The implemented certificate and note issuance source and stronger proof state exercised by the suite; the suite is a check, not authority.
Guarantee: A passing execution confirms the checked certificate and note issuance invariants for the exact repository state exercised.
Executable check: pnpm test:issuance-conformance
Evidence output: Issuance report hash, revision, and issue-route results.
Failure meaning: The checked certificate and note issuance contract is not conformant. Release is blocked; explanatory surfaces cannot alter the failure.
Recovery / escalation: Inspect the first failing assertion and its stronger source, correct the implementation, then rerun pnpm test:issuance-conformance.
Offline behavior: The suite runs against repository-local implementation or deterministic fixtures unless its output explicitly declares a live external dependency.
External boundary: A local pass does not establish production deployment, live endpoint state, or third-party availability.
What this record does not prove: This record does not prove production certificate and note issuance state, deployment status, or the validity of an artifact not supplied to the suite.

executable-conformance

World conformance

World conformance executes the repository-defined world public witness contract.

Exact source: scripts/test_world_conformance.tsSHA-256838b6388877ba79dfd2ebe447db80320b3445f5293c58c7db3f00a045b42e38e
Implemented primitive: world public witness
Source of truth: The implemented world public witness source and stronger proof state exercised by the suite; the suite is a check, not authority.
Guarantee: A passing execution confirms the checked world public witness invariants for the exact repository state exercised.
Executable check: pnpm test:world-conformance
Evidence output: World proof and public witness conformance report.
Failure meaning: The checked world public witness contract is not conformant. Release is blocked; explanatory surfaces cannot alter the failure.
Recovery / escalation: Inspect the first failing assertion and its stronger source, correct the implementation, then rerun pnpm test:world-conformance.
Offline behavior: The suite runs against repository-local implementation or deterministic fixtures unless its output explicitly declares a live external dependency.
External boundary: A local pass does not establish production deployment, live endpoint state, or third-party availability.
What this record does not prove: This record does not prove production world public witness state, deployment status, or the validity of an artifact not supplied to the suite.

executable-conformance

Sports conformance

Sports conformance executes the repository-defined sports settlement proof contract.

Exact source: scripts/test_sports_conformance.tsSHA-25697497c0b1530728a737885ff36b397df6ec7565f91321a7b54018984ba978c06
Implemented primitive: sports settlement proof
Source of truth: The implemented sports settlement proof source and stronger proof state exercised by the suite; the suite is a check, not authority.
Guarantee: A passing execution confirms the checked sports settlement proof invariants for the exact repository state exercised.
Executable check: pnpm test:sports-conformance
Evidence output: Sports conformance hash, revision, result status, and vectors.
Failure meaning: The checked sports settlement proof contract is not conformant. Release is blocked; explanatory surfaces cannot alter the failure.
Recovery / escalation: Inspect the first failing assertion and its stronger source, correct the implementation, then rerun pnpm test:sports-conformance.
Offline behavior: The suite runs against repository-local implementation or deterministic fixtures unless its output explicitly declares a live external dependency.
External boundary: A local pass does not establish production deployment, live endpoint state, or third-party availability.
What this record does not prove: This record does not prove production sports settlement proof state, deployment status, or the validity of an artifact not supplied to the suite.

executable-conformance

Signal Circuit conformance

Signal Circuit conformance executes the repository-defined signal-circuit proof contract.

Exact source: scripts/test_signal_circuit_conformance.tsSHA-256ee1b937f81ee157d264f912094e3528f02a047909004b3584dead8b086455cfe
Implemented primitive: signal-circuit proof
Source of truth: The implemented signal-circuit proof source and stronger proof state exercised by the suite; the suite is a check, not authority.
Guarantee: A passing execution confirms the checked signal-circuit proof invariants for the exact repository state exercised.
Executable check: pnpm test:signal-circuit-conformance
Evidence output: Signal Circuit report hash, revision, snapshot identity, and attestation projection.
Failure meaning: The checked signal-circuit proof contract is not conformant. Release is blocked; explanatory surfaces cannot alter the failure.
Recovery / escalation: Inspect the first failing assertion and its stronger source, correct the implementation, then rerun pnpm test:signal-circuit-conformance.
Offline behavior: The suite runs against repository-local implementation or deterministic fixtures unless its output explicitly declares a live external dependency.
External boundary: A local pass does not establish production deployment, live endpoint state, or third-party availability.
What this record does not prove: This record does not prove production signal-circuit proof state, deployment status, or the validity of an artifact not supplied to the suite.

executable-conformance

Verification conformance

Verification conformance executes the repository-defined artifact verification contract.

Exact source: scripts/test_verification_conformance.tsSHA-2568832d6deab2b117bfaefce67285dd3da6247957d5674eff74514ed1f75cb6678
Implemented primitive: artifact verification
Source of truth: The implemented artifact verification source and stronger proof state exercised by the suite; the suite is a check, not authority.
Guarantee: A passing execution confirms the checked artifact verification invariants for the exact repository state exercised.
Executable check: pnpm test:verification-conformance
Evidence output: Verification report hash, revision, exact acceptance, and rejection states.
Failure meaning: The checked artifact verification contract is not conformant. Release is blocked; explanatory surfaces cannot alter the failure.
Recovery / escalation: Inspect the first failing assertion and its stronger source, correct the implementation, then rerun pnpm test:verification-conformance.
Offline behavior: The suite runs against repository-local implementation or deterministic fixtures unless its output explicitly declares a live external dependency.
External boundary: A local pass does not establish production deployment, live endpoint state, or third-party availability.
What this record does not prove: This record does not prove production artifact verification state, deployment status, or the validity of an artifact not supplied to the suite.

governance-control

Governance control check

Required governance documents and control structure are checked as release evidence.

Exact source: scripts/check_governance_controls.tsSHA-2568fa9d6429e8775c2fbea9b731078aab4a7d978f649bd6323d01b1199e8c7c4a8
Implemented primitive: governance
Source of truth: Normative governance documents and registered controls.
Guarantee: Required control records exist and satisfy the script's exact structural checks.
Executable check: pnpm governance:check
Evidence output: A passing governance control report or exact failing control.
Failure meaning: Required governance structure is absent, inconsistent, or invalid.
Recovery / escalation: Correct the named control source and rerun the check before release.
Offline behavior: Repository governance controls are checked locally.
External boundary: The check does not establish live organizational practice beyond recorded evidence.
What this record does not prove: This record does not prove every control operated in production during an unobserved period.

evidence-register

Governance evidence check

Evidence mappings are checked without converting the register into artifact truth.

Exact source: scripts/check_governance_evidence.tsSHA-2564d887a3943808bec1f3d274b02bd4cf7cfc9f3b39c5e34169c709ddc97c8263c
Implemented primitive: governance evidence
Source of truth: The underlying evidence artifacts and their registered digests.
Guarantee: Registered evidence entries satisfy the checker's exact presence, binding, and status rules.
Executable check: pnpm governance:evidence-check
Evidence output: Evidence validation result identifying each accepted or failed binding.
Failure meaning: An evidence claim is unbound, stale, missing, or structurally invalid.
Recovery / escalation: Do not relabel evidence; supply the missing source or correct the exact register binding.
Offline behavior: Committed evidence and digests are checked locally.
External boundary: An evidence entry does not independently prove current production state.
What this record does not prove: This record does not prove signature presence or unobserved activity.

signed-evidence-verifier

Governance artifact signature verification

Signed governance artifacts are verified against the registered public key.

Exact source: scripts/check_governance_artifact_signature.tsSHA-256a7ba1e04bc27e2106d286f532d4ece159a20974c00df1b41994917531eac7eaf
Implemented primitive: signed governance evidence
Source of truth: Exact artifact bytes, detached signature, and registered verification key.
Guarantee: A passing result establishes signature validity for the supplied bytes and key.
Executable check: pnpm governance:verify-artifact-signature
Evidence output: Verified signature result or exact unknown-key, missing-signature, or mismatch failure.
Failure meaning: Signature absent; unknown or invalid signatures retain failure status.
Recovery / escalation: Restore the original signed bytes and known key, or issue a new signed artifact through authorized custody.
Offline behavior: Signature verification executes locally with committed key material.
External boundary: Signature validity does not prove the truth of every claim inside the signed artifact.
What this record does not prove: This record does not prove an unsigned, unknown-key, or modified artifact is authentic.

release-evidence-emitter

Release attestation emission

Attestation emission follows release gates and records exact build evidence.

Exact source: scripts/create_release_attestation.tsSHA-256918a5c328799194fe44095100ba30c54eede44b956b7dcfe0d03ba5347a397db
Implemented primitive: release attestation
Source of truth: Exact release commit, tree, build, gate outputs, and signing material.
Guarantee: The command emits a dated attestation only from its observed inputs.
Executable check: pnpm release:attest
Evidence output: A dated signed attestation artifact and latest convenience pointer.
Failure meaning: No verified attestation exists for the attempted release evidence.
Recovery / escalation: Pass release gates, preserve exact outputs, then emit and independently verify the dated artifact.
Offline behavior: Local artifact creation is possible with authorized local key custody; it does not publish deployment state.
External boundary: Attestation creation may mutate release evidence and is not run by Academy validation.
What this record does not prove: This record does not prove deployment or production smoke unless those exact evidence dimensions are present and verified.

signed-evidence-verifier

Release attestation verification

A dated attestation is verified independently; latest.json is not independent proof.

Exact source: scripts/verify_release_attestation.tsSHA-256f04e07009107c30a2c41a2f237ed08a581b4773caef3771d8167b762e23d6606
Implemented primitive: release attestation
Source of truth: Exact dated attestation bytes, registered key, signature, commit, tree, and build bindings.
Guarantee: A passing command verifies every bound attestation field for the supplied artifact.
Executable check: pnpm release:verify-attestation <exact-dated-attestation-path>
Evidence output: Verified attestation result or an exact binding/signature failure.
Failure meaning: Verification absent; a missing artifact retains failure status.
Recovery / escalation: Use the exact dated artifact emitted after gates and resolve the first failed binding.
Offline behavior: Committed attestation and key material can be verified offline.
External boundary: A valid attestation does not establish later production drift or an unbound deployment.
What this record does not prove: This record does not prove latest.json is independent evidence or that production state is current.

evidence-register

Governance evidence register

The register maps claims to artifacts, controls, and status without replacing their underlying authority.

Exact source: docs/governance/evidence-register.v1.jsonSHA-256d08b41fe380fa07035f85d05520ca260d38e64043e90596d58501e79a8423354
Implemented primitive: evidence provenance
Source of truth: Each referenced evidence artifact and its exact digest.
Guarantee: Declared evidence remains traceable to a stable registered record.
Executable check: pnpm governance:evidence-check
Evidence output: Register validation plus exact evidence source identifiers.
Failure meaning: The claim-to-evidence chain is incomplete or inconsistent.
Recovery / escalation: Correct the mapping or declare the evidence absent; never invent or upgrade status.
Offline behavior: The committed register and referenced committed evidence remain inspectable offline.
External boundary: Production state is unknown unless a dated production observation is explicitly bound.
What this record does not prove: This record does not prove every registered statement remains true outside its dated evidence boundary.

normative-governance

Governance control boundaries

Authority, custody, approval, operational, and evidence boundaries are explicitly separated.

Exact source: docs/governance/control-boundaries.v1.mdSHA-256da31636848c373e8d54e8d101885e15a9a29f7f8a734cf5fe675b7e7d5ec166e
Implemented primitive: authority boundary
Source of truth: Receiz law, sealed evidence, and explicitly assigned control custody.
Guarantee: Assigned control custody remains separated by recorded boundary.
Executable check: pnpm governance:check
Evidence output: Validated boundary records and named control owners.
Failure meaning: A duty, authority, or evidence boundary is absent or collapsed.
Recovery / escalation: Stop the affected operation, restore separation, assign explicit custody, and record corrective action.
Offline behavior: Recorded boundaries remain binding offline.
External boundary: Third-party services remain outside Receiz governance and must be named as external dependencies.
What this record does not prove: This record does not prove a third party operated within Receiz controls.

exception-register

Declared exception register

Active exceptions are disclosed explicitly: none.

Exact source: docs/governance/exception-log.v1.mdSHA-2569957d60dbf833f2881475aece133e72349e3f5b2df891d27b6462cbe39af2a84
Implemented primitive: governance exception
Source of truth: The exact exception record, owner, scope, expiry, and corrective action.
Guarantee: The active set and historical set remain visibly disclosed; a future deviation is recorded with its exact identifier rather than represented as passing truth.
Executable check: pnpm governance:check
Evidence output: Declared exception status or exact missing/expired exception failure.
Failure meaning: A deviation is hidden, unowned, expired, or presented as conformant.
Recovery / escalation: Block release or operation, register the exact exception, assign remediation, and enforce expiry.
Offline behavior: Committed exceptions remain visible without a network.
External boundary: External production state is unknown when no dated observation is bound.
What this record does not prove: This record does not prove an exception is remediated until closure evidence is registered and checked.
Visible exception disclosure: Active exceptions are disclosed explicitly: none.
Required record IDs: exception-register
Required record count: 1
Active exception count: 0
Route: /trust/exceptions#exception-register