Evidence chain
Signed authorization→Pre-effect consume→Trusted executor→Execution receipt→Reconciliation
Idempotency and recovery standing help distinguish unresolved outcomes from completed effects. System-of-record reconciliation detects discrepancies within observed coverage; it is not prevention of every alternate route.
In correctly configured production trust mode, required evidence must be independently anchored and verified before acknowledgement/protected execution; unavailable required proof cannot yield success. Reference-log qualification is not evidence of an external production log deployment. Historical integrity, current freshness, rollback and fork checks are distinct.
Proof disclosure uses approved scope and pinned trust identities. Browser checksum verification is not signature, independent-log or freshness verification.
PR #201 · TRACE adapter
Independently reviewed bounded integration
Merged September 20, 2026. Independent maintainer reproduction: 27 adapter tests. Authorized $250,000 path committed once with TRACE; altered $260,000 path refused, pending, zero commits and no TRACE.
Read PR #201 and review
PR #236 · Pre-commit enforcement
Independently reviewed bounded integration
Merged October 6, 2026; October 3 review by Carlos (carloshvp): 36 integration tests, 97 negative wrapper/direct-executor probes refused with zero commits and no protected effect, 4 positive probes executed the validated exact action. Imran Siddique approved and merged.
Read PR #236 and review
Bounded adapter and software harness, not independent validation of the complete runtime, SI, customer deployment or universal non-bypassability. Source: linked PRs.