Verifiable Execution
How does Catalyst bind an execution record to the specific agent version that produced it?
At invocation, Catalyst captures a digital fingerprint of the agent's codebase, configuration, and prompt, embedding it into the execution record. This binds the run to that exact version, enabling precise replay. The binding relies on the referenced artifacts remaining available; if they are lost, replay fidelity may degrade.
Was this article helpful?
Your feedback helps improve Diagrid's FAQ experience.
Keep reading
More Diagrid FAQ articles
- Verifiable Execution
What is a verifiable execution record in Catalyst?
A signed, immutable sequence of agent steps enabling auditors to prove run integrity through independent replay. It does not validate decision correctness.
- Verifiable Execution
How does Catalyst ensure that step records are tamper-evident?
Catalyst uses a hash chain and digital signatures per step, so any alteration breaks the chain and becomes detectable through signature verification.
- Verifiable Execution
Can an auditor independently replay a Catalyst agent run to verify its outcome?
Auditors can replay runs using signed step records and initial state to verify output consistency, though non-determinism may limit exact reproduction.