The auditor’s side of E015,
written down and run.
A scoping step and eleven test procedures for AIUC-1 requirement E015 and the control it supports, D003.4, where the audited team seals agent decisions as Sealed Evidence Records. Every command was run end to end on 2026-11-12 against the public sample on /aiuc-1, with the verifier at ser-spec commit 17c9c8f. Free to run: no account, no fee, and no trust in Verdict required.
The files
Version 1.1, 2026-11-12. Each version keeps its own address, so a file you have already hashed never changes under you.
- Verdict-E015-Workpaper-Package.pdf →PDF, 13 pages · 379 KB. Reading guide with the audit-process notes, a scoping step and eleven test procedures (TP-00, then TP-01 to TP-11), a specimen workpaper re-performed on 12 November 2026, an evidence request list, the limits and the version history.SHA-256 93b6d215e9cd87749ec3a843647a7c785ace5e1dc67c2a89e926b09b3f30fd95
- Verdict-E015-Test-Matrix.xlsx →Spreadsheet · 15 KB. The procedures as a fillable matrix, the specimen results, the evidence request list, a verdict summary per requirement, and the sources.SHA-256 8302cb664c229e99a784af6010bc13bb90fac21d1e6c542e5542eab308e6384a
- Verdict-E015-Workpaper-Template.docx →Word document · 39 KB. The same procedures with blank result and sign-off cells, the Statement of Applicability line and a verdict table.SHA-256 5365cf690231f5aaead95335b35edc664aca75f5ce65e8bc3b50fa9b12d3e214
- Verdict-E015-Evidence.zip →Zip, 16 files · 24 KB. The specimen's evidence folder: the two records, the Rekor entries, Rekor's public key, the evidence map, seven run logs and a SHA-256 manifest.SHA-256 c54fe4729f51bf788f00fa9b49c468575ad9b103a3f60b4120e5fadfab327668
The procedures
- TP-00 Scope, independence and tool provenance (the scoping step)
- TP-01 Obtain the records
- TP-02 Offline self-consistency
- TP-03 Independent anchor check
- TP-04 Chain walk
- TP-05 Negative controls
- TP-06 Approval event
- TP-07 Completeness of capture
- TP-08 Storage and retention
- TP-09 Signer identity
- TP-10 Display fields
- TP-11 Standard currency and re-performance
The specimen records PASS for TP-01 to TP-05 and TP-10, the role-only limit under TP-06, and the signer limit under TP-09. TP-07 and TP-08 do not apply to a public sample.
E015.2 and E015.4 are supplemental controls, so TP-00 begins with the Statement of Applicability: the integrity procedures reach the audit report where the team has opted in. A procedure result is an input to the auditor’s verdict on the requirement, never the verdict. Where the procedures sit in an AIUC-1 audit →
Versions
- TP-00 starts from the Statement of Applicability and records whether E015.2 and E015.4 are opted in.
- “Period” now reads “dates in scope”, because an AIUC-1 audit is point in time.
- Results map to AIUC-1’s per-requirement verdicts, and TP-11 records the version fixed at kickoff.
- E015.2 names the approver-identity limit and agent provenance metadata. D003.3 has its own row.
- The specimen was re-performed on 12 November 2026 with the same results, one file reference is fixed, and the evidence folder is published as a zip.
The SHA-256 list of these four files was itself sealed: record ser_d23eec25d475e2c43726cbc2cbd43a10, Sigstore Rekor log index 3828920751, logged 2026-11-12T08:43:57Z. Its output_hash is the SHA-256 of the four-line list. A passing check shows the four hashes existed no later than that log time. It does not show who sealed them.
curl -sO https://verdict.systems/aiuc-1/workpapers/seals/ser_d23eec25d475e2c43726cbc2cbd43a10.json && python3 ser-spec/tools/verify.py ser_d23eec25d475e2c43726cbc2cbd43a10.json --anchor --rekor-key rekor.pem- Verdict-E015-Test-Matrix.xlsx →SHA-256 e60d7ca4658164e7b1322a11d9d798abfab84f4360122aae0d32f7f4db602cda
- Verdict-E015-Workpaper-Package.pdf →SHA-256 da7ab165e951016b21e21d04345eeeff015367f488a5e00387237941e3b3723e
- Verdict-E015-Workpaper-Template.docx →SHA-256 d3b64c0f3dd315d2f7a11bec5564d8164ebd5602009c2b7d33ab5cc2b1d9136d
The SHA-256 list of these three files was itself sealed: record ser_100211b2071777ac904282a3d7f942be, Sigstore Rekor log index 3572625337, logged 2026-10-29T17:34:11Z. Its output_hash is the SHA-256 of the three-line list. A passing check shows the three hashes existed no later than that log time. It does not show who sealed them.
curl -sO https://verdict.systems/aiuc-1/workpapers/seals/ser_100211b2071777ac904282a3d7f942be.json && python3 ser-spec/tools/verify.py ser_100211b2071777ac904282a3d7f942be.json --anchor --rekor-key rekor.pemRekor’s key comes from Sigstore’s own repository: https://raw.githubusercontent.com/sigstore/root-signing/main/targets/rekor.pub
What it does not show
Who made a record (the public sandbox signs with a one-time key), who approved (an approval record names a role, not a person), a second record sealed off the same predecessor, and anything the audited system never sent to be sealed. Section 05 of the package states each limit and what it means for the engagement.
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. Control names and status are from standard.aiuc-1.com, October 15, 2026 release, read on 2026-11-12. Check the current standard before relying on this package. Defects: founder@verdict.systems.

