Repository navigation
v5.4.0 — The One Where It Stops Talking Like a Robot
What this release is about
Your brain stops interrupting you to ask things you would never have wanted to be asked, and says the rest in words you can read.
Ask your brain to tidy your notes and, until now, it came back with a list of findings in its own vocabulary — dangling links, orphans, frontmatter issues — and then asked you, one prompt after another, whether it could fix each of them. Somebody who had asked for their notes to be tidied got five questions in a row about machinery they had never heard of.
That was a deliberate choice, and it was the safe one: nothing should rewrite your notes behind your back. What it missed is that the questions are not all the same question. "This link says capacity-managment and your note is called capacity-management — may I fix the spelling?" is not a decision, it is a chore. "Shall I create a page for this person?" really is yours, because the page becomes your notes' own answer to who exists.
So this release sorts them. What is obvious and undoable gets done. What is small and reversible is announced once, in a single message you can stop. What actually shapes what your notes mean is still a question — and it now says what is at stake before it lists the options. What makes the first two safe is not optimism: every change lands in your own history, so anything done without asking is one undo away.
What you get
When you ask your brain to tidy your notes (/lint)
- 🧹 A link that is plainly a typo is simply repaired.
[[capacity-managment]]whencapacity-managementis sitting right there: one candidate, no judgement, nothing to decide. If two notes could plausibly be meant, it does not guess — that one goes in the message below. - 📋 The small tidy-ups arrive as one message, and your move is to stop it. "I'm about to do 4 things: … Say stop if you'd rather I didn't — otherwise I'll go ahead." Not four prompts, not a question mark: saying nothing is a perfectly good answer, and it is the one most people want.
- ❓ What is genuinely yours is still asked — and it says why it matters first. Creating a page for a person your notes mention, settling a contradiction between a note and a page: those stay questions, and the question now opens on what it costs you rather than on a list of options.
- 🗣️ The report is written in your words. "Links pointing at a note that does not exist", "Notes nothing links to", "Pages your newer notes have moved past" — where it used to say dangling links, orphans and stale entity pages. And the one finding that costs you answers rather than tidiness now says so plainly: a note the engine can no longer read still answers your searches, with what it said months ago.
When you ask it to fold your recent notes into your pages (/consolidate)
- 🧾 It proposes the whole batch at once, and one reply is enough. "I've drafted 4 pages from your recent captures — 2 new, 2 refreshes." Accept some, decline others, in a single answer; it does not come back candidate by candidate to re-confirm what you already said.
Every time a conversation starts
- 👀 The opening screen stops showing you the notes your brain writes to itself. Instructions meant for the brain — how to phrase an offer, which command to run, which word never to use in front of you — were reaching your screen word for word. What is left is the handful of facts that are actually about your notes.
- 🕰️ It stops telling you it is up to date when what it means is nothing was newer when I last looked. Your brain checks for a new engine once a day; a release published a few hours after that check used to read as "up to date (checked today)". It now says which it is, and gives the clock as well as the day.
- ↩️ Nothing it does on its own is a one-way door. Every change it makes is saved into your own history the moment it happens, so undo is always available, including for the things it did not ask about.
What you have to do
Ask your brain to update its engine (/update-engine), then restart Claude once. Your notes, your keys, your constitution and the skills you tailored are left alone, as always.
Under the hood
The unit of this release is the gesture, not the string, and that is what gave it an end. "Rewrite every message" has no bottom: there are ~3 700 lines of delivered skills and ~1 400 of constitution, and nobody can say when they have been audited. A gesture — a point where the brain asks, announces or acts on a person — is countable. The audit produced maintainers/registers/gestures.md: 62 gestures across 9 surfaces, 13 to change, 46 already right. And the count said something the plan had not expected — ten of the thirteen live in two places, the opening screen and /lint, which are exactly the two surfaces the field report named. Three quarters of the product was already at the tier the doctrine would give it, so this is two repairs rather than a sweep.
The doctrine is ADR 0043, accepted in v5.2.0; this release is the application it explicitly opened and did not do. Its gate is reversibility first, then confidence, and the tier belongs to the gesture, never to the skill — which is why /lint now spans all three tiers on its own. The middle tier is built once, in the engine (lib/batched-announcement.mjs), rather than reinvented per skill, and two of its properties are pinned word for word: the message says silence proceeds and asks nothing (no question mark, no "shall I"), and a gesture whose write would escape auto-commit may never ride the batch. The net is what buys the tier.
The opening screen: the July diagnosis was inverted, and the wrong reason had a live cost. A field report last July said the leak was an echo of what the brain relays. Re-measured two independent ways — the host's own renderer, and a live probe on a throwaway folder — the truth is the other way round: the channel we believed was the safe one is precisely the one printed to the owner. The fix made at the time was right under either reading, so nobody re-opened it, and four more emitters kept routing directives into that channel afterwards. All six now carry an assertion that what a person reads contains no instruction to the model. A right fix built on a wrong reason does not generalise.
The guard, and what it deliberately cannot do. lib/owner-facing.mjs decides the one honest subset of a wording rule that a machine can decide: a banned literal in a string the engine prints. It states its three blindnesses in its own header — it sees printed literals only, never a sentence composed at runtime; it cannot tell whether the replacement is any clearer; it judges a string, never a channel. ADR 0043 is explicit that no guard can judge whether prose is plain, and this one does not pretend to. A sweep runs every printed report through it, over a fixture with every section filled, so a section added later is covered the day it is written.
It was wrong once, and that is the test that matters for a checker. It read [[people/ada-lovelace]] as an internal routing marker, because a line opening on a bracket is how the engine addresses its own dispatcher — but a [[link]] is the reader's own notation, the thing they type in their notes. A guard that is wrong about the most ordinary string in the product is a guard someone switches off. Doubled brackets are exempt, with tests in both directions so the carve-out cannot quietly empty the rule.
Mutation pass, run over everything the release wrote — the two new modules whole and the changed ranges of the six files altered: 98.11 % and 100 %, one survivor left and it is a named equivalent (details). The interesting half is not the number: nine of the nineteen first-pass survivors said the new checker was tested only on what it catches — its allow-list of ordinary acronyms was entirely unasserted. Six more were answered by deleting production that could not change an answer.
The update path was rehearsed on a copy of a real brain installed at v3.5.0, before the tag: it converged to this release, 530 engine files were swapped, and the owner's own files came back byte-identical. The rehearsal only ever reads an original — the copy is taken without its history, so a push home is not even expressible. It earned its place by finding something no test in the repo can see: on a brain that has crossed several releases, an engine skill can stop receiving updates and the report explains it as "your customized skill was kept exactly as you wrote it", about a file nobody opened. The new version does land beside it and nothing is lost. A brain installed normally is unaffected — verified on the same brain with its two copies made equal again. Filed as #115 with the reproduction rather than patched in a hurry the night before a release.
Two of these came from the owner reading his own screen, the morning of the tag, which is the only test this class of defect has. The first is the status line above: the measurement was correct and the sentence was not. It said "up to date" — a claim about the world, in the present tense — when all the brain holds is a claim about its own memory, and the date alone read as "checked today" when the probe had run five hours before the release existed. Both halves are wording, and both are fixed: the verb says it is a memory, the stamp carries the clock. UTC is named rather than converted, because a line that renders differently per machine cannot be asserted by a test.
The second is one thing with two names, which this release elsewhere spends its whole argument against. The product calls a retrieval scope a universe, in both locales; the prose beside it called the same thing a sphere — in the v5.3.0 note above all, which the update prompt quotes back verbatim. Corrected in the two printed strings that carried it, in the published v5.3.0 note, and added to the word list the printed-report sweep runs on, so a new one trips a test rather than a reader. What the ban does not cover is the word's other job: saying what kind of thing a universe is (an employer, a client, a personal sphere) is a definition, and it stays.
The marketing surface was re-read whole, and one promise had gone from true to half-true the moment /lint started repairing an obvious typo on its own: "propose fixes you confirm (never a silent rewrite)", written in three places. It now describes the three tiers and names the net. EN-QUOI-C-EST-DIFFERENT.md: re-read, nothing moved.
Closed by this release: #79, and the plain language half of #62.