While v32 was on the cabinet, David Friedrich rewrote the notes on the cabinet.
landed as “The game is hostile on purpose and the people are not” — 09 August 2026
what changed
XXXIIchapterv32
David Friedrich09 August 2026 · 18:39
David taught the flight records to climb down off the splash screen and into the field, so the first thing waiting for him out there is his own 15170, in pieces, with his name on it.
landed as “The flight above yours is adrift out there, and it pays to carry it”
While v32 was on the cabinet, David Friedrich rewrote the notes on the cabinet.
landed as “The game is hostile on purpose and the people are not” — 09 August 2026
While v32 was on the cabinet, David Friedrich changed the rules.
landed as “The two tools that would not run” — 09 August 2026
The rules themselves were altered: No rule text moves here. The two files live under the rules mark, so setting their mode reads as one - and the honest way through that is the line, not a quieter path around it.
While v32 was on the cabinet, David Friedrich changed the rules.
landed as “The crew gets its button back” — 09 August 2026
The rules themselves were altered: main no longer requires an approving review. The crew resumes merging its own generated paperwork, which is what it did before the requirement existed.
While v32 was on the cabinet, David Friedrich changed the rules.
landed as “The crew files the book and leaves the button to you” — 09 August 2026
The rules themselves were altered: main requires one approving review. The crew cannot approve its own paperwork, so it stops merging it and leaves the merge to a person.
While v32 was on the cabinet, David Friedrich rewrote the notes on the cabinet.
landed as “The front door is written for somebody who has never been here” — 09 August 2026
While v32 was on the cabinet, David Friedrich changed the rules.
landed as “The numbers on the front page are counted, not typed” — 09 August 2026
The rules themselves were altered: tools/badges.sh paints the README strip from the history - the versions, the roster, the arsenal, the sealed tapes, the rules and the licence - and nobody edits one by hand, for the reason nobody edits the ledger. The post-commit hook and the book workflow run it where the tally already gets refreshed. The notes stylesheet also learned that a run of images with no blank line between them is a badge strip and belongs in a row.
While v32 was on the cabinet, David Friedrich changed the rules.
landed as “Rename asks the branch, not the desk it is sitting on” — 09 August 2026
The rules themselves were altered: tools/branch.sh --rename read only the working tree, and the tree is clean exactly when a rename is wanted - the work is committed, that is why the name is wrong. It reads what the branch holds since it left main as well now, and says which other marks it is passing over.
While v32 was on the cabinet, David Friedrich changed the rules.
landed as “A branch says what it is about before anybody opens it” — 09 August 2026
The rules themselves were altered: Branches go in a directory and the directory is the mark - the same nine words the flight strip puts on the pull request and the book puts on the chapter, so one change wears one word from the branch to the chapter. tools/branch.sh reads it off what has changed rather than asking anybody to type it, takes the loudest when there are several, and --rename fixes a branch cut before its author knew what it would hold. chronicle.sh --marks --all hands out the vocabulary, because a second copy of those nine words is a second opinion waiting to happen. Untracked files now count in both readers: a feature here is a new file (GR3), so the commonest branch there is used to read as being about nothing.
While v32 was on the cabinet, David Friedrich changed the rules.
landed as “The fixture was reading the wrong repository over its own shoulder” — 09 August 2026
The rules themselves were altered: tools/lockstep.sh clears git's exported environment in every subshell that enters the fixture except one - the line that asks --version. A commit hook exports GIT_DIR, chronicle.sh prefers it to the directory it was called in, and so that line compared a count of 8 taken from the fixture against v32 taken from the repository the hook was running in, and called it a disagreement. LOCK is a red line, so there was no override, and .claude/worktrees/ is a documented place to work: the effect was that taking a worktree quietly made it impossible to commit. Verified both ways - green under a hook's environment now, and still red when --version is made to lie.
While v32 was on the cabinet, David Friedrich changed the rules.
landed as “The map still described the labels the cabinet stopped using” — 09 August 2026
The rules themselves were altered: Completes the two commits before it. The architecture note for tools/labels.sh still listed the eleven kindof() buckets and said the tool read them, which stopped being true when it started asking chronicle.sh --marks. Nine marks now, and the note says the tool classifies nothing itself.
While v32 was on the cabinet, David Friedrich changed the rules.
landed as “Two things the memory knew that the first pass left behind” — 09 August 2026
The rules themselves were altered: Completes the previous commit. The pinning a kraken needs to sit still for a picture went to /shoot, and backing your own hunks out before a peer commits went to the shared-tree paragraph - both were in the memory being replaced and neither made the first pass.
While v32 was on the cabinet, David Friedrich changed the rules.
landed as “The things only one machine knew are in the cabinet now” — 09 August 2026
The rules themselves were altered: Five working agreements and two pieces of craft were being kept per machine, so a second developer or a second clone got none of them and had no way to know they existed. They belong here: who pushes and opens a pull request (the referee at the keyboard, not the pilot - a command handed over to be pasted is a chore rather than a decision, and it crowded out the one line that needed an answer), that several sessions share this working tree and must say so before touching a shared generator, closing a browser you drove, and the improvements notebook that keeps a candidate until somebody spends a rule-change commit on it. The two pieces of craft get skills: rehearsing the ownership rules from another seat through git's environment goes to /referee, and staging a frame from the console - trails need motion and shapes need stillness, and the grapple has to be led - becomes /shoot, which is the twenty minutes the media/ nudge keeps asking for.
While v32 was on the cabinet, David Friedrich changed the rules.
landed as “A pull request now wears the same marks its chapter will” — 09 August 2026
The rules themselves were altered: The labels on a pull request were mirroring kindof(), which answers where a path sits and is drawn from for the plate art. The marks answer what a commit moved, and those are the badges the book actually prints on a chapter. Two vocabularies, both defensible, disagreeing about src/render/ on every pull request that touched it. markof() and markname() move into the shared library, --marks is the handle on them, and tools/labels.sh asks rather than keeping a table of its own. Eleven buckets become nine. The ground crew's paperwork now wears nothing at all, because the book gives its own pages no mark and inventing one for the strip would be the same second opinion in a new place.
Drop a coin in this one: git checkout 84359a28