TR-CORE-RECEIPTS / Teal / Review draft

Receipt binding and replay

Terminology revised · September 12 evidence

Later individual Teal rerun. The reported execution status is historical and is not a new test result.

TEAL LIBRARY RERUN  |  12 SEPTEMBER 2026  |  Michael Patrick Bangel
12
TEAL-RERUN-03-B001 | RELATED_EXECUTION_EVIDENCE_AVAILABLE
TR-CORE-RECEIPTS / Receipt binding and replay
IF
A receipt is presented for inspection, comparison or replay.
HOW
Verify schema, roots, source/program linkage, resource usage and cross-linked evidence. Replay must bind
the same program and compare the complete outcome.
THEN
Reject tampering, incorrect program linkage or a replay mismatch. A digest is integrity evidence, not
authentication by itself.
CURRENT EVIDENCE
Fresh related language/paper/water checks are in the evidence ledger. The test count is suite evidence, not
proof of every branch in this requirement.
REMAINING REQUIREMENT
Use the source and recorded case evidence to close remaining per-branch, native-host and full-contract coverage gaps.
SOURCE REFERENCES
bangel:language/python/src/bangel/receipts.py; bangel:language/python/src/bangel/inspector.py;
bangel:language/python/src/bangel/receipt_contract.py; associated-core:reference/src/bangel/receipts.py;
associated-core:reference/src/bangel/inspector.py; associated-core:reference/src/bangel/receipt_contract.py;
associated-core:products/water/legacy/quantum-security-python/src/mjos_qs/receipts.py

Publication is pending owner review. White papers are excluded.