FPF Pattern-Quality Evaluation CharacteristicSpace

E.21 · Stable · Pattern · Part E - The FPF Constitution and Authoring Guides

About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Pattern Status: Stable

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.

Relations

E.21builds onFPF Authoring Conventions & Style Guide

E.21builds onPattern Quality Gates: Review and Refresh Profiles

E.21builds onQ-Bundle: Authoring "-ilities" as Structured Quality Bundles

E.21builds onMeasurement & Metrics Characterization (MM‑CHR)

E.21builds onA.CHR-NORM — Canonical “Characteristic” & rename (Dimension/Axis → Characteristic)

E.21builds onCharacteristicSpace & Dynamics Hook (A.CHR‑SPACE)

E.21builds onLocal-First Unification Naming Protocol

E.21builds onEvaluation CharacteristicSpace Construction

E.21coordinates withImprovement-Oriented Quality Evaluation Question Framing

E.21coordinates withQuality Improvement Loop Method

E.21coordinates withDRR Decision-Adequacy Evaluation CharacteristicSpace

E.21coordinates withFPF Pillar-Adequacy Evaluation CharacteristicSpace

E.21coordinates withUnified Lexical Rules for FPF

E.21coordinates withOntology-First Plain Technical Rewriting

E.21coordinates withRelational Precision Restoration — Recovering Direct Relations from Under-Specified Claims

E.21coordinates withEpistemic Precision Restoration

E.21coordinates withFirst-Practical Entry and Pattern-Use Discoverability Discipline

E.21coordinates withExpanded Entry Disambiguation Cases

E.21explicit referenceDRR Decision-Adequacy Evaluation CharacteristicSpace

E.21explicit referenceFPF Pillar-Adequacy Evaluation CharacteristicSpace

E.21explicit referenceOntology-First Plain Technical Rewriting

E.21explicit referenceEvaluation CharacteristicSpace Construction

E.21explicit referenceThe Agential Role & Agency Spectrum

E.21explicit referenceSystemRoleAssignment and Performed-Work Attribution Check

E.21explicit referenceU.Episteme: Constitution, Empirical Grounding, and Edition Relations

E.21explicit referenceEvidence Graph Referring (C-4)

E.21explicit referenceTrust and Assurance Calculus

E.21explicit referenceStatus Families Mapping (Evidence • Standard • Requirement)

E.21explicit referencePattern Quality Gates: Review and Refresh Profiles

E.21explicit referenceQuality Improvement Loop Method

E.21explicit referenceU.Mechanism - Reusable Law-Governed Operation Declaration

E.21explicit referenceCharacteristicSpace & Dynamics Hook (A.CHR‑SPACE)

E.21explicit referenceFirst-Practical Entry and Pattern-Use Discoverability Discipline

E.21explicit referenceExpanded Entry Disambiguation Cases

E.21explicit referenceQ-Bundle: Authoring "-ilities" as Structured Quality Bundles

E.21explicit referenceImprovement-Oriented Quality Evaluation Question Framing

E.21explicit referenceU.Work: Dated Performed Work Occurrence

E.21explicit referenceU.Method: Reusable Way of Doing with Explicit Applicability

E.21explicit referenceUnified Lexical Rules for FPF

E.21explicit referenceWording-Use Ontological Precision Restoration Architecture

E.21explicit referenceLocal-First Unification Naming Protocol

E.21explicit referenceOntic Candidate Detection and First-Use Disposition

E.21explicit referenceOntic Description and Publication Discipline

E.21explicit referenceU.Signature - Reusable Law-Governed Declaration Episteme

E.21explicit referenceRelation-Declaration Slot Discipline - SlotKind, ValueKind, RefKind, and participant-designation discipline

E.21explicit referenceRelational Precision Restoration — Recovering Direct Relations from Under-Specified Claims

E.21explicit referenceMathematical Lens Use

E.21explicit referenceSystem-Role–Method–Work Alignment

E.21explicit referenceTelemetry-Driven Refresh & Decay Orchestrator

E.21explicit referenceMeasurement & Metrics Characterization (MM‑CHR)

E.21explicit referenceA.CHR-NORM — Canonical “Characteristic” & rename (Dimension/Axis → Characteristic)

E.21explicit referenceA.CSLC-KERNEL — Minimal CSLC in Kernel (Characteristic/Scale/Level/Coordinate)

E.21explicit referenceQuality-Term Precision Restoration

E.21explicit referenceFPF Authoring Conventions & Style Guide

E.21explicit referenceSystem-Role Kinds and Assignments

E.21explicit referenceU.SystemRoleAssignment - Contextual System-Role Assignment

E.21explicit referenceEpistemic Precision Restoration

E.21explicit referenceCharacteristic and Scale Precision Restoration

E.21explicit referenceConstraint Validity for Transformation Steps

E.21explicit referenceGate Decisions from Independent Check Results

Content

Problem frame

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.

Problem

FPF patterns need a quality evaluation that is stronger than a style checklist and lighter 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 solves this by measuring the pattern of concern against one complete coordinate set. The coordinates ask whether the pattern is usable, coherent, current, precise, affordable, mature enough for its claim, and safe from proxy improvement.

Forces

Force	Tension
Comparability vs false precision	Pattern versions must be comparable, but ordinal qualities cannot be averaged.
Completeness vs affordability	Every coordinate is evaluated; rationale and evidence can stay compact.
Maturity vs length	A short pattern is mature only when selected mature-pattern ingredients are present in the body or neighboring pattern governing the claims.
Ontology vs usability	Names and kinds must be precise enough for the governed use without burying the first user-facing action.
Semio precision vs semio-bias	Episteme and publication distinctions matter, but non-semio patterns still lead with their own `EntityOfConcern`.
Open-ended improvement vs stop	Improvement can continue forever, while one version needs a scoped stop condition.

Solution

E.21 declares the FPF pattern-quality U.CharacteristicSpace, its object-specific A.19.ECS evaluation specification, ordinal scale, complete result-shape rules, the local non-arithmetic PatternQualityQBundle result payload, and local result-status meanings. An evaluator applies these questions to the pattern and assigns its coordinate values. Evidence use, assurance, admission, and later repair have their own objects and relations below.

For one pattern-quality evaluation, keep independently recoverable the objects and relations that the selected ordinary or Work-bearing form actually asserts:

one exact authored FPF pattern edition or bounded version as the checked object;
the declared ClaimScope, working reader, intended receiving use, qualification window, evidence basis, and evaluation configuration;
the selected U.CharacteristicSpace, this E.21 evaluation-specification episteme, every coordinate/scale binding, and the local result-form and status-value rules;
when exact Method identity or actual assessment Work is asserted, one separately identified semantic evaluation U.Method;
when actual dated assessment U.Work is asserted, first recover every evaluator-performer's A.13 core for the assessment action. A.15.1 then independently admits the Work from its performance history, enacted Method, temporal extent, and one obtaining locally declared relation to the containing U.System, under the exact system boundary and qualification window. Add F.6 only when the evaluation account also needs precise assignment-bound attribution, using the same obtaining A.13 assignment. A compact account may omit an identifier unused by the receiving claim only when every relation it consumes remains recoverable;
every coordinate-result claim, their same-bearer non-arithmetic PatternQualityQBundle ClaimGraph payload, and one C.2.1 aggregate pattern-quality-result episteme when a durable result is needed;
witnesses, comparator/source/case refs, exact A.10 evidence-use/provenance relations and bounded reliance results, and any B.3 result for an actual named assurance claim;
an optional evaluation-record episteme that packages those refs;
the local PatternQualityStatus value and any separate F.10 status use/interpretation, E.19 admission or refresh decision, project gate or authority decision, publication, and currentness relation; and
later E.23 improvement or other repair work and its changed pattern edition.

A.6.1 enters only when a separately admitted U.Mechanism declares the exact operation that was actually used and the receiving claim needs that application occurrence or its bindings. Then name the mechanism and operation and require that operation's ApplicationPredicate, ApplicationIdentityRule, ApplicationExtentRule, argument and result declarations, declaration-local binding predicates, exact application occurrence, and actual declaration-local bindings. Treat the checked pattern, configuration, coordinate results, and aggregate result as application inputs or results only when the operation declares those exact meanings and the corresponding bindings actually obtain. Otherwise omit PatternQualityEvaluationApplicationRef; the dated-Work and result accounts remain complete without it.

In the ordinary form, an admitted evaluator U.System applies the quality questions. A claim of dated assessment Work opens item 5; an A.6.1 application requires the independently satisfied operation condition above. Any local evaluator system-role kind and independently obtaining System-classification judgment are optional separate claims. Route unresolved source role through E.10.ROLE.

Each coordinate-result claim is one quality ascription about the exact checked pattern edition. It keeps recoverable the bearer, effective ReferenceScheme, characteristic, scale value, evaluation rule or probe, comparison or calibration frame when used, U.ClaimScope, intended use, qualification window, ordinary assessing action or exact declared-operation application when separately asserted, short rationale, and evidence locus. The complete same-bearer coordinate set forms the non-arithmetic PatternQualityQBundle payload carried by the aggregate result episteme. The evaluator system, evaluator viewpoint episteme if any, witness set, optional record, and receiving status or admission use remain separate.

One conforming two-level assessment-and-result shape applies:

configure the checked pattern edition, scope, use, reader, window, characteristic space and specification, and evidence basis; include the exact semantic evaluation Method only when its identity or actual assessment Work is asserted;
let the admitted evaluator U.System apply the specification; add item 5 only when the result deliberately asserts dated assessment Work, and add an A.6.1 application only when the compact conditional rule above is independently satisfied;
constitute every coordinate-result claim with ShortRationale and the aggregate result episteme;
assert the local PatternQualityStatus in that result;
state its stop, repair, architecture-hold, or refresh condition; and
when improvement is requested, return distinct finding or proposal claims without changing the coordinate result into a work plan.

If a pattern lacks frame, first move, source basis, mature comparison, or naming clarity, lower the relevant coordinates in the one E.21 result.

A bounded lexical, checklist, or automated smell screen may identify suspect loci and reduce search cost. Record the checked edition, covered defect family, and observed limits in EvaluationEvidenceBasis; the screen neither assigns a coordinate value nor establishes semantic completeness, practical use, or the aggregate result.

When candidate editions are compared, keep the declared use, reader, probes, and evidence conditions common where possible and expose missing or underrepresented evidence. This supports replayable comparison; it does not turn ordinal coordinates into one score or establish evaluator agreement that has not been studied.

An E.21 result evaluates one exact edition for one declared use. It does not validate the pattern universally. A stronger validation claim needs separately declared expert checks, observed applications or cases, or other fit-for-purpose research evidence. Missing actual-use evidence therefore caps only the coordinates whose stronger values require it.

Local names and kind settlement

Local name	Kind and function
`PatternQualityEvaluation`	Compatibility compound label for the configured evaluation package. Any use resolves to the exact characteristic space/specification, configuration, ordinary assessment or separately asserted dated Work, result episteme, witnesses/evidence-use relations, optional record, and exact declared-operation application only when the compact A.6.1 condition holds.
`PatternQualityCharacteristicSpaceRef`	Reference to the exact A.19 `U.CharacteristicSpace` whose slots are the required E.21 coordinates and whose bindings use the E.21 ordinal scale.
`PatternQualityEvaluationSpecRef`	Reference to this object-specific A.19.ECS evaluation-specification episteme: applicability, coordinate and scale meanings, evidence/missingness rules, calibration, result shape, local status meanings, and reopen conditions.
`PatternOfConcernRef`	Exact authored FPF pattern edition or bounded version named by value as the checked object, with its host path or monolith section and edition, commit, hash, or other pinned version basis recoverable. `PatternOfConcern` is relation-relative: the same pattern can also be the concern in another use, review, or evaluation flow. The evaluated pattern also has its own primary `EntityOfConcern`: the subject that its Problem, Solution, or guidance is about. FPF patterns are applied to situations, claims, texts, or work objects. Say that a pattern defines, constrains, tests, or supplies a repair for a claim, relation, or boundary only when its content actually does; use `related pattern` for a looser pattern relation and `relation` only for the relation itself.
`ClaimScope`	Quality claim boundary recovered from the governing frame: ordinary use, authoring input, landing input, release input, external-review input, high-assurance reuse input, canonization input, or another explicitly requested pattern-quality use. It is not chosen by the evaluator to make a failing request pass.
`WorkingReaderScope`	Working-reader family, viewpoint, and first-use situation the pattern must serve.
`IntendedUse`	Action that may use the result: continue drafting, admit for declared use, repair, refresh, or compare candidates.
`QualificationWindow`	Edition, SoTA, related-pattern, release, time, or comparison window in which the evaluation is current.
`EvaluationEvidenceBasis`	Checked evidence loci named by value for the evaluation: pattern body version, host or monolith section, README scenario, ToC row, `E.11` entry-distribution locus, `I.2` expanded entry-disambiguation case when corpus-facing, card or retrieval cue when claimed, the best-known-line comparison and source-role loci when SoTA is valued, source-identity/currentness traces when replayability or the qualification window needs them, mature comparator set when maturity is valued, and worked case or absence of worked case when case coverage is valued. Inclusion here is neither a witness claim nor an evidence-use relation.
`QualityEvaluationQuestionFrameRef`	`E.22` frame when purpose, floor, trade-offs, absorption, or proposal expectation needs to be declared.
`PatternQualityEvaluationConfiguration`	Local input tuple binding the exact checked pattern, scope, use, reader, and window, characteristic space and specification, question frame when used, and evidence basis, plus the semantic evaluation Method only when its identity or actual assessment Work is asserted.
`SemanticPatternQualityEvaluationMethodRef`	Reference to the exact semantic `U.Method` when Method identity or actual assessment Work is asserted. Exact assessment Work enacts that Method; the E.21 specification and coordinate table supply its evaluation questions.
`PatternQualityAssessmentWorkRef`	Used only when the evaluation asserts exact dated A.15.1 `U.Work`. Then the item 5 Work account applies. Add an application ref only when the separately admitted mechanism-operation condition is also satisfied.
`PatternQualityEvaluationApplicationRef`	Reference to one exact A.6.1 application occurrence admitted under one exact operation declared by a separately admitted `U.Mechanism`, together with its actual declaration-local bindings. It is present only when the compact conditional rule in E.21:4 holds.
`CoordinateValueRationales`	One result claim for every required coordinate: `Coordinate`, `Value`, `ShortRationale`.
`CoordinateEvidenceRefs`	Per-coordinate text, case, relation, SoTA, mature comparator, projection, or review refs where the short rationale depends on evidence outside the pattern body row being discussed. Reference presence does not itself establish a coordinate value.
`PrecisionRestorationProfile`	Compact quality summary of the `F.19` whole-span reading: `overallEffect`, `checkedLoci`, and `affectedCoordinates`. Optional issue-bearing fields in E.21:4.3a retain the six diagnostic layers: word, head, and use precision; phrase-level apparatus; repeated or distributed material; ontic and slot-relation clarity; description, publication, and source boundary separation; and pattern-application ontology. The profile collapses their findings into one scalar effect and the affected existing coordinates. A finding names the restoration locus or concrete pattern contribution needed; a clean result names its checked absence scope once.
`PatternQualityQBundle`	E.21-local non-arithmetic bundle-shaped ClaimGraph payload for one exact pattern edition, effective ReferenceScheme, `ClaimScope`, intended use, and qualification window. It contains the complete coordinate-result claims and rationales, `PrecisionRestorationProfile`, local `PatternQualityStatus`, stop or repair condition, reopen condition, and an optional grounded non-use boundary when a named competing use or plausible confusion makes that boundary material. The aggregate C.2.1 result episteme carries this payload; a general C.25 engineering `Q-Bundle` or another evaluation object remains separate.
`DominanceSet`	Coordinates used to compare already evaluated candidate versions. It never changes the required coordinate set.
`PatternQualityResultRef`	One C.2.1 result episteme whose EntityOfConcern is the exact checked pattern edition and whose ClaimGraph carries the same-bearer `PatternQualityQBundle`: declared use and window, every coordinate-result claim, `PrecisionRestorationProfile`, local status, stop or repair, reopen, and any grounded non-use boundary. Assessment work, witnesses, records, admission, and authority remain separate objects or relations.
`PatternQualityWitnessRefs`	Exact pattern loci, cases, comparators, sources, traces, or projection loci cited by result claims; witness presence is neither a value nor evidence use.
`PatternQualityEvidenceUseRefs`	Exact A.10 evidence-use/provenance relations supporting reliance on result claims.
`PatternQualityEvaluationRecordRef`	Optional C.2.1 record episteme packaging the current configuration, work or application, result, witness or evidence, reopen refs, and any grounded non-use boundary. Its function is reference packaging; status, admission, assurance, and authority use their direct relations.
`PatternQualityStatus`	Local admissible-use value asserted by the aggregate E.21 result episteme. It is not an E.19 admission or refresh decision; any F.10 status use or interpretation by a receiver is a separate relation.
`StopCondition`	Why improvement may stop, continue, refresh, or hold.
`ReopenCondition`	Change in evidence, use, source, or other stated premise that requires reconsidering the result.
`BoundedNonUse`	Optional non-use boundary, included only when an independently grounded competing use or plausible confusion changes the result's use.

Names are local to pattern-quality evaluation unless F.18 promotes a durable name. Each has only the direct function stated above; any later receiving use requires its own relation.

Evaluation configuration, application, result, and optional record

PatternQualityEvaluationConfiguration:
  PatternOfConcernRef: <exact authored FPF pattern edition or bounded version>
  ClaimScope: <declared quality claim>
  WorkingReaderScope: <reader and first-use situation>
  IntendedUse: <what may consume the result>
  QualificationWindow: <edition, source, neighbour, release, or comparison window>
  PatternQualityCharacteristicSpaceRef: <exact A.19 characteristic space>
  PatternQualityEvaluationSpecRef: <this E.21 specification edition>
  SemanticPatternQualityEvaluationMethodRef: <exact U.Method when its identity or actual assessment Work is asserted; otherwise omitted>
  QualityEvaluationQuestionFrameRef: <E.22 frame when used>
  EvaluationEvidenceBasis: <checked pattern, corpus, source, comparator, case, and projection loci; missing or unchecked loci named explicitly when they affect values>

When dated assessment Work is asserted:
  AssessmentWorkRef: <PatternQualityAssessmentWorkRef: the dated assessment U.Work independently admitted under A.15.1>
  EvaluatorSystemRefs: <every admitted U.System that performed AssessmentWorkRef>
  EvaluatorA13CoreBasisRefs: <for every precise performer, exact local agential kind and
    criterion, classification, same obtaining assignment, scope, working situation, window,
    and adequate core evidence; add a characteristic profile only when separately consumed>
  AssessmentTemporalExtent: <exact extent of W>
  WorkToSystemRelationBasis: <name one locally declared Work-to-System predicate and its
    obtaining relation for AssessmentWorkRef, the exact containing U.System, system boundary,
    and qualification window>
  EnactedMethodRef: <the exact A.3.1 U.Method enacted by AssessmentWorkRef>
  PreciseAssignmentAttributionRefs?: <only when the receiving claim needs exact
    assignment-bound attribution; for every performer cite the direct case fact that it
    performed AssessmentWorkRef under the same obtaining A.13 assignment, the declared
    assignment species and participant values, holder equality, the obtaining assignment
    predicate and interval, coverage of AssessmentTemporalExtent, and the resulting F.6 link>
  EvaluationConfigurationRef:
When an exact declared-operation application is also asserted:
  ApplicationAndBindingAccount: <the separately admitted mechanism, exact declared operation and application occurrence, and actual declaration-local bindings required by the compact A.6.1 rule in E.21:4>
PatternQualityResultEpisteme:
  EntityOfConcern: <same exact PatternOfConcernRef>
  EffectiveReferenceScheme:
  ClaimGraph:
    PatternQualityQBundle:
      ClaimScope:
      WorkingReaderScope:
      IntendedUse:
      QualificationWindow:
      PrecisionRestorationProfile: <E.21:4.3a compact quality summary; issue-bearing detail only when needed>
      CoordinateValueRationales: <all required coordinates, values, short rationales>
      CoordinateEvidenceRefs:
      PatternQualityStatus: <local result value>
      StopCondition: <local stop, first repair, hold, or refresh>
      ReopenCondition: <change that requires reconsidering this result>
      BoundedNonUse?: <only when an independently grounded competing use or plausible confusion changes the result's use>
  AssessmentApplicationRef: <PatternQualityEvaluationApplicationRef: exact A.6.1 occurrence ref only when the declared-operation condition holds; otherwise omitted>
  PatternQualityWitnessRefs:
  PatternQualityEvidenceUseRefs:
PatternQualityEvaluationRecord: <optional packaging of configuration, application or work, result, witness or evidence, reopen refs, and any grounded non-use boundary>

An unfinished table, prose summary, or record with missing coordinate claims remains assessment material. A complete E.21 result places every required coordinate claim in the result episteme; the objects named in E.21:4.1 retain their stated functions.

Ordinal scale, result row, and adjacent-value rationale

Value	Label	Meaning
0	`absent`	The characteristic is not expressed for the declared scope.
1	`namedOnly`	It is named or implied but not usable as quality evidence.
2	`partiallyExpressedForDeclaredUse`	It is present but incomplete, fragile, or insufficient for the declared use.
3	`sufficientlyExpressedForDeclaredUse`	It is usable for the declared scope, with limits visible.
4	`wellExpressedForDeclaredUse`	It is clear, evidenced, and bounded for the declared scope.
5	`exceptionallyExpressedForDeclaredUse`	It is exceptional for the declared use across reinforcing loci and cases, without hidden cost or neighbour loss.

Values are ordinal content evaluations. They are not U.Measures, averages, percentages, maturity-ladder steps, review votes, or landing status.

The result-bearing coordinate row has exactly this shape:

Coordinate	Value	ShortRationale
`<E.21 coordinate>`	`<0..5>`	`<assigned-value basis and the applicable adjacent-value rationale below>`

For values 1..4, explain why the lower adjacent value would understate the evidence and the higher adjacent value would overstate it. For 0, explain why 1 would overstate the evidence and what would raise the value or reopen it. For 5, explain why 4 would understate the evidence and what would lower the value or reopen it.

A two-column coordinate-and-value table, a narrative paragraph, a table whose comment lacks adjacent-value comparison, or a result whose value depends on unchecked external loci is not an E.21 result. It is only draft evaluation material until every coordinate has a ShortRationale row and the result names the EvaluationEvidenceBasis used for values that depend on source, comparator, corpus, projection, or worked-case evidence.

A ShortRationale is allowed to be compact, but it is not allowed to be evidenceless. When the value depends on a source-currentness row, mature comparator, README scenario, ToC row, E.11 entry-distribution locus, I.2 expanded entry-disambiguation case, card, retrieval cue, monolith section, worked slice, near-miss, or anti-case, the rationale names that locus by value or says that the locus was missing or unchecked. "By value" means a recoverable section, row, case, checklist item, relation, source row, projection row, comparator id plus selected ingredient, or specific absent locus; a category list such as "entry, first move, boundaries, SoTA, checklist, relations" is not by-value discharge. Missing or unchecked evidence lowers the value for the coordinate that needs it; it does not create a separate "not evaluated" result. For SoTABindingAndCurrentness, source identity and currentness support traceability only. One completed canonical E.8:11 comparison supplies the required comparison basis; the evaluator assigns the value from that substantive comparison and its binding into the checked pattern.

A 5 is not a reward for clear early wording, named neighbour relations, or a well-formed field set alone. It needs exceptional expression for the declared use: reinforcing loci, a worked or otherwise replayable slice where the coordinate demands one, and no hidden cost or neighbour loss. When the evaluator cannot say why 4 would understate the evidence, assign 4 or lower.

When a coordinate's 5 meaning names a filled case, replayable slice, near-miss, anti-case, worked comparison, projection evidence, currentness basis, or selected-neighbour replay, absence of that evidence caps that coordinate at 4 even if the prose is otherwise strong. Do not hide the same absence only in CaseCountercaseAndTransferCoverage; lower every coordinate whose own 5 meaning needs that missing evidence. A 5 rationale names the reinforcing evidence loci that make 4 too weak.

For MaturePatternParityAndSelectedContentSufficiency, the rationale names a mature-pattern comparison set and the selected mature ingredients being claimed. For non-epistemic patterns, include at least one mature non-epistemic comparator when one exists—for example, a mature pattern about Work, Method, a system-role kind, a system-role assignment, direct-relation participation, a System, control, architecture, selection, engineering action, or another primary EntityOfConcern that is neither an episteme nor a publication. Route an unresolved source role through E.10.ROLE rather than treating the word as one pattern family. Value 4 requires by-value discharge of selected ingredients in the body or neighboring pattern that defines or constrains the claims; comparator IDs plus a generic "main ingredients are present" sentence are only value 3. The comparison is not a length target and not permission to copy semio apparatus.

For a 4 or 5 on MaturePatternParityAndSelectedContentSufficiency, include a compact maturity-discharge payload in the rationale or CoordinateEvidenceRefs: comparator=<pattern id>; selectedIngredient=<ingredient name>; currentLocus=<section, row, case, checklist item, relation, or neighboring pattern governing the claim>; missingOrLowering=<absent or weak ingredient, if any>. A category list such as "frame, first move, neighbour relations, CC, SoTA, relations" without current loci is still value 3, even when the listed categories are plausible mature ingredients.

Use the question-to-ground and result-acceptance operation in E.22:4.3 within this evaluation.

Precision-restoration profile

Before assigning the coordinate table, apply the whole-span precise-language reading in F.19 and record one PrecisionRestorationProfile summarizing its quality effect. F.19 governs the reading, repair, and local revalidation; E.21 consumes their result for its existing coordinates. The reading asks which governed object, claim, relation, and reader use the sentence, table, section, or repeated content family serves in the pattern of concern.

Use F.19's evidence-selection and coverage conditions for recoverability. Name the kind of basis and its material reading conditions in EvaluationEvidenceBasis; use checkedLoci for the text and relations it actually covers. A clean profile retains those qualifications. If F.19 requires an actual reading that is missing, the dependent recovery claim lacks that basis. Apply E.21:4.3's missing-evidence rule to the affected coordinates and identify the missing judgement. Distinguish this evidence gap from a wording defect established by reading the text.

Use this compact shape:

PrecisionRestorationProfile:
  overallEffect: <clean | boundedLocal | lowersCoordinates | repairBeforeUse>
  checkedLoci: <sections, rows, cases, and relations checked>
  affectedCoordinates: <coordinates lowered or protected>
  repairProposal?: <actual repair or blocker and its locus>
  kindRestorationCheck?: <when a changed FPF-governed expression can alter meaning: pre-repair and proposed post-repair object, kind, relation, current ontic slot, relation position, use relation, claim kind, admissible use, and scope; preserved | split | intentionally changed by accepted decision | blocker>

The diagnostic fields below are optional. Retain a field when its finding, restoration choice, or bounded evidence changes the quality result; a clean result needs no separate clean entry for each field. Fuller profiles use the same field meanings. When a receiving form needs an explicit untriggered kindRestorationCheck disposition, it may use not triggered, ordinary prose, or no FPF-governed phrase changed with the checked locus; this is optional detail in E.21.

Field	Diagnostic value
`wordHeadUsePrecision`	`clean`; `[E.10](/generated/patterns/E.10)`, `[E.10.ARCH](/generated/patterns/E.10.ARCH)`, `[F.18](/generated/patterns/F.18)`, or a concrete pattern contribution needed; or lowers coordinates.
`mgdaColdReaderRecoverability`	`clean`; broad replacement; hidden specialization; defining, constraining, or checking pattern content missing; or lowers coordinates.
`phraseApparatus`	`clean`; bounded local apparatus repair; or lowers coordinates.
`repetitionAndNegativeDistribution`	`clean`; bounded-local; or lowers coordinates.
`onticAndSlotRelationClarity`	`clean`; hidden candidate ontic or slot-relation drift; or lowers coordinates.
`descriptionPublicationSourceBoundary`	`clean`; description-publication-source boundary leakage; or lowers coordinates.
`patternApplicationOntology`	`clean`; application relation unclear; or lowers coordinates.

The scalar is the strongest quality effect that any layer requires: clean, bounded local repair, coordinate lowering, or repair-before-use. Classify a new symptom under the relevant diagnostic layer or restoration locus and apply its effect to existing E.21 coordinates. [F.19](/generated/patterns/F.19) settles ordinary whole-span language questions. Open [E.10](/generated/patterns/E.10), [E.10.ARCH](/generated/patterns/E.10.ARCH), or [F.18](/generated/patterns/F.18) for an unresolved word, head, or name problem; for hidden candidate ontics and ontic-vs-description-vs-publication boundaries, use [E.24.CD](/generated/patterns/E.24.CD), [E.24.PUB](/generated/patterns/E.24.PUB), or the concrete pattern content that defines or constrains the disputed object; claim, relation, evidence, Work, decision, assurance, publication, or pattern-application problems return to the pattern content that defines, constrains, or tests the disputed item. A pattern reference locates the content whose concrete contribution the evaluation uses. Exact predicates and ClaimGraph identity are required only when the evaluated claim or named reliance needs them. [E.21](/generated/patterns/E.21) consumes only the result: which coordinates fall, which stay protected, and what repair would make the quality claim true. The mgdaColdReaderRecoverability layer asks whether a reader without the DRR, campaign notes, or evaluator memory can recover the object, kind or ordinary status, relation or claim position, admissible use, next exact assertion when one is needed, and next concrete defining, constraining, or checking contribution. If a repair replaces a specific phrase with object, item, value, relation, record, condition, basis, material, or unqualified specialization and the reader cannot recover what specializes what, which relation is live, or which assertion or concrete pattern contribution is required, this layer is not clean.

When this layer finds a hidden candidate ontic or publication-form confusion, the E.21 result records only the quality effect and affected coordinates. Candidate detection, ontic placement, slot-relation design, and publication-boundary repair remain with [E.24.CD](/generated/patterns/E.24.CD), [E.24.PUB](/generated/patterns/E.24.PUB), or the concrete pattern whose content defines or constrains the affected object. The kindRestorationCheck is required when a changed FPF-governed expression can alter the meaning-bearing object, kind, relation, current ontic slot, relation position, use relation, claim kind, admissible use, or scope. It records those live values before and after the proposed repair, then names the concrete contribution when another pattern defines, constrains, or tests the affected kind, relation, claim, or position ([A.6.0](/generated/patterns/A.6.0), [A.6.5](/generated/patterns/A.6.5), [A.6.P](/generated/patterns/A.6.P), [C.29](/generated/patterns/C.29), [A.15](/generated/patterns/A.15), [E.24.CD](/generated/patterns/E.24.CD), [E.24.PUB](/generated/patterns/E.24.PUB), [E.10.ARCH](/generated/patterns/E.10.ARCH), or another relevant pattern). Every value that can drift receives an explicit preserved, split, intentionally changed by accepted decision, or blocker disposition. When no such risk is present, F.19's ordinary local revalidation is sufficient and the profile omits this field. The underlying slot, ontic, publication-form, and mathematical-lens rules remain with their subject patterns. A lexical replacement is not a repair when it only removes a trigger word, substitutes one umbrella for another, narrows a graph or method into a work sequence, widens a work occurrence into a method, turns a publication form or evidence source into the object itself, or otherwise changes kind, current ontic slot, relation position, use relation, or claim kind without an accepted decision. If the kind, current ontic slot, relation position, use relation, or claim kind cannot be recovered, the profile is at least lowersCoordinates; if the proposed repair would change one of them and no accepted DRR or concrete defining, constraining, or checking pattern content justifies that change, the result is repairBeforeUse or holdForArchitectureDecision.

When the profile is not clean, lower every affected coordinate named by the profile. Do not hide a present precision-restoration issue only in EntityOfConcernPrimacyAndSemioBiasResistance, and do not raise the result through related-pattern-boundary praise, projection evidence, or "correct but true" guards when those materials compete with the pattern's own EntityOfConcern, first useful move, practitioner action, practical delta, or next useful action.

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, `I.2` expanded entry-disambiguation cases, 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`, `I.2`, 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, I.2, 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.

Frequent value-3, value-4, and value-5 calibration points

These rows calibrate common disagreements. They do not replace the coordinate definitions above.

Coordinate family	3 is typical when	4 is typical when	5 is typical when
`WorkingSituationAndUseBoundaryRecognizability`	The situation is recoverable but late, abstract, or missing its practical gain, harm, first move, or action boundary.	The situation, intended use, first move, practical consequence, and stop or return are early and clear; any non-use distinction has a locally grounded plausible reading.	Early recognition is reinforced by a filled or replayable first-use slice showing that a cold practitioner can enter correctly.
`EntityOfConcernAndClaimScopeStability`	The primary object is named but related record, evidence, lens, or project claims keep pulling the scope.	The primary `EntityOfConcern` and claim scope stay stable, with bounded related-pattern material.	Scope stability is reinforced across title, recognition text, Solution, worked or replayable case material, checklist, relations, and any independently grounded non-use boundary without any local apparatus stealing attention.
`PatternApplicationGuidance`	The first action is named but only partly executable, or the Solution mostly assigns governing loci instead of giving this pattern's own action.	The first action and continuation are executable in this pattern's own subject terms; related-pattern statements are declarative, compact, and late.	The application guidance is demonstrated by a filled worked slice or equivalent replayable evidence.
`ClosureAndBoundedNonUseRecoverability`	Stop, repair, return, or related-pattern contribution is present but does not yet select the next action.	Stop, repair, return, reopen, and concrete defining, constraining, testing, or restoration contributions are recoverable for the declared use; any non-use boundary has an independent local ground.	A worked stop, overturn, return, or grounded non-use case shows how closure changes status or the next applicable pattern relation.
`NeighborAuthorityAndBoundedUseFit`	Related patterns are named but their contribution remains generic, future-pattern-like, ambiguous, hidden behind an unresolved role nickname, or too early in the Solution; or a separately asserted authority relation lacks its own basis.	Related patterns are named by value with limited declarative relations and the concrete definition, constraint, test, or repair contribution used here; use of each contribution stays within its stated scope, and related-pattern content does not replace the pattern's own content.	Those contributions and their limits remain replayable across cases, relations, and grounded boundary cases, with pattern application and any independently asserted authority relation explicit.
`EntityOfConcernPrimacyAndSemioBiasResistance`	The pattern is about its object but one or more precision-restoration layers lead or leak into it as development, review, or evaluation apparatus.	The pattern leads with its own object and application guidance; auxiliary material is compact, declarative, and late; role-word, slot, publication-form, source, locus, flow, and status expressions are used only when they add a real kind, relation, evidence value, or user-facing action; quality or projection evidence about the pattern stays outside the pattern.	The primary object and application guidance are first recoverable across recognition text, Solution, cases, and checks even when auxiliary material is present, and any precision-restoration, quality, or projection material is in its proper evaluation, projection, or publication locus rather than in the pattern.
`PracticalUseDeltaAndHarmPrevention`	The practical gain or prevented harm is named but not demonstrated.	The pattern changes a recoverable use through a named practical gain or prevention of plausible harm or misuse for the declared use.	A worked or near-miss case shows the practical delta and cost of missing the pattern; when harm prevention is claimed, the case demonstrates it.
`UseAffordabilityAndApparatusProportionality`	The first move exists but apparatus is heavy for ordinary readers.	Ordinary first use is affordable and heavier apparatus opens only when useful.	A minimal first-use example shows the thin ordinary use works before heavy apparatus.
`RepairLocalityAndChangeImpactPredictability`	Repair conditions or related-pattern relations are named but downstream impact is not shown.	Repairs have local loci and predictable impact for declared use.	A worked repair or downstream-impact slice shows the smallest locus and changed related-pattern relation.
`ProxyForValueSubstitutionResistance`	Proxy risks are named but "what got worse" is not applied.	The pattern blocks visible proxy substitutions and asks what worsened.	A proxy-failure case shows a visible improvement damaging intended value, and the pattern prevents that proxy substitution.
`ClaimJustificationTraceabilityCurrentnessAndReplayability`	Fields or sources exist but replayability and currentness basis are incomplete.	The claim can be replayed from pinned text, evidence, currentness basis, status, and stop reason.	A filled evidence and currentness slice shows how the claim is replayed and when it reopens.
`CaseCountercaseAndTransferCoverage`	Archetypes are listed, but no filled worked case or near-miss exercises the claim.	At least one filled worked case plus a near-miss or anti-case covers the declared use.	Heterogeneous cases, countercases, and transfer slices cover the breadth claimed.
`MaturePatternParityAndSelectedContentSufficiency`	Mature comparators are named or implied, but selected mature ingredients are not discharged by value.	Mature comparators are named and selected ingredients are discharged by value in the body or related patterns named by value.	Mature parity is shown across reinforcing body sections, related patterns, omissions, cases, and lowering conditions without copying irrelevant apparatus.
`SoTABindingAndCurrentness`	A source set or currentness account is relevant, but the positive claim does not yet satisfy the `E.8:11` comparison; identity/currentness alone remains below the ordinary floor.	One complete `E.8:11` comparison is present by value, its selected line defeats or bounds a serious alternative at comparable effort, and the decision changes exact governed pattern loci.	A replayable comparison across reinforcing loci shows why `4` understates the binding; a longer, newer, more official, or more popular bibliography supplies no increase.
`FormalClaimAdmissibilityAndLensFit`	Formal, scale, lens, or measurement terms are bounded but not exercised.	Formal, lens, and measurement claims are admissible for their stated use, bounded, and connected to the concrete pattern content that defines, constrains, or tests their admissibility when the evaluated pattern makes such claims; exact predicates are required only when the claim or named reliance needs them.	A worked formal, lens, or scale comparison shows what is preserved, lost, admissible, and not proved.
`FalsifiabilityAndLoweringCondition`	A closure or limitation is stated, but lowering and reopen triggers for the main claims are mostly implicit.	The pattern states explicit lowering and reopen triggers for its main claims; named fields alone do not reach `4` unless they say what evidence change lowers, overturns, rejects, or reopens the claim.	Worked lowering or overturn cases show how values, status, or use change.
`CorpusEntryProjectionAndEcologyFit`	Host text is coherent, but README, ToC, `E.11`, `I.2`, card, retrieval, monolith, or projection evidence is absent for a corpus-facing claim, or that evidence is placed anywhere in the pattern as method, note, appendix, relation, rationale, or quality-status content about the pattern.	Corpus-facing entry or projection loci are named and aligned enough for the declared use, and their evidence stays in the evaluation, result, or projection locus rather than entering the pattern.	Retrieval, stale-projection, cold-reader, or projection-update evidence shows corpus ecology stays aligned after change without leaking into the pattern.
`EvolutionFrontAndRefreshDiscipline`	Reopen is delegated to related patterns or implied by source-return.	The smallest reopen locus, source or currentness trigger, or variant or front condition is explicit.	Variant, front, archive, or ongoing refresh discipline is replayable for the declared use.

For EntityOfConcernPrimacyAndSemioBiasResistance, do not compensate a bad PrecisionRestorationProfile with NeighborAuthorityAndBoundedUseFit or CorpusEntryProjectionAndEcologyFit. Ask which governed object, claim, relation, and reader use the sentence serves. Material about developing, reviewing, projecting, landing, evaluating, or proving this pattern's quality belongs in the evaluation, projection, release, or publication locus that carries that work. Related-pattern statements can be true and still damage the pattern when they precede its own EntityOfConcern and application guidance. If the opening Problem frame or Solution starts with precision-restoration material before the subject and move, this coordinate is at most 2; if the reader must traverse that material across sections to find the action, it is at most 3. Put compact concrete contributions in Relations or a late boundary row. Add local guard prose only when it passes F.19:4's full independent-ground, plausible-reader, contribution, and smallest-clear-correction test and the subject pattern does not already settle the needed distinction. Also lower PatternApplicationGuidance, WorkingSituationAndUseBoundaryRecognizability, PracticalUseDeltaAndHarmPrevention, and UseAffordabilityAndApparatusProportionality when the profile shows that auxiliary material displaces first use. If the declared use is Stable, landing-input, release-input, external-review-ready, or another corpus-facing use, assessment work must inspect the applicable corpus-entry and projection evidence and the result's EvaluationEvidenceBasis must name it. A host-only body assessment can still produce values about the pattern body, but it cannot silently turn missing README, ToC, E.11, I.2, card, retrieval, monolith, or projection evidence into a high CorpusEntryProjectionAndEcologyFit value.

Status and stop condition

Status	Meaning
`admissibleForDeclaredUse`	Every coordinate meets the declared floor for the scoped use, and the result states the usable next action, stop or repair, and reopen condition.
`repairBeforeUse`	One or more coordinate floors fail for the declared use.
`holdForArchitectureDecision`	Repair requires a decision about `EntityOfConcern`, the scope of contributing pattern content, split, merge, or placement.
`refreshNeeded`	A SoTA, neighbour, terminology, retrieval, telemetry, use-scope, or corpus change invalidates a previous evaluation.

Default floor is 4 wellExpressedForDeclaredUse on every coordinate for ordinary practitioner use, authoring-input use, landing-input use, Stable, external-review-ready, release-input, canonization-input, stop-improving claims, and ordinary improvement-loop use. Every result presented as an E.21 result contains every coordinate and its rationale, including a diagnostic or exploratory E.21 result. A bounded diagnostic may borrow selected E.21 questions; it reports only their findings and makes neither an E.21-result nor an admissible-use claim. If the current request asks for corpus-facing, landing-input, Stable, release, or external-review use, the evaluator measures that required use and returns repairBeforeUse, holdForArchitectureDecision, or refreshNeeded when the floor is missed.

An all-5 result is a local exceptional result under the declared scope and qualification window. It is not a permanent end of development. E.23 can reopen improvement when use, source, comparison set, front, affordability, or payoff changes.

Consume Pattern-Edition Use-Value Evidence Noncompensatorily

When an E.19:4.3.3 replay is current, use that one stable-candidate replay as evidence for the E.21 assessment. During assessment, keep materially affected predecessor and candidate-only uses distinguishable whenever their action, result, boundary, necessity, or consequence can differ; do not copy clean per-use dispositions into the E.21 result. The evaluator still applies every existing coordinate required by the declared scope once. The result names the replay loci in EvaluationEvidenceBasis and carries only distinctions, failures, or improvements that actually change a coordinate rationale or PatternQualityStatus; it does not replace the coordinate set with one use-value score, average replay results, or infer a coordinate value from an E.19 outcome.

Apply these consequences:

Use-review condition	Mandatory E.21 consequence
A required prior-edition use probe is `regressed`	Set status to `repairBeforeUse`. Every affected coordinate is at most `2 partiallyExpressedForDeclaredUse`. Include at least `PatternApplicationGuidance` and `PracticalUseDeltaAndHarmPrevention` when action or result was lost; also include each of `ClosureAndBoundedNonUseRecoverability`, `NeighborAuthorityAndBoundedUseFit`, `UseAffordabilityAndApparatusProportionality`, and `ClaimJustificationTraceabilityCurrentnessAndReplayability` when that coordinate's claim depended on the use.
A required new intended-use check is absent or insufficient for the candidate-only use	Set status to `repairBeforeUse`. Every affected coordinate is at most `2`. Include at least `PatternApplicationGuidance` and `PracticalUseDeltaAndHarmPrevention`. Additionally cap each of `EntityOfConcernPrimacyAndSemioBiasResistance`, `ClosureAndBoundedNonUseRecoverability`, `NeighborAuthorityAndBoundedUseFit`, `UseAffordabilityAndApparatusProportionality`, `CaseCountercaseAndTransferCoverage`, and `ClaimJustificationTraceabilityCurrentnessAndReplayability` only when the missing evidence affects that coordinate's claim.
An optional new intended-use check is absent or insufficient for the candidate-only use	Do not create a status blocker merely from absent optional breadth. The missing case cannot support a breadth, transfer, or value-`5` claim. Reflect the absence in `CaseCountercaseAndTransferCoverage` and every coordinate whose declared scope actually includes that use.
A new intended-use check is adequate for the candidate-only use	No blocker follows from that check. Its evidence may support affected existing coordinates but establishes neither their values nor status by itself.
The pattern's subject, problem, action, and result are not stated in usable positive terms: its own `EntityOfConcern`, first useful move, practitioner action, practical delta, or next useful action cannot be recovered	Set status to `repairBeforeUse`. `PatternApplicationGuidance`, `EntityOfConcernPrimacyAndSemioBiasResistance`, `PracticalUseDeltaAndHarmPrevention`, and `UseAffordabilityAndApparatusProportionality` are each at most `2`.
A required enumeration has an unresolved hidden kind, alien member, hidden proposition, false closure claim, or series whose form contributes nothing to the receiving use	Set status to `repairBeforeUse`. `SemanticKindAndNameRecoverability` is at most `2`; each of `EntityOfConcernAndClaimScopeStability`, `NeighborAuthorityAndBoundedUseFit`, `FormalClaimAdmissibilityAndLensFit`, and `PatternApplicationGuidance` is also at most `2` when the unresolved or needless series affects that coordinate's claim.
A required prior-edition use is discoverably `transferred`	No regression blocker follows. The handoff evidence may support `NeighborAuthorityAndBoundedUseFit`, `PatternApplicationGuidance`, and `ClosureAndBoundedNonUseRecoverability` but establishes none of their values by itself.
A harmful or false prior-edition use is `intentionally retired` with a positive corrected action or boundary	No regression blocker follows. Evaluate the corrected use and harm prevention on their own evidence.
The material-change trigger is false	Apply no new use-review cap. The ordinary complete coordinate, rationale, and result requirements still apply whenever an E.21 result claim is requested.

The cap is 2, not 3, because 3 sufficientlyExpressedForDeclaredUse already means usable for the declared scope while the required action or semantic member here is unusable. Unrelated strengths, source count, formal cleanliness, or corpus projection cannot compensate for the failed required use. Conversely, preserved, improved, transferred, intentionally retired, or adequate candidate-only evidence can support only the existing coordinates whose claims it actually tests; it cannot raise unrelated coordinates or determine status by label.

Compact result form

An E.21 result uses this result-bearing form:

E.21 result:
  Pattern of concern: <PatternOfConcernRef>
  Declared scope, use, reader, and window: <ClaimScope, IntendedUse, WorkingReaderScope, QualificationWindow>
  Evidence basis checked: <EvaluationEvidenceBasis>
  Status: <PatternQualityStatus>

Include one PrecisionRestorationProfile under E.21:4.3a: overallEffect, checkedLoci, and affectedCoordinates, plus issue-bearing detail only when it changes the quality result.

Coordinate values.

Coordinate	Value	ShortRationale
`<all RequiredPatternQualityCoordinates rows>`	`<0..5>`	`<assigned-value basis and the value-appropriate adjacent comparison in E.21:4.3>`

When SoTABindingAndCurrentness is 4 or 5, the result also includes one completed instance of the canonical [E.8:11](/generated/patterns/E.8#sota-echoing-normative-typed-comparison-to-contemporary-best-known-practice) comparison contract in the rationale or immediately after the coordinate table. The form below records that result; it does not redefine its fields:

E.8:11 SoTA comparison:
  practiceQuestion: <exact practice question>
  bestKnownLine: <selected best-known current answer>
  seriousAlternativeOrDefault: <rival or default compared>
  defectOvercome: <action-changing defect or trade-off>
  patternMutation: <exact Solution, boundary, case, check, relation, evidence, stop, or reopen locus>
  sourceRolesAndLimits: <best-known candidate, rival, failure evidence, explicit comparator, and what each does not establish>
  reopenCondition: <smallest evidence, rival, failure, or use change that reopens the judgement>

Source identity, publication status, currentness, and maintenance evidence may support ClaimJustificationTraceabilityCurrentnessAndReplayability and the qualification window. They cannot fill bestKnownLine, raise this coordinate, or replace the comparison payload.

First repair or stop: <repair | hold | local stop>
Reopen if: <ReopenCondition: smallest changed locus or condition>
BoundedNonUse?: <only an independently grounded boundary that changes the result's use>

The header, compact PrecisionRestorationProfile, complete coordinate table with ShortRationale, required evidence basis, and stop and reopen conditions constitute the E.21 result; incomplete material supports further assessment. The result asserts local PatternQualityStatus. Separate E.19 review work and result, plus the authority-bearing release or admission work or decision named by value, govern gate-specific carry-through, projection, monolith, packaging, authority, and receiving-use boundaries.

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](/generated/patterns/E.22), [E.23](/generated/patterns/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.

Archetypal Grounding - worked slices

Complete compact evaluation

Exact example edition EX.1@source-pin-1. The quoted text below is the whole pattern edition being evaluated; no campaign note or unstated appendix is part of it.

EX.1 - Pin a reused rule to its source edition.

Use this when a team relies on a rule from a source that can change.

First move: beside the decision, record the source title, exact edition or date, the exact rule used, and what that rule changes in the decision.

If the edition or rule cannot be recovered, stop that reuse and retrieve it.

Not this pattern when the source is background reading and no claim or decision relies on it.

The pin lets a reader recover which source rule changed the decision.

Example: a team records Cooling Guide, edition 3, rule 7 beside the chosen inspection interval and notes that rule 7 sets the maximum interval; a mention of the guide in a reading list is outside this use.

Reopen the decision whenever the source publishes any new edition.

The final sentence is deliberately defective: an unrelated editorial revision would trigger the same reopen as a change to rule 7. Everything below evaluates that exact text, including the defect.

Configuration and evidence basis.

PatternOfConcernRef: the complete quoted EX.1@source-pin-1 edition.
ClaimScope: diagnostic rehearsal of E.21 on one small pattern; declared floor 3 sufficientlyExpressedForDeclaredUse for this rehearsal only.
WorkingReaderScope: a new evaluator who has E.21 and the quoted text but no campaign history.
IntendedUse: learn whether this edition is coherent enough for the diagnostic rehearsal and identify the first repair; if EX.1 is later proposed for publication or ordinary authoring use, that receiving use requires its own admission decision.
QualificationWindow: until the quoted edition, E.21 scale, or named comparison evidence changes.
EvaluationEvidenceBasis: all seven sentences of the quoted edition; its filled Cooling Guide case; its background-reading non-use boundary; the absent material-change test in the last sentence; E.2.DA's pinned source-use discipline and G.11's bounded currentness contribution as mature comparators; no README, ToC, retrieval, external SoTA, observed-use, or corpus-projection evidence.
Ordinary path only: the evaluator reads and judges the text; this diagnostic use needs no additional reliance-bearing identity or receiving decision.

PrecisionRestorationProfile:
  overallEffect: clean
  checkedLoci: all seven quoted sentences, the filled case, the grounded background-reading boundary, the pin's traceability use, and the last-sentence reopen rule
  affectedCoordinates: none — the overbroad refresh rule is evaluated in the coordinate table and finding, not through a precision-restoration layer

Coordinate	Value	ShortRationale
`WorkingSituationAndUseBoundaryRecognizability`	`3`	The edition states the rule-reuse situation, first move, stop, and grounded background-reading boundary, so `2` understates recognition; `4` would require the missed harm and practical payoff to be early and explicit rather than inferred from the later case.
`EntityOfConcernAndClaimScopeStability`	`4`	Every sentence stays on a source rule reused by one decision, so `3` understates stability; `5` would overstate one small case with no second receiving use.
`PatternApplicationGuidance`	`4`	The reader can record four exact items and knows when to stop, so `3` understates executability; `5` would require observed first use or a second case.
`ClosureAndBoundedNonUseRecoverability`	`3`	Stop, return, the grounded background-reading boundary, and reopen are explicit, so `2` is too low; `4` would hide that the reopen condition is materially overbroad.
`SemanticKindAndNameRecoverability`	`4`	Source, edition, rule, decision, and pin remain distinct, so `3` understates the text; `5` lacks a hard ambiguity countercase.
`NeighborAuthorityAndBoundedUseFit`	`4`	The pin supplies a recoverable source return for the relying decision; the text asks the reader to record reliance and keeps the decision itself separate, so `3` understates the boundary; `5` would require replay across evidence, assurance, and publication uses.
`EntityOfConcernPrimacyAndSemioBiasResistance`	`4`	The pattern opens with the working rule-reuse problem and action, not source apparatus, so `3` is too low; `5` lacks observed cold-reader evidence.
`PracticalUseDeltaAndHarmPrevention`	`4`	The case shows how a decision stays traceable to rule 7 and the stop prevents unsupported reuse, so `3` understates the gain; `5` lacks an observed before-and-after project case.
`UseAffordabilityAndApparatusProportionality`	`4`	First use asks for four nearby facts and opens no optional apparatus, so `3` understates affordability; `5` would require observed first-use effort or repeated project use rather than this text-only rehearsal.
`RepairLocalityAndChangeImpactPredictability`	`4`	One last-sentence condition is the exact repair locus and its effect is predictable, so `3` understates locality; `5` lacks a replay through several dependent decisions.
`ProxyForValueSubstitutionResistance`	`3`	The source pin has a stated traceability use, so `2` understates proxy resistance; `4` would require a near-miss where a visible pin is wrongly treated as approval.
`ClaimJustificationTraceabilityCurrentnessAndReplayability`	`4`	Title, edition, rule, effect, decision, and stop are recoverable, so `3` understates replayability; `5` lacks an actual replay across two source editions.
`CaseCountercaseAndTransferCoverage`	`4`	The filled inspection-interval case and background-reading near-miss meet the declared small use, so `3` understates coverage; `5` would require heterogeneous transfer cases.
`MaturePatternParityAndSelectedContentSufficiency`	`3`	`comparator=[E.2.DA](/generated/patterns/E.2.DA) and [G.11](/generated/patterns/G.11); selectedIngredient=pinned source use plus bounded currentness; currentLocus=sentences 2-3 and 7; missingOrLowering=sentence 7 lacks a material-change test`; this makes `2` too low, while the missing selected ingredient prevents `4`.
`SoTABindingAndCurrentness`	`3`	The edition makes no positive SoTA claim and supplies no `[E.8:11](/generated/patterns/E.8#sota-echoing-normative-typed-comparison-to-contemporary-best-known-practice)` comparison, so its source pin and currentness rule cannot raise this coordinate; `2` would understate the explicit source-use scope, while `4` requires one complete comparison result that this diagnostic example expressly lacks.
`FormalClaimAdmissibilityAndLensFit`	`4`	The edition makes no measurement, scalar, causal, or formal-model claim and assigns the pin only its traceability use, so `3` understates the fit; `5` lacks a formal near-miss.
`FalsifiabilityAndLoweringCondition`	`3`	Edition publication is an observable reopen trigger, so `2` is too low; `4` would overstate a trigger that does not distinguish material from irrelevant change.
`CorpusEntryProjectionAndEcologyFit`	`3`	The declared diagnostic use is explicitly non-corpus-facing and the whole checked text is present, so `2` is too low; `4` would require the absent entry or projection evidence for a corpus-facing claim.
`EvolutionFrontAndRefreshDiscipline`	`2`	The edition states a refresh trigger, so `1` understates it; any new edition triggers refresh without testing whether the used rule changed, so `3` would overstate usable evolution discipline.

The profile, complete table, status, stop and reopen, plus the quoted pattern's grounded background-reading boundary, constitute this example's non-arithmetic PatternQualityQBundle; the single value of 2 is the one below-floor defect, not an arithmetic penalty or a reason to lower unrelated qualities.

E.21 result:
  Pattern of concern: EX.1@source-pin-1, exactly as quoted
  Declared scope, use, reader, and window: diagnostic rehearsal; teach one new evaluator; floor 3; current until the quoted edition, E.21 scale, or evidence basis changes
  Evidence basis checked: seven quoted sentences, filled case, background-reading near-miss, absent material-change test, E.2.DA and G.11 comparators, and the explicitly absent corpus, observed-use, and external-source evidence
  Status: repairBeforeUse

First repair: narrow the final sentence to a change in the used rule, its applicability, or a stated limitation.
Receiving use: if EX.1 is proposed for admission or publication, use a separate receiving decision; this diagnostic result supplies its quality finding and repair.
Reopen if: EX.1's exact text, E.21's scale, the stated floor, or any named evidence locus changes.
BoundedNonUse: EX.1's evaluated use excludes background reading on which no claim or decision relies.

E.21 finding:
  Pattern of concern: EX.1@source-pin-1
  Coordinate or status affected: EvolutionFrontAndRefreshDiscipline; repairBeforeUse
  Pattern locus: final sentence
  Value or status effect: EvolutionFrontAndRefreshDiscipline = 2 below the declared floor 3
  Correction direction: reopen only for a material change to the used rule, its applicability, or a stated limitation
  Closure test: an unrelated new-edition change no longer triggers work, while a changed rule 7 still reopens the relying decision

This is the ordinary path. The evaluator needed no dated-Work account or operation-application record to produce a complete result.

Names named by value, no first move. A pattern has precise Tech names and current source rows but no first user-facing action. WorkingSituation..., PatternApplicationGuidance, and PracticalUseDelta... fall; source currentness does not rescue ordinary use.

Short architecture pattern. A compact pattern has a triage form but no worked slice and no mature-pattern comparison. It can be useful as local expert reference material, but MaturePatternParity... and CaseCountercase... stay below exceptional until selected mature content is present.

Precision-restoration profile in a non-semio pattern. A pattern tries to introduce a non-semio EntityOfConcern through a catalog of other claim kinds or objects outside its own subject. Its membership rule—outside this pattern's subject—does not explain which distinctions the reader needs. If copied boundary doctrine leads the Problem frame or Solution, EntityOfConcernPrimacyAndSemioBiasResistance falls to 2 or 3 even when every individual boundary is true. Lead with this pattern's own subject, first useful move, practitioner action, practical delta, and positive guidance. Add one local explanation, stop, or non-use boundary only when it passes F.19:4's full independent-ground, plausible-reader, contribution, and smallest-clear-correction test. Replace other copied doctrine with the relevant pattern ID and its concrete contribution. If the doctrine is distributed across sections, repair that distribution rather than only its sentences.

Reference apparatus before Solution content. A pattern's first Solution paragraph assigns other patterns or related-pattern mappings before it unfolds the ontology, method, norm, worked action, or other positive solution for the pattern of concern's own EntityOfConcern. Even if the related pattern id is correct, PatternApplicationGuidance, EntityOfConcernPrimacyAndSemioBiasResistance, PracticalUseDeltaAndHarmPrevention, and sometimes NeighborAuthorityAndBoundedUseFit fall. Move discoverability to README, ToC, [E.11](/generated/patterns/E.11), [I.2](/generated/patterns/I.2), or retrieval loci; put compact pattern references and their concrete contributions in Relations or a late boundary row; put architecture-placement rationale in a DRR or architecture document; and make the Solution answer “what do I do with this pattern's EoC?” first.

Overformalized precision. A pattern uses correct FPF kinds, slots, references, and cross-pattern pointers so densely that the working reader cannot recover the first useful move, practical delta, or generalizing insight without doing an internal audit. Precision is then present but not usable. Lower UseAffordabilityAndApparatusProportionality, WorkingSituationAndUseBoundaryRecognizability, and sometimes PatternApplicationGuidance. Repair by keeping the ontology named by value only where it carries a current FPF-governed claim, moving restoration evidence to the evaluation result or DRR, and adding a short worked slice or plain recognition sentence that preserves the same kind without extra apparatus.

QualityEvidenceLeakage in the pattern. The pattern says that corpus projection, README, ToC, [E.11](/generated/patterns/E.11), or [I.2](/generated/patterns/I.2) alignment, retrieval or cold-reader evidence, monolith parity, external-review readiness, landing evidence, PatternQualityStatus, all-4 or all-5 result framing, or another quality-result locus is what the user should do with the pattern's EntityOfConcern, or records developer, reviewer, or executor correspondence as if it were pattern content. The defect is not limited to Problem frame, Solution, examples, or checklist; notes, appendices, Relations, Rationale, SoTA-Echoing, tables, and conformance rows are also parts of the pattern in hosts and the monolith. That evidence may be required for [E.21](/generated/patterns/E.21), [E.19](/generated/patterns/E.19), landing, or retrieval loci, but it is not automatically a user action in the pattern of concern. Lower EntityOfConcernPrimacyAndSemioBiasResistance, PatternApplicationGuidance, UseAffordabilityAndApparatusProportionality, and CorpusEntryProjectionAndEcologyFit when this evidence enters the pattern. Repair by moving the evidence to the [E.21](/generated/patterns/E.21) result, [E.19](/generated/patterns/E.19) run record, README, ToC, [E.11](/generated/patterns/E.11), [I.2](/generated/patterns/I.2), card, retrieval, projection, or release or landing evidence locus, and keeping in the pattern only the user-facing move or boundary that follows from that evidence.

Quality table without rationale. A result gives values but no adjacent-value rationale. Values are unsupported. Add ShortRationale or lower.

Goodharted improvement. A rewrite improves source refs and proof sketches but becomes hard to use, or treats every non-5 coordinate as a defect to be fixed with more apparatus. Re-evaluate affordability, repair locality, proxy-for-value, and corpus ecology before stopping. When exceptional improvement is requested, keep searching for content movement, not proof movement; the aggregate no-proposal disposition in E.21:4.7 needs loci showing that further content change is dominated, unavailable, or outside scope.

Bias-Annotation

E.21 resists Goodhart-style quality substitution: a high value is not produced by length, source count, approval state, checklist closure, or elegant phrasing when the required coordinate evidence is absent. It also blocks semio-bias by checking whether the evaluated pattern leads with its own EntityOfConcern and user-facing action rather than with description, publication, source, review, or repair apparatus.

Conformance checklist

Check	Requirement
`CC-E21-0`	Keep the exact checked pattern edition, characteristic space and specification, evaluation configuration, admitted evaluator `U.System` and ordinary assessing action, coordinate-result claims, aggregate result episteme, and any admission or refresh decision distinct. Do not invent a system-role kind, assignment, Method, Work, or A.6.1 application for the ordinary form. When actual assessment `U.Work` is asserted, item 5 MUST hold: every precise evaluator-performer has an A.13 core, and A.15.1 independently admits the Work from its performance history, enacted Method, extent, and containing-System relation under the exact boundary and qualification window. F.6 MUST be added only when the evaluation account also needs precise assignment-bound attribution. A compact account may omit an unused identifier only when every consumed relation remains recoverable. The Work assertion alone establishes neither an application nor a result. Keep the Work, any returned value or direct evaluation-result relation, and the C.2.1 result episteme separate; connect them only through an exact A.6.1 result binding or a separately declared direct evaluation-result relation that actually obtains. When an exact application is asserted, the compact A.6.1 rule in E.21:4 MUST hold and its required application-and-binding account MUST be recoverable. Keep witnesses or evidence use, optional record, status use, assurance, publication, currentness, and later repair separately recoverable when claimed.
`CC-E21-0a`	Constitute each coordinate value as a quality ascription about the same exact checked pattern edition with recoverable ReferenceScheme, characteristic, scale value, evaluation rule or probe, scope, use, and window, ordinary assessing action or exact assessment application when asserted, rationale, and evidence locus. Keep all required coordinate claims in one non-arithmetic `PatternQualityQBundle` payload carried by a separate C.2.1 aggregate result episteme; evaluator identity, viewpoint, witness presence, record placement, or bundle membership supplies neither value nor grounding by itself.
`CC-E21-1`	Recover `ClaimScope` from the governing evaluation question: the current request, an `E.22` frame, an accepted decision or content source named by value, a landing or release check, a review request, or another actual quality-use request. Then name `PatternOfConcernRef`, `ClaimScope`, `WorkingReaderScope`, `IntendedUse`, `QualificationWindow`, and `EvaluationEvidenceBasis`.
`CC-E21-2`	Evaluate the full `RequiredPatternQualityCoordinates` set.
`CC-E21-2a`	Before assigning coordinate values, apply `F.19` and record one `PrecisionRestorationProfile` under E.21:4.3a with `overallEffect`, `checkedLoci`, and `affectedCoordinates`. Add issue-bearing detail when it changes the result; ordinary repairs use F.19's local revalidation, and a risk of changed FPF-governed meaning opens `kindRestorationCheck`.
`CC-E21-3`	Use the result-bearing three-column table: coordinate, value, and `ShortRationale`; a two-column coordinate-and-value table is not an `E.21` result.
`CC-E21-4`	Let `floorEvaluation` change floor and evidence cost only, not the coordinate set.
`CC-E21-5`	Assign values from checked pattern content and named content evidence, not review, landing, popularity, praise, or absence of prior use.
`CC-E21-6`	For corpus-facing values, name the checked README, ToC, `E.11`, `I.2`, card, retrieval, monolith, or projection loci, or lower the affected coordinate when those loci are missing or unchecked.
`CC-E21-6a`	Keep corpus-projection; README, ToC, `E.11`, and `I.2` alignment; retrieval or cold-reader evidence; monolith-parity; `PatternQualityStatus`; developer, reviewer, and executor correspondence; and other quality evidence out of the pattern unless the pattern's own `EntityOfConcern` and user-facing action are that evaluation or projection work. Part E patterns may define or guide FPF-pattern authoring, review, evaluation, entry, or publication as their subject matter; that does not license rationale or instructions about developing the same pattern version. Test what the sentence is doing, not whether it contains a listed word. If such material appears anywhere in the pattern, including notes, appendices, `Relations`, `Rationale`, `SoTA-Echoing`, examples, tables, conformance rows, or any other host or monolith pattern section, as development, review, projection, or quality-status content about the pattern, lower `CorpusEntryProjectionAndEcologyFit`, `EntityOfConcernPrimacyAndSemioBiasResistance`, and the affected action or usability coordinates.
`CC-E21-7`	For any `5`, name the reinforcing evidence loci required by that coordinate's `5` meaning; otherwise lower the coordinate to `4` or below.
`CC-E21-8`	For `MaturePatternParityAndSelectedContentSufficiency = 4` or `5`, include a compact maturity-discharge payload: comparator id, selected ingredient, current locus, and missing or lowering item if any; category lists without loci cap the coordinate at `3`.
`CC-E21-9`	Invoke the canonical definition and positive comparison contract in `E.8:11` for every positive SoTA judgement; use `F.1` only to inspect whether its source cut can support that comparison. For `SoTABindingAndCurrentness = 4` or `5`, include one complete `E.8:11` comparison payload by value. A relevance/currentness table plus adopt/adapt/reject labels is below the ordinary floor when that comparison is absent.
`CC-E21-9a`	Treat source identity and currentness as supporting traceability only. Official, popular, maintained, canonical, highly cited, recent, or academically praised status supplies zero positive evidence for `bestKnownLine`; a registry or publisher check cannot raise `SoTABindingAndCurrentness`. An official or widespread source can still fill `bestKnownLine` when its substantive answer independently wins the required comparison. A value `5` additionally names the replayable comparison and reinforcing loci that make `4` too weak rather than adding bibliography, prevalence, or freshness.
`CC-E21-10`	Keep measurement, score, scale, formal, causal, mathematical, QL, simulation, representation, or learned-lens claims under `C.16`, `A.17`, `A.18`, `A.19`, or the pattern that defines, constrains, or tests the claim when the evaluated pattern makes those claims.
`CC-E21-11`	State floor satisfaction, next usable action, stop or repair, and lowering or reopen conditions. Add a non-use boundary only for an independently grounded reading that a plausible intended reader could make here.
`CC-E21-12`	Keep coordinate rationale separate from improvement proposal rows.
`CC-E21-13`	Keep quality results within their declared receiving use; any further evidence, assurance, gate, work, safety, compliance, release, or publication claim requires its direct relation.
`CC-E21-14`	Do not raise a pattern with a bad `PrecisionRestorationProfile` through related-pattern-boundary, projection, or quality-result praise. When the profile shows defects before the pattern of concern's primary subject action is recoverable, or enough volume to compete with the Solution, lower `EntityOfConcernPrimacyAndSemioBiasResistance` and the affected action and usability coordinates; do not offset that loss with generic related-pattern-boundary praise or correct corpus projection evidence.
`CC-E21-15`	Keep ordinal values as ordinal content-evaluation result claims, not repair targets. Below-floor values require findings or repair. Values at or above the floor receive proposal rows only for concrete non-dominated content opportunities when improvement is requested; a non-`5` value is not automatically a defect. No proposal may raise a value by adding quality proof, guards, relation catalogues, or process evidence that worsens use, affordability, locality, ecology, or the pattern's own subject kind and positive action guidance. The aggregate no-proposal or stop disposition in E.21:4.7 must name checked loci and why no substantive content improvement remains.
`CC-E21-16`	When `E.19:4.3.3` use-value replay evidence is current, evaluate the full existing coordinate set once and keep only materially affected uses whose outcomes can differ distinguishable during assessment. Carry into the durable result only replay distinctions that affect a coordinate rationale, cap, or status; do not create a second clean-use ledger. Apply the required-failure caps and `repairBeforeUse` effects in `E.21:4.5.1`; keep optional absence non-blocking by itself while denying unsupported breadth, transfer, or value-`5` claims. Do not average outcomes, substitute an E.19 label for an ordinal value or status, compensate a failed required use with unrelated strengths, or infer values from a successful label alone.

Common Anti-Patterns and How to Avoid Them

Anti-pattern	Repair
Subject/action guidance reified or operationalized. Plain first-use guidance is turned into a `SubjectActionSpine`, structural field, method, CGUS, or performed work; or `PrecisionRestorationProfile`, process proof, or guard catalogues substitute for judgment of the pattern's actual content.	Keep subject and action guidance Plain unless an exact admitted method or A.22.CGUS is genuinely current and cited by value; require dated `U.Work` independently when performance is claimed; judge the pattern's own `EntityOfConcern`, first useful move, practitioner action, practical delta, and next useful action, adding a guard only when a plausible intended reader has an independently grounded reason for that reading.
Score illusion. `Pattern quality = 87 out of 100`.	Use ordinal coordinate values; no arithmetic aggregation.
Two-column table. Coordinate-and-value table has no rationale.	Add `ShortRationale` for every coordinate.
Floor as omission. A floor evaluation omits maturity, SoTA, formal, corpus, or evolution coordinates.	Keep floor low if needed; evaluate all coordinates.
Scope laundering. A landing-input, corpus-facing, `Stable`, release, or external-review request is reported under an easier use, local-only use, diagnostic pass, or evaluator-selected use.	Re-evaluate under the governing scope; if it fails, return `repairBeforeUse`, `holdForArchitectureDecision`, or `refreshNeeded` with the missed coordinates and repairs.
Administrative proxy. "4 because landed" or "3 because not externally reviewed".	Evaluate pattern content.
Currentness laundering. A registry entry, official publication date, maintained status, latest release, citation count, or fresh preprint is verified and then used to raise `SoTABindingAndCurrentness`.	Keep that evidence under traceability and the qualification window. Require one completed `E.8:11` comparison and cap a currentness-only result below the ordinary floor.
Comparator-free or locus-free maturity. `MaturePatternParity... = 4` by impression, comparator IDs only, or category list such as "frame, first move, checklist, SoTA, relations".	Name mature comparison patterns and use the maturity-discharge payload: comparator, selected ingredient, current locus, and missing or lowering item. Without that payload, cap at `3`.
Omission account as maturity. A note explaining absence raises the value.	Add content to the body or neighboring pattern governing the claim, lower value, or mark the current request `repairBeforeUse`.
Semio-biased maturity. Non-semio pattern is judged by episteme or publication exemplars only.	Include non-epistemic mature comparators and score action on the primary `EntityOfConcern`.
Quality-evidence leakage. Corpus projection, retrieval evidence, README, ToC, `E.11`, or `I.2` alignment, monolith parity, `PatternQualityStatus`, developer, reviewer, or executor correspondence, or other quality evidence is written anywhere in the pattern as method, problem, note, appendix, relation, rationale, or status content about the pattern.	Move the evidence to the `E.21` result, `E.19` run record, README, ToC, `E.11`, `I.2`, card, retrieval, projection, or release or landing evidence locus; keep only the user-facing action or boundary that the evidence justifies.
Apparatus overwrap. A simple FPF claim is wrapped in extra role-word, publication-form, locus, flow, state, status, text-state, package, or process expressions, such as `current pattern text`, `current object`, `active record`, `field used in the current pass`, or route-like pattern talk where no real state or use relation is named, so the reader sees a bureaucratic apparatus instead of the object, relation, action, or boundary.	Apply `F.19`; record the scalar effect in `PrecisionRestorationProfile`, then lower the affected coordinates or name the completed repair.
Apparatus maximalism. Every pattern gets evidence cards, telemetry, archives, and companions.	Keep evidence compact unless it changes value, status, stop, or candidate comparison.
Quality veto theatre. "Not ready" has no E.21 coordinate named by value, evidence, status effect, and repair.	Rewrite as an `E.21` finding or remove the veto.

Consequences

Benefit	Trade-off or mitigation
Pattern quality becomes inspectable without a fake score.	Authors must name scope and all coordinate values.
Compact evidence remains possible.	The coordinate table is still complete.
Maturity claims become harder to fake.	Mature-pattern comparison adds cost where maturity or corpus-facing use is claimed.
Semio-bias becomes visible.	Semio distinctions remain auxiliary unless they are the pattern's own `EntityOfConcern`.
Stop decisions become less taste-based.	Open-ended improvement remains possible through `E.23` when a stronger aim is requested.

Rationale

E.21 keeps the declared measurement structure simple: one checked-object class, one ordinal scale, one required coordinate set, one non-arithmetic PatternQualityQBundle result payload, one local status set, and one stop-condition form. The specification marks no coordinate inactive; an evaluator applies them all, and the result episteme states what value the exact checked pattern edition and named evidence basis support under the declared use.

The mature-pattern parity coordinate tests whether formally clean wording also carries the worked slices, source carry-through, lowering conditions, and transfer coverage selected from mature FPF patterns for the declared use. Carry those selected ingredients in the body or the neighboring pattern that governs the claim; length alone establishes none of them.

SoTA-Echoing

This self-application uses the canonical E.8:11 definition and comparison contract; E.21 does not define a second meaning of SoTA. Its practice question is: how can one complete, use-scoped pattern evaluation expose semantic and practical defects, preserve distinct quality dimensions, and stop without turning a checklist or visible score into the value being sought? The selected answer is an FPF-local synthesis of four best-known branches. No cited source validates E.21's coordinate set or demonstrates inter-evaluator agreement; the comparison below states the exact transfers and limits instead of converting publication status, prevalence, freshness, or academic praise into rank. An official source would be admissible here if its answer won the same substantive comparison, not because it was official.

Practice question	Best-known line	Serious alternative or default	Defect overcome and E.21 mutation	Source roles and limits	Reopen condition
What evidence distinguishes pattern validation from a favorable review?	Riehle, Harutyunyan, and Barcomb's 2025 handbook method is the best-known-line candidate for explicit pattern discovery and validation through research questions, cases, observed applications, and evidence limits.	Expert approval, the rule of three, and one favorable quality review are the serious defaults.	The defaults hide what was tested and overread small positive histories. Adapt: E.21 evaluates one exact edition for one use and caps only claims that need absent actual-use evidence; reject calling one E.21 result universal validation or requiring a full research programme for every diagnostic use.	Riehle, Harutyunyan, and Barcomb, Pattern Discovery and Validation Using Scientific Research Methods (2025), supplies the validation branch but does not validate E.21. E.19 replay and E.21 assessment remain different results.	Reopen if stronger current pattern-validation practice changes the evidence needed for a declared validation or ordinary-use claim.
How can a multi-quality evaluation expose gaps and trade-offs without a hidden scalar score?	HELM is the best-known-line candidate for the bounded standardized-scenario and multi-metric comparison branch because it keeps scenarios, metrics, coverage gaps, and raw evidence inspectable together.	A single headline score, a convenient checklist subset, or a leaderboard is the serious default.	The default hides missing dimensions and compensation. Adapt: E.21 fixes scope and use first, keeps every required coordinate visible, names missing evidence, and forbids arithmetic aggregation; reject HELM's language-model taxonomy and any claim that standardization proves evaluator agreement.	Bommasani et al., Holistic Evaluation of Language Models (2023), concerns language models, not pattern texts. It supports coverage and replay discipline only; mature-pattern comparison and pattern-use evidence remain FPF-specific.	Reopen if current evaluation research supplies a lower-cost comparison with equal coverage, missingness, trade-off, and replay visibility.
What can cheap automated defect detection contribute without replacing semantic review?	Veizaga, Shin, and Briand's 2024 requirements-smell work is the best-known-line candidate for the bounded automated suspect-locus branch because it couples detection with inspectable defect classes and recommendations.	Treating a lint, smell detector, or checklist pass as the quality result is the serious default.	The default confuses search assistance with semantic and use judgement. Adapt: a bounded screen may seed `EvaluationEvidenceBasis`; reject using it as a coordinate value, practitioner-use test, completeness proof, or substitute for the complete table and profile.	Veizaga, Shin, and Briand, Automated Smell Detection and Recommendation in Natural Language Requirements (2024), reports natural-language requirements, Rimay patterns, and one industrial domain; it does not evaluate FPF patterns.	Reopen if a cross-domain method demonstrates broader semantic and use-defect coverage with declared limits at comparable effort.
What prevents optimization of visible quality values from replacing pattern value?	The best-known line for this narrow question treats visible indicators as defeasible proxies and keeps the intended values and trade-offs in the decision even when the indicator improves.	Targeting all `5`s, discharge counts, proof volume, or green checks is the serious default.	The default rewards apparatus and can worsen affordability, locality, or practitioner use. Adapt: `ProxyForValueSubstitutionResistance`, protected-quality questions, adjacent-value rationales, and the stop rule ask what became worse; reject transferring one reinforcement-learning mechanism as a universal causal model.	Karwowski et al., Goodhart's Law in Reinforcement Learning (2024), supplies current failure and counterexample evidence for proxy optimization, not a validation of E.21, a complete cross-domain theory, or a numeric quality model.	Reopen if a material proxy failure escapes the current checks or stronger proxy-risk evidence changes the protected-value and early-stop rule.

The combined answer is deliberately asymmetric: screening narrows where to look; the complete use-scoped evaluation constitutes the E.21 result; stronger validation claims require actual evidence suited to those claims; and currentness evidence only keeps the comparison replayable. More current citations cannot compensate for a missing serious alternative, defect, or pattern mutation.

Relations

Neighbour	Relation
`A.19`, `A.19.ECS`, `A.17`, `A.18`, `C.16`, and `C.16.Q`	Govern the characteristic space, object-specific evaluation specification, characteristics, scale/value bindings, measurement boundary, coordinate-result quality ascriptions, and precision of those ascriptions. E.21 supplies the pattern-quality coordinates, calibration, non-arithmetic `PatternQualityQBundle` result payload named by C.16.Q, aggregate result shape, and local status meanings.
`E.8.ECSPF`	Guides an author in carrying an accepted evaluation characteristic-space specification into practitioner-facing FPF pattern content. It keeps the specification, its `CharacteristicSpace`, the authored pattern, a later evaluation, and its result distinct.
`F.19`	Governs whole-span precise-language reading, repair, and local revalidation. E.21 consumes its compact quality effect through `PrecisionRestorationProfile` and lowers the affected existing coordinates. `E.10` supplies cues and unresolved word or kind routes.
`E.8`	Governs authoring of the pattern body whose exact edition E.21 assessment work evaluates and owns the canonical SoTA definition and positive comparison contract. E.21 consumes one completed `E.8:11` comparison when it assigns `SoTABindingAndCurrentness = 4` or `5`; it does not redefine that contract.
`A.13`, `A.15.1`, `A.3.1`, `F.6`, `A.2`, and `A.2.1`	Define or constrain the item 5 dated-assessment-Work account. A.13 supplies every precise evaluator-performer's core and same obtaining assignment; A.15.1 independently admits the Work from its performance history, temporal extent, enacted Method, and obtaining containing-System relation under the exact boundary and qualification window; F.6 adds only a current precise assignment-bound attribution. A compact account may omit an unused identifier only when every consumed relation remains recoverable. The Work, any returned value or direct evaluation-result relation, and the C.2.1 result episteme stay distinct. An E.21 claim connects them only through an exact A.6.1 result binding or a separately declared direct evaluation-result relation that actually obtains. An evaluator may ordinarily apply the questions without asserting dated Work. Route unresolved source role through `E.10.ROLE`.
`A.6.1`	Constrains only the exact declared-operation application admitted under the compact conditional rule in E.21:4.
`C.2.1`	Governs the constitution of the checked pattern episteme/version reference, per-coordinate result claims, aggregate pattern-quality-result episteme, and optional evaluation-record episteme independently.
`A.10` and `B.3`	A.10 governs evidence use/provenance and bounded reliance on the result; B.3 governs an actual named assurance claim about it. Witness presence and a favorable value create neither relation.
`F.10` and `G.11`	Govern downstream status use/interpretation and currentness. The local `PatternQualityStatus` value neither admits a pattern nor authorizes downstream use by itself.
`E.24.PUB` and `C.29`	E.24.PUB governs publication occurrence/form/carrier; C.29 governs any mathematical-lens use in representing a result or record; the coordinate claims and their justification remain in the E.21 result.
`E.19`	Declares admission and refresh review profiles and result boundaries. Dated E.19 review work may request or consume a current E.21 result, but its review work, findings/result, and authority-bearing admission or refresh decision remain separate from E.21 assessment work and coordinate results.
`E.22`	Frames purpose, floor, trade-offs, and proposal expectation before an evaluation.
`E.23`	Governs repeated improvement and repair work using the existing E.21 values and stop meanings for pattern versions.
`E.13`	Governs pragmatic utility and proxy-to-value alignment when quality values, visible measures, review results, all-`5` result framing, or release cues are used as practical value, target, incentive, gate, or improvement proof.
`E.9.DA`	Declares the DRR decision-adequacy characteristic space and result rules. Dated E.9.DA assessment work evaluates one exact upstream DRR episteme when pattern-quality defects trace to decisions; its checked object, work, and result are not E.21 objects.
`F.18`, `E.10`, `A.6.P`, `C.2.P`, `C.16.P`, and `C.16.Q`	Govern naming and wording-use precision when quality defects are lexical or ontological.
`A.20`, `A.21`, and `A.15`	A.20 governs internal-constraint validity for its stated transformation-flow subjects and cases; A.21 governs gate decisions; A.15 governs system-role–Method–Work alignment. Authority claims retain their separate direct relations. An E.21 result may be cited only through the exact receiving relation and supplies none of these by itself.
`E.11` and `I.2`	Govern entry-distribution and expanded entry-disambiguation cues; E.21 supplies only the scoped quality result.

E.21:End

Last Updated: 2026-09-10 — upstream FPF commit a87d0ef4 (github.com/ailev/FPF)

#FPF Pattern-Quality Evaluation CharacteristicSpace

#About this pattern

#How to use this pattern

#Relations

#Content

#Problem frame

#Problem

#Forces

#Solution

#Local names and kind settlement

#Evaluation configuration, application, result, and optional record

#Ordinal scale, result row, and adjacent-value rationale

#Precision-restoration profile

#RequiredPatternQualityCoordinates

#Frequent value-3, value-4, and value-5 calibration points

#Status and stop condition

#Consume Pattern-Edition Use-Value Evidence Noncompensatorily

#Compact result form

#Finding and proposal rows

#Archetypal Grounding - worked slices

#Complete compact evaluation

#Bias-Annotation

#Conformance checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

#Rationale

#SoTA-Echoing

#Relations

#E.21:End

FPF Pattern-Quality Evaluation CharacteristicSpace

About this pattern

How to use this pattern

Relations

Content

Problem frame

Problem

Forces

Solution

Local names and kind settlement

Evaluation configuration, application, result, and optional record

Ordinal scale, result row, and adjacent-value rationale

Precision-restoration profile

RequiredPatternQualityCoordinates

Frequent value-3, value-4, and value-5 calibration points

Status and stop condition

Consume Pattern-Edition Use-Value Evidence Noncompensatorily

Compact result form

Finding and proposal rows

Archetypal Grounding - worked slices

Complete compact evaluation

Bias-Annotation

Conformance checklist

Common Anti-Patterns and How to Avoid Them

Consequences

Rationale

SoTA-Echoing

Relations

E.21:End