Proving what happened
A run's evidence is its signed, chained decisions, a replay that finds the same decisions again, and its signed delegations. A run's Proof tab gathers them; the auditor export takes them away, signed.
A run's evidence
- The attestation chain: every human decision, signed and chained to the previous one. The server verifies the chain and says whether it holds.
- Deterministic replay: the run is replayed from its entry state with what it recorded — the models' answers, the clock —, without calling any model, and the verdict says whether it reaches the same decisions. Recording is on by default.
- Signed delegations: every call to another agent, with the fingerprint of what was sent.
- The run's human supervision and its replay attestation.
Studio screenshot · a run's Proof tab — to come
The auditor export
An approver or an owner exports a run's file: the run, its checkpoints, its full journal, its compliance report, the attestation chain, the replay verdict and what it takes to reproduce it — signed as one.
Verifying offline
- Remove the « signature » field from the exported file.
- Re-serialise the file and compute its SHA-256 fingerprint.
- Verify the detached Ed25519 signature with the instance's public key.
public keyThe API publishes its key at /.well-known/jwks.json, and Governance › Proof & compliance shows it with its fingerprint. An instance without a durable key publishes an ephemeral one, which changes at every restart.
Not yet
SoonReplay covers the run up to its first gate; what follows a resume is not replayed yet.
SoonAn auditor file per period, across several runs: the export exists per run.