Receipts
"At the frontier" is a claim, and a claim needs receipts. Every number on this site is listed below with the file, test run or commit history it comes from, a label, and when it was pulled. The labels: measured (counted, source named), recorded (taken from a stored report or an earlier run, not re-run for this page), approximate (rounded or partial, said so), estimated (a judgment, not a count), declared (a plan, not a result). Numbers I can't source yet don't appear anywhere. When a number changes, this table changes first. Last full refresh: 29 October 2026; rows that date an event keep the event's date.
| Claim | Figure | Source | Label | As of |
|---|---|---|---|---|
| Software projects on the builds page, by status word | 12: 6 live or shipped, 2 in development, 4 parked | each build page's own status word; aggregate in evidence/2026-10-09-portfolio-aggregate.md §2, re-checked §6 |
Measured | 2026-10-29 |
| Automated tests across those projects, measured or recorded counts summed | more than 8,000 (8,894; 7,530 without LEGION's internal packages; 11,227 if a parked project's own recorded counts are included) | per-project evidence files, full runs today for Sadyr and Content Ops, static counts elsewhere; aggregate §1 and §6 | Approximate: methods and dates differ per project; stated as a floor | 2026-10-29 |
| Commits across the seven projects that keep git history (four do not) | about 1,100 (1,132) | git rev-list --count HEAD per repo; aggregate §6 |
Measured | 2026-10-29 |
| Content Ops: versioned releases since July 2026 | 23 minor versions + 7 point releases (0.1.0 → 5.13.3); no release since 27 September | git log, docs/changelog.md, v4/v5 roadmaps; aggregate §3 |
Measured | 2026-10-29 |
| Content Ops automated tests passing (TypeScript) | 995 of 995 | state/repo-state.md, full run today at commit 5f831e4 |
Measured | 2026-10-29 |
| Content Ops automated tests passing (Python) | 57 of 57 | state/repo-state.md, same run |
Measured | 2026-10-29 |
| Sadyr: automated tests | 3,051 passing, 1 skipped, 0 failing, across 24 packages | pnpm -r test in the Sadyr repository, full run today at commit 9d0364f |
Measured | 2026-10-29 |
| Sadyr: architecture decision records | 17 | products/sadyr/docs/adr/ |
Measured | 2026-10-29 |
| Sadyr: structure | 3 apps, 17 packages, 155 commits | filesystem and git log, claims ledger C-03 |
Measured | 2026-10-29 |
| Sadyr: recorded evaluation runs | 78 | state/repo-state.md, Sadyr Evaluation |
Measured | 2026-10-29 |
| Sadyr: latest standard evaluation battery | 172 of 202 cases passing | state/repo-state.md, Sadyr Evaluation, run 20260929-1544 against the live Adroit deployment |
Measured | 2026-09-29 |
| Sadyr: approved public documents it answers from on Adroit's site | 24 (26 more approved and held back) | Content Ops knowledge rollups for the Adroit client; manifest B-02, claims ledger C-04 | Measured | 2026-10-29 |
| Sadyr: working demos (not yet sold as a product) | 2 | claims ledger C-05 | Measured | 2026-10-29 |
| LEGION: capability packages | 64 across five folders | state/repo-state.md, filesystem inventory, claims ledger C-11 |
Measured | 2026-10-29 |
| Game in development: gameplay C++ / automated-test C++ | 127,191 / 90,188 lines | game development-stats collector, re-run today over the repository | Measured | 2026-10-29 |
| Game: documentation per line of production C++ | 1.27 lines | same collector run | Measured | 2026-10-29 |
| Game: commits | 610 | git rev-list --count HEAD |
Measured | 2026-10-29 |
| Game: prompts in the two weeks that hold about 75% of the production C++ | 157 (about 53,000 typed characters) | dev-stats report + git blame coverage check, claims ledger C-14 |
Measured | 2026-09-21 |
| Game in development: product decisions recorded, all made by Todd | 250 | evidence/E-20; decision log in the game's repository |
Recorded | 2026-09-20 |
| Cadence: narration produced / GPU time / failed segments | 6.94 h / 98.2 min / 0 | Cadence generation manifests | Recorded | 2026-09-21 |
| Brain Vault: documents (synthesized + raw) | 1,765 (869 + 822) | aggregate count script, totals only | Recorded | 2026-09-21 |
| Adroit website rebuild: pages updated + pages created, now live | 74 + 17 | manifest B-03, claims ledger C-10 | Measured (event) | 2026-09-23 |
| Content Ops: planned website pages drafted in two days of batch runs | 92 of 95 | manifest B-03 / B-08, claims ledger C-08 | Measured (event) | 2026-09-09 |
| Adroit website: home page JavaScript before → after (compressed) | 103 KB → 2 KB | manifest B-03, claims ledger C-10 | Measured (event) | 2026-09-09 |
| Adroit website: plugins retired for native theme code | 8 | manifest B-03, claims ledger C-10 | Measured (event) | 2026-09-09 |
| Content Ops: production defects found and fixed the same night | 3 | manifest B-08, claims ledger C-09 | Measured (event) | 2026-09-08 |
| Sadyr: first commit to production | 12 days (63 commits on 8 working days) | Sadyr git log, claims ledger C-01 |
Measured (event) | 2026-06-30 |
| Revenue-operations rebuild for a national amateur sports league | 7 systems into 1, about 2,400 teams, 6 weeks, 0 rollbacks | claims ledger C-12 (client anonymized) | Measured (event); team count approximate | 2026-09-21 |
The working-habits receipt
The numbers above measure what got built. For how it got built (sessions, friction, what the tooling itself says about my working patterns), see what Claude Code's report says about how I work.