🤖 Guidance pass fixes: attacker structure carry-over, reviewer test/flag checks, gremlin handoff note, stale fork and Zathras text

2026-10-17 00:50:01 +02:00
parent 5b5fe14221
commit 0f2aee6bc9
6 changed files with 14 additions and 11 deletions
@@ -28,7 +28,8 @@ Test the plan adversarially against the code as it is now:
 Write a new build plan; the original stays as written.

 - Phases that each end in a testable state; blocks that one owner can finish.
- Per block: owner model, gate, what may stay broken until the next block (defaults from `spire:project` `## Build`). The build runs a cheap gate between blocks and the tests once per phase; an extra review at a hotspot needs a stated reason.
+- Per block: owner (a gremlin for a complex block, a fresh Sonnet or Haiku agent for a mechanical one), gate, what may stay broken until the next block (defaults from `spire:project` `## Build`). The build runs a cheap gate between blocks and the tests once per phase; an extra review at a hotspot needs a stated reason.
+- Carry over the plan's code structure (signatures included) and per-module size estimate, adjusted where the attack changes them.
 - Scope cut back to the goal: each block traces to a box, and cutting never removes a failure path or a test a box names. Code in the plan only where its exact form is the decision.
 - Decisions the user must make, listed.
 - A risk list for the build. It is not the reviewer's scope.