Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:40:20 UTC

E.21:1 - Problem frame

Use E.21 to evaluate the quality of an authored FPF pattern edition or bounded version for a named use. Its result can guide ordinary practitioner use or supply input to authoring, landing, release, external review, high-assurance reuse, canonization or another stated pattern-quality use. E.21 declares the characteristic space, evaluation specification and result rules. The evaluator applies the questions to that edition or version under the required ClaimScope.

If the pattern fails the required use, the result episteme states repairBeforeUse, holdForArchitectureDecision or refreshNeeded. A different use needs its own evaluation frame and cannot rescue the original 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 form the aggregate result episteme.

floorEvaluation changes only the declared floor and expected cost of obtaining evidence. An E.21 result retains the required ClaimScope, full coordinate set, rationales, and PrecisionRestorationProfile. Evaluate fragmentary, ill-formed or weak pattern text under the required scope. For an established weakness, record low coordinate values, repair status, an architecture hold or refresh, as applicable.

What goes wrong if missed. Reviewers can mistake taste, checklist closure, source count, review or landing state, or text length for pattern quality. 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 provides. The result makes one scoped, non-arithmetic PatternQualityQBundle claim about one exact pattern edition. It gives the complete coordinate set, evidence basis, adjacent-value rationales and a visible stop, repair, hold or refresh status.

What the evaluation is about. Its primary EntityOfConcern is 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 the dated-Work account in E.21:4 and CC-E21-0 only when a later claim needs a dated assessment-Work account.