capteames.com/receipts · public · updated 30 July 2026

The Ledger

The receipts behind “The $2 Billion Echo” — an Off Leash newsletter issue. Every claim below was counted on the machine itself and is checkable.

The claim being backed: before Thinking Machines published their manifesto on July 10, 2026, this server was already running all three of its pillars — a specialized brain per organization, a system that condenses what it learns, and a human’s judgment on every trigger. Not claimed: priority over the ideas. Claimed: independence, with timestamps.

The counts

627
commits before July 10
2,074
commits to date
35
repositories
30
services live now

How they were counted — summed across every repository on the box, recounted 30 July 2026:

for repo in */; do
  git -C "$repo" rev-list --all --count --before=2026-07-10T00:00:00
done   # summed → 627

git rev-list --all --count      # summed across repos → 2,074
pm2 jlist                       # 30 processes, 30 online

Recounted 30 July 2026 by the same method as the first count on 26 July. The pre-manifesto figure came back 627 again, unchanged — which is the point of a dated record: the past doesn't move. What moved is everything after it (1,799 → 2,074 commits, 33 → 35 repositories, 23 → 30 services live). Run the commands above yourself; that's what they're printed for.

The dated receipts

Real commit lines from the ledger, oldest first. Git history can’t be edited backwards without breaking every hash that follows it.

2026-06-14 58fdb5e
Initial commit: Global Pulse v4 Cloudflare Worker
The first line of code ever pushed. Day zero.
2026-06-19 988237c
Phase 1 WIP: fix correction.ts false-positive bug, header validator, safe-append concurrency handling
Week one already ships a header validator and safe-append protocol; the same commit’s tree carries a build lock — going live requires a deliberate code change, not an environment-flag flip. Writes default to a sandbox.
pillar: human judgment on every trigger
2026-06-25 8822f25
chore: initialize n120ka ops project and audit structure
Adds docs/business-rules.md, dated that day: the system audited every codebase and wrote its operating rules down — including an 11-step verified-append protocol (confirm → validate headers → verify target row empty → snapshot → write → snapshot again → compare) and the build lock preserved as doctrine.
pillar: condense what you learn
2026-06-26 54f5806
docs: add independent N120KA audit
A second AI with zero prior session context audited the whole stack cold — static analysis, git history, HTTP probing — and filed its findings into the same ledger.
pillar: condense what you learn
2026-07-02 28de766
fix: exact passenger match in /api/trips, drop [client] fallback — stops cross-person trip bleed
Fuzzy matching bled one person’s trips into another’s view; the fix became doctrine — exact match plus an explicit alias table, no substring matching, no shared state between tenants. (One word redacted: a client’s name.)
pillar: a specialized, isolated brain per organization
2026-07-05 4606572
feat(voice): tap-and-talk flight control — mic pill + voice sheet (webkitSpeechRecognition, TTS read-back, yes/no confirm listen), rule-based parser, book/change/cancel through existing endpoints
The voice interface ships with a spoken yes/no confirmation before any booking lands.
pillar: human judgment on every trigger
2026-07-05 0c034a8
feat(wheel): midnight guard — 12:00–4:45 AM times need a second confirming tap (amber note, button becomes ‘Keep 12:15 AM’)
Even the time-picker distrusts a plausible-looking mistake and asks a human twice.
pillar: human judgment on every trigger
Why the repositories are private: they run a real flight operation and real client work, so they stay closed. Nothing here is a screenshot of a screenshot, though — every hash above is a real commit, and the full logs (git history, process list, the dated rules files) will be shown to anyone who asks: tim@capteames.com. Client names are redacted and marked where they appear.