Operational reliance and execution receipt references

This informative experiment for #100 checks that the existing execution receipt’s authority_decision_receipt points to a supplied decision record and that the subject and result are structurally consistent. It does not authenticate, sign or issue an execution receipt, verify actual authority, or establish a production action occurred.

sequenceDiagram
 participant D as Authority decision source
 participant E as Execution receipt
 participant O as Operational evidence
 participant V as Bounded reference checker
 D-->>V: Supplied decision reference
 E-->>V: Receipt and subject
 O-->>V: Informative reliance summary
 V-->>V: Check structural references
 V-->>E: Structural outcome only, no authority change

Run python3 scripts/validate_operational_receipt_binding.py. Negative fixtures include decision-reference mismatch, identity mismatch, success with denied authority, and operational evidence claiming authority. A structurally consistent receipt is not proof of a valid signature, current authorization, authoritative policy, or actual execution. The broader #100 execution-receipt assurance checkbox must remain unchecked until those external boundaries are tested.


Agent Registry Protocol documentation. Specification text and documentation are licensed as stated in the repository NOTICE and license files.

This site uses Just the Docs, a documentation theme for Jekyll.