Verifiable Execution
How does Catalyst bind a verifiable record to the entropy source used for non-deterministic steps?
Catalyst records the seed or hash of the entropy source used in non-deterministic steps, signing it as part of the step’s input. This allows a replayer to reproduce exactly the same random sequence. However, if the entropy comes from an external True Random Number Generator, the seed may not be reproducible; verifiability then relies on recording the actual random bytes, which increases record size.
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.