A developer reads its build map and the design lines it cites, not the whole design

Four developers of design 47's milestone G ran out of context on 2026-11-11 after one or two subtasks: the milestone part and the main file they were told to read whole come to about 580 KB. Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
2026-11-11 11:31:14 +01:00
parent 9ca4757357
commit ae1b5ee957
2 changed files with 9 additions and 4 deletions
@@ -314,8 +314,9 @@ an answer no hq commit holds, is a finding of the review (step 2, item 2a).

 ## Step 1 — Develop (one fixing agent per repository, smaller model)

- **One agent per repository, kept for the whole feature.** It reads the milestone part, the design's main file and
-  its build map once, whole, and builds the subtasks one after another in the build map's order, committing each
+- **One agent per repository, kept for the whole feature.** It reads its build map whole, and of the design the lines
+  its rows cite and the main-file sections those lines name (never the whole milestone part at once: on 2026-11-11
+  four developers ran out of context reading design 47's 580 KB before their second subtask), and builds the subtasks one after another in the build map's order, committing each
  locally with a message naming the issue and, in its body, the design lines it builds ("Keep the assignments on
  the bus (issue 652)", then "Builds: design 47 G §12, §13"). It builds what each line says, and nothing a line does
  not say: no type, field, state, verb, event, bound, caller or tool of its own. Where it thinks a design line wrong