E.21:2 - Problem
FPF patterns need an evaluation that goes beyond a style checklist while requiring less work than a project assurance audit. Earlier review habits produced two opposite failures:
- Too weak. A reviewer marks a pattern “ready” because no blocker is obvious, because it landed, or because headings exist.
- Too heavy. A reviewer adds more warnings, evidence cards, source rows, boundary notes, and process residues until the pattern becomes harder to use.
E.21 addresses both failures by evaluating the quality of the pattern on every required coordinate. The coordinates ask whether the pattern is usable, coherent, current, precise, affordable, mature enough for its claim, and safe from proxy improvement.