The Record Does Not Change: what a verifiable record of AI-agent work costs
A 12-page report details the costs and savings of maintaining a verifiable record of AI-agent work within a small engineering company. The study, conducted since March 2026, features a one-person operation utilizing an AI chief of staff to manage operations. The findings and supporting evidence are publicly available through a Zenodo deposit with a pending DOI.
- ▪The report measures the cost and efficiency of a verifiable AI-agent record in a company run by one person with an AI chief of staff.
- ▪An evidence bundle dated September 28, 2026, allows for independent verification of the record's history since September 9.
- ▪The full report and system details are deposited at Zenodo under DOI 10.5281/zenodo.23042774.
- ▪The first public release of the text version occurred on September 29, 2026, superseding an earlier version from September 25.
- ▪The agent that assisted in writing the report is the same agent verified within the record.
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,914 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Appendonly |
| Canonical URL | https://appendonly.ai/ |
| Publication time | Tue, 29 Sep 2026 20:07:06 +0000 |
| Retrieval time | 2026-09-29T20:07:33.928Z |
| Last seen | 2026-09-29T20:07:33.928Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | PeVuqS82HM8m · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
The Record Does Not Change. 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, 12 pages) The evidence bundle that lets anyone check the record's history since 9 September was not rebuilt: bundle-2026-09-28.zip, with a one-command check inside. Part C, the case study of one afternoon run on the record, follows once the filing that covers what it adds is on the record.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Appendonly.
Discussion
0 commentsMore from Appendonly
