Skip to content

Check a recorded run is intact

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. Proven against quoxcli 0.5.0 on 2026-11-08.

Is this run's record still in one piece?

Every VOLT run is a hash chain of events. Ask Quox whether one is intact, then pull the run down and check every link on your own machine.

What you get: a yes or no on whether a recorded run has been changed, and how many events it holds, first from Quox and then from a file you checked yourself.

Name the run and ask:

quox · talking to Quox

Verify the hash chain integrity of VOLT run RUN_01KWKV7XR52FESA0X4YJA9F67G. Is the chain intact, and how many events does it have?

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 5ms

◐ VOLT │ verify run ✔ VOLT │ verify run │ Chain intact: 2 events, 0 gaps, 0 content mismatches (content hashes + linkage verified) · 1.9s

⛓ AEE │ envelope opened · ops.tool · volt_verify_run ok

⛓ AEE │ envelope opened · stream_success

The chain for VOLT run RUN_01KWKV7XR52FESA0X4YJA9F67G is intact. It has 2 events, with
no gaps and no content mismatches. Both the content hashes and the links between events
checked out, and the confidence is VERIFIED.

13.7s · 1 tool · 0 approvals

A real turn on our own install (CLI 0.5.0, 8 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 8 Nov 2026 · test report mw7jvm

Quox ran the VOLT run check and told you the chain is intact: 2 events, no gaps, and no content mismatches. Both the hash of each event and the links between them were re-checked.

Runs that have been certified are listed with their run ids:

Terminal window
quox governance cert list
fetch the run
quox volt fetch RUN_01KWKV7XR52FESA0X4YJA9F67G --out run.jsonBundle written to run.json (2 events)Verify it: quox volt verify run.json
From a real run on our scratch organisation.
verify the chain
quox volt verify run.jsonVOLT Evidence Bundle Verification────────────────────────────────────────Bundle:   BDL_RUN_01KWKV7XR52FESA0X4YJA9F67G_1783169494806Run:      RUN_01KWKV7XR52FESA0X4YJA9F67GVersion:  0.1Events:   2Chain:    PASSSignature: VALID (key f695..., embedded, not pinned)Timestamps: 1 1 warning(s):  ⚠ [SIGNER_UNPINNED] signature is valid but the signing key is not pinned; pass --key/--trusted-keys to prove WHO signed
From a real run on our scratch organisation. Key id shortened by the CLI. The closing RESULT line, PASS with 2 events verified, left out.
  • Chain: PASS: every event re-hashed and every link matched. Change one byte of one event and this fails.
  • Signature: VALID, not pinned: the bundle was signed and the signature checks out against the key inside the file. The warning is honest: a key carried in the file proves the file was not changed after signing, not who signed it. Pass --key or --trusted-keys with a key you already trust to prove that too.
the events
quox volt inspect run.jsonBundle: BDL_RUN_01KWKV7XR52FESA0X4YJA9F67G_1783169494806 SEQ  EVENT TYPE                  ACTOR               HASH (first 12)───────────────────────────────────────────────────────────────────────────   1  run.started                 user                f2ed6efd762c…   2  aee.envelope.sent           user                24a6a7548413… 2 events total
From a real run on our scratch organisation. The Run header line left out.

Quox checked the run on the server. Then you downloaded the same run and checked it on your own machine, with no trust in the server needed for that second check. Both agree: two events, chain intact.

An intact chain is not the same as a certified run. quox governance cert for-run <runId> shows which tier the run reached and why; Read what a certificate proves walks through it.

Nothing to undo on your Quox: fetching and verifying only read. Delete the downloaded file when you are done.