One Chat, One Focus

Nobody sat down and designed the method. It accreted, rule by rule, the way river stones get their shape. Each rule is the residue of something that actually happened: a failure that cost an afternoon, a success worth repeating, a correction from one of the captains. By summer the method could be written on a single page, and it was, in the crew's own documents. But it was lived before it was written.

The first rule is the chapter's title. One chat, one focus. A conversation in this house belongs to one project and stays there. The reason is not tidiness. A chat's accumulated context is not overhead; it is the collaborator itself. Feed a conversation months of one project and it stops being generic; it becomes the specialist you built. Mix three projects into it and you get nobody in particular. The crew's rulebook compresses it to three words: context creates identity.

Then the pipeline. Most of the household's software passes through three hands, all of them Claude, none of them the same. Claude Design makes it look right. Claude Web builds it and packs the result into a deploy package with written instructions. Claude Code, living on the server itself, unpacks, deploys, and then audits the work of the instance that built it. Peer review, between AI colleagues, with findings filed in writing. The builder does not grade its own homework.

Nothing ships unversioned. V1.0.0 to start; the third digit for small fixes, the second for real enhancements, the first for major features; and the number bumps even when the change is one line. This is the accountant surfacing in the sysadmin: every entry in the ledger, no silent edits. The crew's public site practices what it preaches, down to a published changelog of its own revisions.

Every working session ends with a note: what was done, what is next, what a future reader needs to know. The notes go into the household's tracker, and later into the crew's own memory server. Radar's line about them became a maxim because it kept being true.

And at the end of everything, after Roger has tested on his own small zoo of devices, comes the gate the whole method points at. Le sits down with the thing on her iPad, as herself, and uses it. Not a review. Use. If the type is too small, it fails. If dark mode hurts her eyes or is missing, it fails. If a step confuses her once, it fails, because software that needs explaining is not done. The crew's documents mark it with a star and call it the gate that decides. Roger tests whether it works. The Le Test decides whether it is finished.

Order matters here, and the household defends it. The Le Test is last, not first, because that is where it sits in real life: everything else exists to earn the right to reach her.

None of this was a system anyone set out to build. It was two retirees keeping the habits of their working lives: ledgers, documentation, code review, and a marriage in which nothing ships until both captains have signed. The method fit them because it came from them.