E.21:4.4 - RequiredPatternQualityCoordinates
For every conforming E.21 result, an admitted evaluator U.System applies the evaluation specification to every coordinate, and the result episteme states every coordinate value and rationale.
| Coordinate | What it evaluates |
|---|---|
WorkingSituationAndUseBoundaryRecognizability | Whether the reader recognises the situation, intended use, practical gain or harm, first move, and action boundary early, plus any grounded non-use distinction that a plausible intended reader needs here. |
EntityOfConcernAndClaimScopeStability | Whether the primary EntityOfConcern and quality-claim scope stay stable across title, Problem frame, Solution, cases, checklist, relations, and status. |
PatternApplicationGuidance | Whether the Solution gives usable pattern-application guidance after the first move is recovered. |
ClosureAndBoundedNonUseRecoverability | Whether stop, repair, return, and reopen conditions are recoverable, together with any concrete defining, constraining, testing, or restoration contribution assigned to another pattern and any locally grounded non-use boundary. |
SemanticKindAndNameRecoverability | Whether names, kinds, relations, qualifiers, and claim boundaries recover the same FPF interpretation. |
NeighborAuthorityAndBoundedUseFit | Whether evidence, assurance, measurement, naming, work, gate, decision, publication, release, and project claims use the pattern content that actually defines or constrains each claim, relation, or boundary. Each outside claim names the concrete contribution used from that pattern and stays within the declared receiving use. |
EntityOfConcernPrimacyAndSemioBiasResistance | Whether the pattern leads with its own EntityOfConcern, first useful move, practitioner action, and practical delta instead of letting auxiliary description, source, evaluation, projection, or reference apparatus take over. The PrecisionRestorationProfile supplies the collapsed diagnosis across its six layers. Lower the value when that apparatus competes with the pattern’s positive subject and action guidance; semio-bias is the special case in which publication or representation material displaces them. |
PracticalUseDeltaAndHarmPrevention | Whether the pattern changes a real reader use, prevents a named misuse, reduces a named cost, or preserves a named boundary. |
UseAffordabilityAndApparatusProportionality | Whether ordinary first use stays affordable and heavier apparatus appears only when it buys admissible use. |
RepairLocalityAndChangeImpactPredictability | Whether repairs have the smallest locus and predictable downstream impact. |
ProxyForValueSubstitutionResistance | Whether the assessment question and coordinate-result rationale state what became worse when visible quality coordinates improved, and keep any use of a visible quality value, metric, review result, or release cue as practical value under an exact E.13 application/result. |
ClaimJustificationTraceabilityCurrentnessAndReplayability | Whether the claim is replayable from pinned text, scope, evidence, currentness basis, limitations, status, and stop reason. |
CaseCountercaseAndTransferCoverage | Whether positive cases, near-misses, anti-cases, and transfer cases match the breadth claimed. |
MaturePatternParityAndSelectedContentSufficiency | Whether selected mature-pattern ingredients are present in the body or related patterns for this EntityOfConcern and use. |
SoTABindingAndCurrentness | Whether the pattern’s positive SoTA claim satisfies the canonical definition and comparison contract in E.8:11 and binds that selected answer into exact pattern loci. Source identity/currentness, officiality, prevalence, and praise are supporting context and cannot raise this coordinate; an official source may still win from its substantive answer. |
FormalClaimAdmissibilityAndLensFit | Whether measurement, scale, comparison, formal model, simulation, causal, mathematical, QL, or learned-lens claims are admissible for their stated use, connected to the pattern content that defines, constrains, or tests their admissibility at the precision the claim needs, or correctly absent. |
FalsifiabilityAndLoweringCondition | Whether coordinate values, status, and stop claims say what would raise, lower, or reopen the evaluation. |
CorpusEntryProjectionAndEcologyFit | Whether README scenarios, ToC query cues, Preface cues, E.11 entry-distribution loci, including worked comparisons, cards, summaries, retrieval snippets, durable names, relations, and corpus ecology preserve the scoped quality result without becoming authority-bearing publication faces, stale echoes, or pattern content. Corpus-entry and projection evidence belongs in the E.21 result, E.19 run record, README, ToC, E.11, retrieval or card publication locus, or other quality evaluation locus unless the pattern of concern’s own EntityOfConcern and user-facing action are that projection or evaluation work. |
EvolutionFrontAndRefreshDiscipline | Whether variants, fronts, archives, refresh windows, and smallest-reopen rules preserve open-ended evolution without endless polishing. |
Constraint, harm, safety, security, compliance, deontic, self-application, recursion, and high-assurance questions do not add a second coordinate family. Evaluate them through the applicable coordinate for that content: related-pattern authority, traceability, formal-claim admissibility, falsifiability, affordability, corpus ecology, evolution, or refresh.
Coupled-flow unity and separation for pattern quality. Use this account when the declared quality use needs the relation between development, use, evaluation, and repair flows. Dated E.21 assessment work evaluates one exact PatternOfConcernRef inside a development, refresh, or admission flow. Another flow may make the same pattern a pattern of concern for a different use relation, for example a practitioner selecting and using it, a reviewer applying it to another text, or subsequent assessment work reopening it. One TransformationFlowStructure may join pattern development, pattern use, use-found evaluation, and repair or refresh flows through transfer, feedback, return, edition-change, or projection relations only when every included valuation or internal portion resolves to that same TFS and structural boundary. Independently identified TFS values and relations across their boundaries use E.18.NET. Keep three positions distinct in each sentence: the pattern as concern of the current flow, the intended reader addressed by the pattern, and the pattern’s own primary EntityOfConcern inside its Problem, Solution, or guidance. E.21 and E.19 are specifications; dated assessment and review work are the checking operations; handoffs, ledgers, README, ToC, E.11, retrieval outputs, and landing evidence are distinct records, publications, or evidence loci in the development/evaluation flow. Those objects may support edits to the pattern, but they are not automatically user-facing content for the reader addressed by it. DesignRunTag stays on the subject-context, claim, work, trace, publication-form relation, or source relation inside the transformation-flow structure; recover currentness, obsolescence, development, and use from their own relations. In pattern development, use quality-loop evidence to guide separately performed repairs and keep that evidence in the evaluation record.