Derive the directories beside the six, rather than counting them twice [#322]

README.md

@@ -69,13 +69,17 @@ that the boundary is visible in the tree and not only in a document:
 `src/server/`, `src/session/`, `src/cache/`, `src/artwork/`, `src/playback/` and
 `src/measurement/`.
 
-Three directories beside those six are not concerns from that record and say so in
-their own first paragraph. `src/failure/` holds the error vocabulary the six map
-onto, `src/diagnostics/` holds the sink a client supplies, and `src/clock/` holds
-the one source all three clocks reach the core through, because
-[0102](docs/decisions/0102-the-clocks-every-deadline-is-measured-against.md)
-states a rule per clock and a reading taken anywhere else would be a deadline no
-test can move.
+Every other directory under `src/` is not a concern from that record, and each one
+says so in its own first paragraph with the reason it sits beside the six rather
+than inside one of them. Which directories those are is read out of the tree
+rather than counted here:
+
+    git grep -l 'not one of the six' -- src/
+
+A reader who wants the reason opens the file the command names, where the
+sentence and the reason are in the same paragraph. Naming them here instead put
+one count in this file and a second one in `src/lib.rs`, and both of them were
+wrong the moment a directory landed without either paragraph being opened.
 
 What each type is, and the statement about which thread a client may call it from,
 is written where a reader meets the type; `tests/thread_statements.rs` is what
@@ -86,12 +90,18 @@ next landing:
     git ls-tree --name-only origin/main src/
 
 THIS PARAGRAPH COUNTED TWO DIRECTORIES AND SAID THERE WAS NO BEHAVIOUR IN ANY OF
-THEM. There are three, and the claim that none of them holds behaviour stopped
-being true of this tree. It was written when the tree held none; `src/lib.rs`
-carries the correction for the sentence it made about the same thing, and this
-file was not brought into step with it. Both errors ran in the direction that
-makes the tree look emptier than it is, in the first file anybody reads about this
-repository.
+THEM. It was written when the tree held none; `src/lib.rs` carries the correction
+for the sentence it made about the same thing, and this file was not brought into
+step with it. Both errors ran in the direction that makes the tree look emptier
+than it is, in the first file anybody reads about this repository.
+
+THE REPAIR THAT REPLACED TWO WITH THREE WENT STALE THE FOLLOWING WEEK, WHICH IS
+WHY THERE IS NO NUMBER HERE NOW. That repair landed on 2026-08-29 and
+`src/lifecycle/` arrived on 2026-09-02, in a change about the core's own lifetime
+that had no reason to open this paragraph, and the count stood at three until
+somebody counted the tree by hand. A number in this
+file is read by nothing that would have said so, so the count is gone rather than
+corrected a second time.
 
 ## What the gate builds for, and what nothing here covers
 

src/lib.rs

@@ -17,7 +17,8 @@
 //! | [`playback`]      | tracking playback position                    |
 //! | [`measurement`]   | producing measurements                        |
 //!
-//! Three more modules are here and none of them is one of the six. [`failure`] holds
+//! The modules beside those six are not among the things 0003 names, and each of
+//! them says so in its own first paragraph rather than only here. [`failure`] holds
 //! the error vocabulary the other six map onto, which 0003 places inside
 //! "reaching a server" and which every one of them uses; splitting it out is a
 //! layout choice rather than a boundary claim. [`diagnostics`] holds the sink a

src/lifecycle/mod.rs

@@ -1,5 +1,10 @@
 //! Creating the core, stopping it, and a host that suspends it.
 //!
+//! This is not one of the six things 0003 names. Its subject is the core itself
+//! rather than anything between a server address and a decoded byte, so it sits
+//! beside the six rather than inside one of them. The record is 0115 and the
+//! issue is #115.
+//!
 //! `docs/decisions/0115-creating-and-stopping-the-core.md` decides all three and
 //! `docs/decisions/0009-the-concurrency-model.md` carries the shape underneath
 //! them. What is here is the part of both that a value settles: what a client