Verifiable Execution
Can an auditor verify that a specific model version was used during a Catalyst agent run without access to the model endpoint?
Yes, the signed step record includes the model identifier and a cryptographic hash of the response. An auditor verifies the hash against the recorded data, confirming the model version was invoked without needing the live endpoint. This approach does not validate the model’s internal weights, guarantee response correctness, or prove that the endpoint configuration was unaltered; it only attests to the specific request-response pair that occurred. Moreover, if the model provider serves a different model under the same identifier, the hash would not detect that.
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.