🤖 Guidance pass D4: drop general knowledge and filler from read-only agents, workpad, research

2026-10-17 00:32:05 +02:00
parent fc6a543162
commit fa80d26309
11 changed files with 28 additions and 140 deletions
@@ -27,8 +27,6 @@ After the plan is written, a fresh agent that did not write it **tests it advers

 A plan written before earlier phases landed may be stale. The attack checks it against the code as it is now; it reads the previous phase's run log and review only when something is off.

-This step is what pays for dropping per-task review. A plan checked against the code catches in minutes what many small reviews would find one by one, or not at all. Without it, lean is just less review.
-
 The build plan sets defaults: block size, owner model per block, the gate per block, what may stay broken between blocks. It may place an extra review at a hotspot if it says why. Its risk list shapes the build. It is not the phase reviewer's scope: a reviewer handed a checklist tends to confirm the checklist.

 A plan holds decisions, the code structure, contracts, invariants and the scope fence. Code goes in only where its exact form is the decision (a schema, a wire format, a state machine, the main signatures): every line of code in a plan becomes an obligation for the build. Whatever tool wrote the plan, the attack is the same.