GH-1 A broken rule leaves prose

A rule that the project has seen broken MUST be enforced by a guard or a gate that reads what the rule governs, not left in prose alone.

Field	Value
Keyword	MUST
Level	2
Checked	by judgement
Findings	F300, F1, F5, F6
Harness facts	none
Threat	internal: the researcher wrote the tool that moved several of these rules
Status	active

Rationale: in Shio and freewilly a rule stated only in prose was measured broken, each time by the repository that stated it: Shio's roadmap lines ran to 142 words under a one-sentence rule, and freewilly's writing skill forbade the em dash while the pinned commit added two to the README (F300, R3/S3). A budget on the every-turn file stated in prose did not stop it growing about nineteenfold, while a gated one held (F1); planning prose outran an instruction to be brief until a limit was refused at write time (F5); a writing rule without a lint did not keep the em dash out (F6). Shio's index states the principle: "A rule nobody can check is a preference, so" [shio@821f18d74:agents.md#L229]. The rule is conditioned on a breach seen, because no project records an agent breaking the rules its guards were written against before they were written (see the open questions). A check that reads a typed copy of the rule rather than the governed text reproduces the fault (F7), so the check reads what the rule governs.