Verifiable Execution
How does Catalyst distinguish a step that failed silently from one that was intentionally not invoked?
Catalyst records every step invocation attempt, including exception objects or error signals, as signed entries. A silent failure produces a step record with a failure outcome, while an unexecuted branch leaves no record. The verifiable record therefore captures execution intent, but only your agent code can define what constitutes a failure. Additionally, if a step failure is not explicitly signaled by the agent runtime, Catalyst cannot distinguish it from a successful no-op.
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.