E.21:4.7 - Finding and proposal rows

E.21 finding:
  Pattern of concern: <PatternOfConcernRef>
  Coordinate or status affected: <all coordinates affected by this repair, and status or stop when affected>
  Pattern locus: <section, row, example, relation, source row, projection>
  Value or status effect: <value, status, floor, or stop impact>
  Correction direction: <what should change>
  Closure test: <what changed pattern text would show>

When E.22, E.23, returned-finding absorption, or exceptionalImprovementEvaluation asks for improvements, cover every below-floor coordinate with a finding and add proposal rows only for substantive non-dominated improvement opportunities inside the declared scope. Record one finding for one independently repairable defect; its Coordinate or status affected field names all affected coordinates, while each coordinate keeps its own value and rationale. A receiving E.22 typed proposal retains its one-coordinate interface; coordinate-specific proposals may share one correction description and closure test.

Do not treat every value below 5 as a defect. For above-floor coordinates, the evaluator still searches by value when exceptional improvement is requested, but the proposal must name a content improvement such as stronger positive action guidance, a worked slice, case or countercase, source-currentness carry-through, mature-content discharge, relation cleanup, deletion of displaced apparatus, split of overloaded content, or another content gain. When ending improvement at the current values, give one aggregate no-proposal or stop disposition showing why further substantive change is dominated, unavailable, or outside scope. Cite the checked loci and relevant coordinate rationales; keep independently different reasons recoverable within that disposition.