Verifiable Execution
How does Catalyst achieve verifiability for steps that involve non-deterministic model responses?
For non-deterministic steps like LLM calls, Catalyst captures the exact output and signs it as part of the step record. Verifiability ensures the output's integrity and origin, proving what was received at that step. However, an auditor cannot expect a replay to generate the same output, because the model's response is not deterministic by nature. The record thus proves provenance, not repeatability.
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.