The record between audits.
Why agent logs the audited system can edit do not answer E015.4, what a sealed record is, the four commands an auditor runs against a public log Verdict does not operate, and what the record does not show.
Run the check yourself: the sample and the four commands · the workpaper package · download the film (MP4)
Transcript
- 0:00 · THE QUESTION
Every agent your client runs will be questioned. By an auditor this year. By a regulator, or a court, later. And the first question is always the same. What did it do, and can anyone check that without taking the company's word for it?
- 0:17 · THE GAP
Most agent logs cannot answer that. They are written by the system being audited, stored where that system can edit them, and read after the fact. Under AIUC-1, requirement E015 asks for logs of what the agent did. Its supplemental control, E015.4, asks for something harder. Logs that are tamper-evident and independently verifiable.
- 0:46 · A SEALED RECORD
A Sealed Evidence Record is one step, sealed when your client's system sends it. The input, the output, the model, the review state and the time, hashed into a single commitment. That commitment is posted to Sigstore Rekor, a public log that Verdict does not run.
- 1:04 · THE CHAIN
When a person approves the next step, that record carries the first one's commitment inside its own hash. Step two cannot have been written before step one existed. Edit step one, and the link breaks.
- 1:18 · THE PUBLIC SAMPLE
Here is the public sample. A credit model recommends withdrawing a loan offer. A lending officer checks with the employer and approves a smaller amount instead. Fictional case. Real seals. Two entries on the public log, dated the fourteenth of October.
- 1:37 · FOUR COMMANDS
An auditor checks it in four commands. Clone the open verifier. Fetch the two records. Take Rekor's key from Sigstore's own repository, not from the log being checked. Run the check. Each record ends the same way. Content self-consistent, and anchor confirmed.
- 1:58 · WALK THE CHAIN, THEN TRY TO BREAK IT
Then walk the chain. Step two names step one. The steps run one to two. The records commit to a length of two, and two are present. Change one character, and it fails. Drop a record, and it fails. Swap the order, and it fails.
- 2:17 · WHAT IT DOES NOT SHOW
What it does not show, because you will ask. Who signed. The public sandbox uses a one-time key that names no one. A fork. A second record sealed off the same predecessor. And anything the system never sent to be sealed. Those stay with the team you audit, and the package says so.
- 2:37 · THE WORKPAPER PACKAGE
So we wrote the auditor's side. A reading guide. Eleven test procedures, with the negative controls. A specimen workpaper, run on the twenty-seventh of October, with the verifier's actual output. An evidence request list for the team you audit. And the limits, on their own page.
- 2:58 · HOW IT LINES UP
It lines up with E015.1 as example log entries. With E015.4 as hashing anchored to a log that nobody in the engagement runs. Partly with E015.2, the approval event linked to the step before it. And it supports D003.4, the human approval control, which became core in the October release.
- 3:25 · THE LOOP
That is the loop. The agent acts. The system sends the step, and it is sealed and logged in public. The team keeps the record. The auditor checks it against the log, not against the team. An insurer or a regulator can run the same check on the same record later, without calling anyone. Certification says the control existed. The record shows what was sent, and when.
- 3:51 · FREE TO RUN
Everything in the package is free to run. No account, no fee, and no trust in Verdict required. It is at verdict dot systems, slash A I U C dash one. Run it on a record from a team you audit, with their consent, and tell me what does not reproduce. Shayne Beavan answers every request himself.
Sources and limits
Control names and status are from standard.aiuc-1.com, October 15, 2026 release. The sample case LN-30417 is fictional; its two seals are real, on Sigstore Rekor at log indices 3247822463 and 3247822472. The commands were run end to end on 27 October 2026.
Images were generated for this film. The voice is synthetic narration. AIUC-1 is a standard of the Artificial Intelligence Underwriting Company. Verdict is not affiliated with or endorsed by AIUC, is not an accredited AIUC-1 auditor, and certifies no one. Also on film: The Record (3:22).
