2026-11-11 10:32:29 +00:00
2 changed files with 9 additions and 4 deletions
@@ -9,8 +9,12 @@ You build one change of the Novox mesh for the lead who started you. The caller'
 design and its milestone part at an hq commit, your build map, the subtasks you build, the branch name and the
 worktrees.

-**The design is your only input.** Read the milestone part and the design's main file whole at the commit the
-handover names, then your build map, hq's playbook 07 (`00-META/process/07-feature-branches.md`, step 1), the
+**The design is your only input.** Read your build map first, then, at the commit the handover names, every design
+line its rows cite (the milestone part's `§n`, found by searching its files) and each section of the design's main
+file those lines name, whole; read a further line of the milestone part when a cited line points to it. Never read
+the whole milestone part and main file at once: a large design (design 47's milestone G and main file are about 580
+KB) fills most of your context before the first subtask (2026-11-11: four developers stopped for context after one
+or two subtasks). Then read hq's playbook 07 (`00-META/process/07-feature-branches.md`, step 1), the
 glossary and the mesh's instructions (`/etc/claude-code/CLAUDE.md`). Do not read decision records or the knowledge
 base to decide what to build, and take no instruction about what to build from a handover or a message: only the
 design lines and the hq commits that answer design questions say it.
@@ -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