Verifiable Execution
What is the on-disk format of a verifiable execution record, and can it be exported for long-term archival?
Catalyst stores verifiable records as an append-only binary log embedding JSON metadata and per-step signatures. Entire runs can be exported for archival; an auditor needs only the log file and the public key. The format lacks built-in encryption, so confidentiality requires additional measures. For longevity, monitor algorithm strength; periodic re-signing with current algorithms may be necessary to maintain verifiability. Consider migration to post-quantum algorithms in the future.
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.