06 / Historical archive
Notes from inside the tunnel.
These essays preserve the project’s pre-release thinking. They contain superseded framing and do not supply current metrics, status, or authority.
The Service Manual Nobody Wrote
The story starts with a Bitcoin worry, an unreasonable language test, and the first glimpse that the missing thing was not only a spec. It was a way to keep many readers from losing the same truth.
2026-04-24Part 02The Night the Agents Ate the Spec
Before Rosetta Bitcoin had a proof machine, a smaller system showed the dangerous promise: agents could move like a swarm if the spec, tests, and human intent stayed in the same loop.
2026-04-25Part 03The Fog Machine
The first antagonist was not code. It was the fog that rises when agents, chats, plans, and generated artifacts all pretend to remember the same project.
2026-04-26Part 04The Static Labyrinth
The first serious technical path produced schemas, generated files, and projections that looked authoritative. That was the warning: a beautiful map can still become a maze.
2026-04-27Part 05The Oracle Needed a Ledger
The project became calmer when durable local state started carrying the cards, decisions, risks, roles, and boundaries that chat and generated files could not be trusted to remember.
2026-04-28Part 06Evidence Is Not Authority
The project only became serious when it accepted that tests, ports, cards, and evidence can sharpen questions, but cannot speak for Bitcoin or outrun maintainer review.
2026-04-29Part 07The Witness-to-Claim Spine
The project began to move again when it narrowed the machine: witness behavior, derive a claim, share a vector, replay it in ports, preserve lineage, and leave every step inspectable.
2026-04-30Part 08The Language Tribes
The 25-language escapade was the attempt to push agent swarms across an absurd range of languages, then learn which assumptions only became visible when the work left its native tongue.
2026-05-01Part 09The Artifact Brought Back
The deepest result may be the working pattern that emerged: agentic kanban as a field discipline for keeping humans, agents, state, tests, and evidence aligned over long arcs.
2026-05-02Part 10Why the Repo Opens Last
The repo opens last because the journey turned ambition into restraint: the public can receive the story, but the evidence room belongs first with reviewers who can correct it.
2026-05-03