E.21:1 - Problem frame

Use this when an authored FPF pattern edition or bounded version must be evaluated for quality under a named use: ordinary practitioner use, authoring input, landing input, release input, external-review input, high-assurance reuse input, canonization input, or another explicit pattern-quality use. E.21 declares the characteristic space, evaluation specification, and result rules. An evaluator applies the quality questions. The evaluator does not replace the required ClaimScope with an easier one. If the pattern fails the required use, the result episteme states repairBeforeUse, holdForArchitectureDecision, or refreshNeeded; a different use needs a different evaluation frame and does not rescue this result.

Not this pattern when the evaluated object is one DRR, an FPF-level corpus object, a single wording repair, a source-use decision, or a project-side evidence, assurance, gate, release, safety, compliance, work, or decision claim. Use E.9.DA for a DRR, E.2.DA for an FPF-level corpus object, F.19 for a wording repair, and the pattern governing a source-use or project-side claim for that claim. Open E.10 or a named precision-restoration neighbor for an unresolved FPF-specific meaning.

First useful move: name the exact pattern edition, required use and scope, working reader, and qualification window. Read its working situation, first useful move, practical delta, boundaries, and evidence. Then assign every coordinate an evidence-based value with an adjacent-value rationale and constitute the aggregate result.

floorEvaluation changes only the declared floor and expected evidence economy. An E.21 result retains the required ClaimScope, full coordinate set, rationales, and PrecisionRestorationProfile. Fragmentary, wrong-shaped, or weak pattern text is still evaluated under the required scope; weakness receives low coordinate values, repair status, architecture hold, or refresh status.

What goes wrong if missed: pattern quality becomes taste, checklist closure, source count, review state, landing state, or length. Short patterns can pass while missing mature content; long patterns can pass while hiding the first user-facing action; semio material can take over a non-semio pattern.

What this pattern buys: one scoped, non-arithmetic PatternQualityQBundle claim about one exact pattern edition, one complete coordinate set, explicit evidence basis, adjacent-value rationales, and a visible stop, repair, hold, or refresh status.

Primary EntityOfConcern in plain terms: one exact authored FPF pattern edition or bounded version checked under one declared quality scope and qualification window. Keep the quality questions, evaluator, coordinate claims, aggregate result, evidence use, any admission decision, and later repair distinct. Use Solution item 5 and CC-E21-0 only when a later claim needs a dated assessment-Work account.