Verifiable Execution
If a step depends on a database query whose data changes, can a replay still produce the same outcome?
Replay can only produce the same outcome if Catalyst captures the query result as part of the step’s input. By recording the exact data returned at execution time, the verifiable record allows deterministic replay. If the data wasn’t captured, replay may yield different results, because the external state may have changed. Auditors should confirm that all mutable inputs are recorded for faithful re‑execution.
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.