Make the cost of reading the code a goal, and answer to a reader panel each PR

2026-09-20 22:45:22 +02:00
parent 0d627d2b11
commit 3dc1cf82f1
2 changed files with 10 additions and 0 deletions
@@ -839,6 +839,12 @@ the Development section below, and who ships a register the four above then draw
    nothing, each on its own path. A fixture that looks nothing like production
    tests nothing; the caller who needs a value that can touch nothing asks for it
    by name.
+13. **A cold reader lands in the right place** — the code is judged on what it costs
+    to read, not only on what it does: reaching the unit behind a symptom without
+    asking a person, changing one piece without holding the rest, a layout whose
+    names tell the truth, and a file that stands with no second document open beside
+    it. A simulated reader panel scores those four, the score is a ratchet no release
+    lowers, and [`AGENTS.md`](AGENTS.md) says how each pull request answers to it.

 ## Decisions