Verifiable Execution
How does a verifiable Catalyst record handle large binary artifacts like images or audio processed by the agent?
Catalyst signs a cryptographic hash of the binary artifact alongside its metadata, not the raw bytes. The verifiable record stores the hash and a retrieval identifier; the full artifact must be preserved externally. This enables tamper-evidence without bloating the record, but verification requires the auditor to possess a copy of the original artifact. If the external storage is compromised, the verifiability of the artifact content breaks down. Furthermore, the hash alone does not prove the artifact was genuine at execution time; it only proves integrity of the stored artifact.
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.