Verifiable Execution
If the signing key used by Catalyst is compromised, does it invalidate all previously recorded agent executions?
Previously recorded executions remain verifiable if the key compromise is detected and the key is promptly revoked, because Catalyst signs each step record individually and appends it to a transparency log with trusted timestamps. The log’s append-only property ensures immutability. However, an auditor must trust the timestamp service and that the key was indeed revoked before any forged records could be created.
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.