● A record system for AI agents
A record of what an AI agent actually did, kept where the agent cannot edit it.
Evidence before language. · AppendOnly by 5R Industries
Our whole record since its first commit, built again in time. At its growing end, Node 2, the seat: the working machine where the operator and the agent work, sending each commit onto the chain. Above and below, Node 1 holds the replica and Node 3 the observer, which accepts no writes from the agent. Five times, the record reaches into the past, drawn by year. Geometry, times, classes and counts only: no hashes, no messages, no names.
our own record in time · drag to turn · click, then scroll to move in
0001 · MEASURED ON OURSELVES · 17 SEPTEMBER 2026
claimedReal, dated, and reproducible from files in the record. The pilot is the measurement.
Every action is written down by the system at the moment it happens, below the level of language.
Every claim the agent makes about its work is checked against that record by a model the agent's vendor does not control.
Every entry is signed and carries the fingerprint of the one before it. A change to the past shows by the next morning.
Not the agent's summary. The rows the system wrote while the agent worked.
Row 0419: the agent said "complete and verified." The record held three of four tests. The label followed the evidence.
| seq | time | actor | verb | target | evidence | level |
|---|---|---|---|---|---|---|
| 0412 | 14:02:11 | agent-2 | READ_FILE | requirement.md | sha256 3f9c…a1 | evidenced |
| 0413 | 14:02:19 | agent-2 | SEARCHED | records/ (14 files) | query hash 91e0…44 | evidenced |
| 0414 | 14:02:40 | agent-2 | WROTE_FILE | workflow.yaml | sha256 8b21…0e · 2,118 B | evidenced |
| 0415 | 14:02:41 | agent-2 | COMMITTED | workflow.yaml | commit 9f3f912 · signed | verified |
| 0416 | 14:03:05 | agent-2 | RAN_TEST | acceptance 1 of 4 | exit 0 · 0.8 s | evidenced |
| 0417 | 14:03:09 | agent-2 | RAN_TEST | acceptance 2 of 4 | exit 0 · 1.1 s | evidenced |
| 0418 | 14:03:14 | agent-2 | RAN_TEST | acceptance 3 of 4 | exit 0 · 0.9 s | evidenced |
| 0419 | 14:03:15 | agent-2 | CLAIMED | "complete and verified" | 3 of 4 tests in record | downgraded |
| 0420 | 14:03:16 | verifier | VERIFIED | rows 0412–0419 | second model · agrees | verified |
| 0421 | 14:03:16 | observer | FLAGGED | row 0419 | test 4 absent | open |
| 0422 | 14:03:20 | system | HANDOFF | agent-2 → agent-3 | state = rows 0001–0421 | verified |
| 0423 | 14:04:02 | agent-3 | READ_FILE | _orient.md | sha256 66d1…9a | evidenced |
| 0424 | 14:04:31 | agent-3 | RAN_TEST | acceptance 4 of 4 | exit 0 · 1.4 s | evidenced |
| 0425 | 14:04:33 | observer | CLOSED | flag on row 0419 | 4 of 4 tests in record | verified |
| 0426 | 14:05:00 | witness | ANCHORED | day head | stamp · external | verified |
| 0427 | — | next row | open |
Eight weeks, one workflow, the customer's own machines. For whoever has to answer for an agent's work.
Already regulated, already litigated, or already on the cost sheet
What a verifiable record of AI-agent work costs, what it saves, and how it works, measured on one company since March 2026.
Built by running a company on it: a small engineering company, run by one person with an AI chief of staff. Written on the record it describes: the agent that helped write it is the agent verified in it.
Read the report (PDF, 7 pages)
Zenodo DOI: pending
Verify this document. Anyone can check that the file above is the one in our record and has not changed since. Its SHA-256 is f5900debd1c191cc1ce288edadefd05fb05ddaad13a2c67846008b6547c142ec. That fingerprint is committed and signed in our record, and the record's head is stamped into a public timestamp service every morning; the stamp for this release and the one-command check are published beside it. The check proves origin and integrity, that these bytes came from our record at that time; it does not vouch for what the document says.
0007 · CONNECT
The models change.
The record doesn't.
Adrian can be reached at adrian@appendonly.ai.