What a source declares
README, manifest, code, schema, or repository history. It can establish what was written at a revision—not whether every runtime path behaves accordingly.
RESOLVING ROUTEFollowing the evidence boundary…
Receipts can bind an execution to its state view, candidate path, degradations, result, and replay boundary. They make the path inspectable; they do not turn the result into truth.
Select a field to understand its role. Then compare Run A and Run B to see how retained state changes an answer without erasing the boundary around that answer.
Which migration target did the team approve for the cache layer?The answer is bound to the state the run was allowed to see. “Known then” and “known now” can legitimately produce different results.
known_then / fixture-t0A state view explains temporal scope; it does not prove the source was true.
“Proof” becomes dangerous when source evidence, package declarations, live observations, and execution receipts are blended into a single confidence claim.
README, manifest, code, schema, or repository history. It can establish what was written at a revision—not whether every runtime path behaves accordingly.
Published version, features, dependencies, ownership, and declared metadata. Publication alone is not evidence of production suitability.
Repository or registry state observed at a named time. Cached observations must not pose as current live telemetry.
Inputs, state view, backend, degradations, result, and retained replay material within a bounded run.
No receipt, benchmark, or release event proves factual truth, security, authorization, or the absence of unobserved failure.
Open the source, registry record, change event, or benchmark contract attached to the specific claim.
Open release evidence →A receipt can identify an execution without carrying enough material to reproduce it. Retention is a deliberate privacy, storage, and authority decision.
Correlate a past execution and its declared result without claiming it can be rerun.
Required fixture, prompt, state, configuration, and artifact versions were deliberately retained.
Some required source is missing or no longer available, and that gap remains visible.
Reproducing an execution does not grant permission to repeat its effects in the world.
The Proofroom is a teaching surface. The install guide connects a supported host to the public agent-memory stack; the Pro path addresses commercial release and proof workflows.