The Unaddressed Widow/Orphan Hard Fail

The briefing pack states it plainly: "No Widow-Orphan is a hard rule with no enforcement gate" and "Every failure required manual detection." This is not a soft preference that needs calibration. This is a known hard-fail condition that the studio catches only when a human reviewer happens to look closely enough.

Three explicit violations appeared in the Prax Health retrospective: the landing page shipped with four confirmed widows, the UI kit had an orphaned "appointment." in a checklist card, and the empty-state patients screen carried a "datasets." widow in body copy. Each one was flagged during QA review, after the artifact was already rendered and submitted. None were prevented upstream.

The enforcement gap is documented in `doctrine/rules/ENFORCEMENT.md` under "Gap" status. The rule exists. The consequences are defined. The detection mechanism does not. This creates a condition where fundamental typographic quality is dependent on manual oversight rather than systemic prevention, and manual oversight scales poorly when the studio is running multiple surfaces in parallel.

The pattern is clear: hard rules without enforcement gates become manual audit checklist items. Manual audit checklist items get skipped under time pressure or when reviewers assume the pipeline already caught them. When that happens, violations ship, and the craft bar drops incrementally until someone notices the accumulation and flags it as a systemic problem.

The solution is not more vigilant manual review. The solution is to add validation code that checks rendered text for widow and orphan conditions before the artifact reaches QA. This moves the enforcement gate upstream, where it belongs, and converts a known failure mode into a preventable one. Until that gate exists, every QA pass on body-copy-heavy surfaces carries the risk of missing a hard-fail condition that should never have reached review in the first place.