FPF Reference

    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 one exact authored FPF pattern edition or bounded version must be evaluated for quality under the use required by the governing evaluation frame: ordinary practitioner use, authoring input, landing input, release input, external-review input, high-assurance reuse input, canonization input, or another explicitly requested pattern-quality use. E.21 declares the characteristic space, evaluation specification, and result rules; an evaluator system performs dated assessment work. 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 the current 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 referenceUnified Lexical Rules for FPF
    E.21explicit referenceEvaluation CharacteristicSpace Construction
    E.21explicit referenceU.Mechanism - Reusable Law-Governed Operation Declaration
    E.21explicit referenceU.Episteme: Constitution, Empirical Grounding, and Edition Relations
    E.21explicit referenceEvidence Graph Referring (C-4)
    E.21explicit referenceTrust & Assurance Calculus (F–G–R with Congruence)
    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 referenceCharacteristicSpace & Dynamics Hook (A.CHR‑SPACE)
    E.21explicit referenceFirst-Practical Entry and Pattern-Use Discoverability Discipline
    E.21explicit referenceExpanded Entry Disambiguation Cases
    E.21explicit referenceWording-Use Ontological Precision Restoration Architecture
    E.21explicit referenceLocal-First Unification Naming Protocol
    E.21explicit referenceOntology-First Plain Technical Rewriting
    E.21explicit referenceOntic Candidate Detection and First-Use Disposition
    E.21explicit referenceOntic Description and Publication Discipline
    E.21explicit referenceQ-Bundle: Authoring "-ilities" as Structured Quality Bundles
    E.21explicit referenceImprovement-Oriented Quality Evaluation Question Framing
    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 referenceRole-Method-Work Alignment (Contextual Enactment)
    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 referenceU.Work: Dated Performed Work Occurrence
    E.21explicit referenceRole Taxonomy
    E.21explicit referenceU.RoleAssignment - System Role Assignment
    E.21explicit referenceTelemetry-Driven Refresh & Decay Orchestrator
    E.21explicit referenceEpistemic Precision Restoration
    E.21explicit referenceCharacteristic and Scale Precision Restoration
    E.21explicit referenceFlow Constraint Validity — Eulerian
    E.21explicit referenceGateProfilization: OperationalGate(profile) (GateFit core)

    Content

    Problem frame

    Use this when one exact authored FPF pattern edition or bounded version must be evaluated for quality under the use required by the governing evaluation frame: ordinary practitioner use, authoring input, landing input, release input, external-review input, high-assurance reuse input, canonization input, or another explicitly requested pattern-quality use. E.21 declares the characteristic space, evaluation specification, and result rules; an evaluator system performs dated assessment work. 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 the current result.

    Not this pattern when the evaluated object is one DRR, an FPF-level corpus object, a single wording repair, a source-use decision, or a project-side evidence, assurance, gate, release, safety, compliance, work, or decision claim. Use E.9.DA, E.2.DA, E.10 and precision-restoration neighboring patterns named by value, or the project-side pattern governing the claim for those objects.

    First useful move: recover the required scope from the governing request, E.22 frame, campaign seam, landing check, release check, or review assignment; then name the exact checked pattern edition, required scope, working reader, intended use, qualification window, characteristic space/specification, semantic evaluation method, and evidence basis. When an actual result is required, identify the evaluator system, obtaining role assignment, dated assessment work, and exact A.6.1 evaluation application/bindings before constituting coordinate-result claims and the aggregate result episteme.

    floorEvaluation changes the declared floor and expected evidence economy. It never creates a partial E.21, inactive coordinates, overlay-trigger shortcuts, narrowing to an easier use, blocker-only substitution, or a permission to skip precision-restoration discharge. 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-claim scope and qualification window. The characteristic space/specification, evaluation configuration, method, evaluator assignment, assessment work/application, coordinate claims, aggregate result episteme, witnesses/evidence use, optional record, status use, admission, assurance, publication, and later repair are separate objects.

    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:

    1. Too weak. A reviewer marks a pattern "ready" because no blocker is obvious, because it landed, or because headings exist.
    2. 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

    ForceTension
    Comparability vs false precisionPattern versions must be comparable, but ordinal qualities cannot be averaged.
    Completeness vs affordabilityEvery coordinate is evaluated; rationale and evidence can stay compact.
    Maturity vs lengthA short pattern is mature only when selected mature-pattern ingredients are present in the body or neighboring pattern governing the claims.
    Ontology vs usabilityNames and kinds must be precise enough for the governed use without burying the first user-facing action.
    Semio precision vs semio-biasEpisteme and publication distinctions matter, but non-semio patterns still lead with their own EntityOfConcern.
    Open-ended improvement vs stopImprovement 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. It does not itself inspect a pattern, perform assessment work, assign coordinate values, create evidence use, issue assurance, admit a pattern, or repair it.

    For one actual pattern-quality evaluation, keep independently recoverable:

    1. one exact authored FPF pattern edition or bounded version as the checked object;
    2. the declared ClaimScope, working reader, intended receiving use, qualification window, evidence basis, and evaluation configuration;
    3. the selected U.CharacteristicSpace, this E.21 evaluation-specification episteme, every coordinate/scale binding, and the local result-form and status-value rules;
    4. one separately identified semantic evaluation U.Method;
    5. the evaluator U.System, obtaining U.RoleAssignment, dated assessment U.Work, enacted method, and exact A.6.1 evaluation application/bindings;
    6. 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;
    7. witnesses, comparator/source/case refs, exact A.10 evidence-use/provenance relations, and any B.3 assurance or reliance result;
    8. an optional evaluation-record episteme that packages those refs without performing assessment or creating the result;
    9. 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
    10. later E.23 improvement or other repair work and its changed pattern edition.

    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/calibration frame when used, U.ClaimScope, intended use, qualification window, assessment application, short rationale, and evidence locus. The complete same-bearer coordinate set forms the non-arithmetic PatternQualityQBundle payload carried by the aggregate result episteme; it is not an average, score, characteristic space, or second result. The evaluator system, evaluator viewpoint episteme if any, witness set, optional record, and receiving status or admission use remain separate.

    One conforming assessment/result shape applies:

    1. configure the checked pattern edition, scope, use, reader, window, characteristic space/specification, semantic evaluation method, and evidence basis;
    2. let dated evaluator work enact that method through the exact A.6.1 application/bindings and apply the ordinal scale to every required coordinate;
    3. constitute every coordinate-result claim with ShortRationale and the aggregate result episteme;
    4. assert the local PatternQualityStatus in that result;
    5. state its stop, repair, architecture-hold, or refresh condition; and
    6. when improvement is requested, return distinct finding or proposal claims without changing the coordinate result into a work plan or making the evaluation specification perform repair.

    There is no separate pre-check result. If a pattern lacks frame, first move, source basis, mature comparison, or naming clarity, the relevant coordinates fall.

    Local names and kind settlement

    Local nameKind and function
    PatternQualityEvaluationCompatibility compound label for the configured evaluation package. Any use resolves to the exact characteristic space/specification, configuration, assessment application/work, result episteme, witnesses/evidence-use relations, and optional record rather than treating this label as one kind or actor.
    PatternQualityCharacteristicSpaceRefReference to the exact A.19 U.CharacteristicSpace whose slots are the required E.21 coordinates and whose bindings use the E.21 ordinal scale; not an assessment, result, or record.
    PatternQualityEvaluationSpecRefReference 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.
    PatternOfConcernRefExact 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. This row does not create a special kind of pattern or a second text. 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.
    ClaimScopeQuality 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.
    WorkingReaderScopeWorking-reader family, viewpoint, and first-use situation the pattern must serve.
    IntendedUseAction that may use the result: continue drafting, admit for declared use, repair, refresh, or compare candidates.
    QualificationWindowEdition, SoTA, related-pattern, release, time, or comparison window in which the evaluation is current.
    EvaluationEvidenceBasisChecked 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, source-currentness locus when SoTA/currentness is valued, 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.
    QualityEvaluationQuestionFrameRefE.22 frame when purpose, floor, trade-offs, absorption, or proposal expectation needs to be declared.
    PatternQualityEvaluationConfigurationLocal input tuple binding the exact checked pattern, scope/use/reader/window, characteristic space/specification, semantic evaluation method, question frame when used, and evidence basis. It is neither a new U-kind nor performed work.
    SemanticPatternQualityEvaluationMethodRefReference to the exact semantic U.Method enacted by assessment work; the E.21 specification and coordinate table do not become that method merely by being consulted.
    PatternQualityAssessmentWorkRefExact dated A.15.1 U.Work performed by the evaluator system under an obtaining role assignment and enacted semantic evaluation method.
    PatternQualityEvaluationApplicationRefExact A.6.1 application and actual bindings connecting assessment work, checked pattern, evaluation configuration, and returned coordinate/result refs.
    CoordinateValueRationalesOne result claim for every required coordinate: Coordinate, Value, ShortRationale.
    CoordinateEvidenceRefsPer-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.
    PrecisionRestorationProfileCompact result profile over six precision-restoration 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. It collapses those layers into one scalar effect for the E.21 result, not one coordinate per defect. The profile names present or bounded issues, checked absence scope when clean, affected coordinates, and the selected restoration locus or concrete pattern contribution such as E.10, E.10.ARCH, F.18, F.19, E.24.CD, E.24.PUB, or an object-specific pattern.
    PatternQualityQBundleE.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/rationales, PrecisionRestorationProfile, local PatternQualityStatus, stop condition, and bounded non-use. The aggregate C.2.1 result episteme carries this payload; it is not a general C.25 engineering Q-Bundle, characteristic space, evaluation specification, method, work/application, evidence use, assurance, admission decision, or second record.
    DominanceSetCoordinates used to compare already evaluated candidate versions. It never changes the required coordinate set.
    PatternQualityResultRefOne C.2.1 result episteme whose EntityOfConcern is the exact checked pattern edition and whose ClaimGraph carries the same-bearer PatternQualityQBundle: declared use/window, every coordinate-result claim, PrecisionRestorationProfile, local status value, stop/repair condition, and bounded overread. It is not the bundle payload alone, assessment work, witness set, record, admission, or authority.
    PatternQualityWitnessRefsExact pattern loci, cases, comparators, sources, traces, or projection loci cited by result claims; witness presence is neither a value nor evidence use.
    PatternQualityEvidenceUseRefsExact A.10 evidence-use/provenance relations supporting reliance on result claims; they do not create those claims or the checked pattern.
    PatternQualityEvaluationRecordRefOptional C.2.1 record episteme packaging configuration, work/application, result, witness/evidence, non-use, and reopen refs. It performs no assessment and grants no status, admission, assurance, or authority.
    PatternQualityStatusLocal 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.
    StopConditionWhy improvement may stop, continue, refresh, or hold.

    Names are local to pattern-quality evaluation unless F.18 promotes a durable name. They are not project evidence, release state, review state, assurance, work, publication, or gate authority.

    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 used by assessment work>
  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>

PatternQualityAssessmentApplication:
  AssessmentWorkRef: <dated U.Work>
  EvaluatorSystemRef: <exact U.System>
  EvaluatorRoleAssignmentRef: <exact obtaining U.RoleAssignment>
  EnactedMethodRef: <same SemanticPatternQualityEvaluationMethodRef>
  A6_1ApplicationAndBindingRefs: <exact application, checked-object/configuration inputs, and returned-result bindings>
  EvaluationConfigurationRef:
  ReturnedCoordinateResultRefs:
  AggregateResultRef:

PatternQualityResultEpisteme:
  EntityOfConcern: <same exact PatternOfConcernRef>
  EffectiveReferenceScheme:
  ClaimGraph:
    PatternQualityQBundle:
      ClaimScope:
      WorkingReaderScope:
      IntendedUse:
      QualificationWindow:
      PrecisionRestorationProfile: <collapsed profile: word, head, and use; phrase-apparatus; repetition-and-distribution; ontic-slot clarity; description-publication-source boundary; pattern-application; scalar effect, affected coordinates, and selected restoration locus or concrete pattern contribution>
      CoordinateValueRationales: <all required coordinates, values, short rationales>
      CoordinateEvidenceRefs:
      PatternQualityStatus: <local result value>
      StopCondition: <local stop, first repair, hold, or refresh>
      BoundedNonUse:
  AssessmentApplicationRef:
  PatternQualityWitnessRefs:
  PatternQualityEvidenceUseRefs:
PatternQualityEvaluationRecord: <optional packaging of configuration, application/work, result, witness/evidence, non-use, and reopen refs only>

    An unfinished table, prose summary, or record with missing coordinate claims remains assessment material, not an E.21 result. The evaluation specification, characteristic space, method description, checklist, evidence-basis list, favorable local status, and optional record perform no work, constitute no coordinate value by themselves, and grant no admission, assurance, gate crossing, publication truth, or authority.

    Ordinal scale, result row, and adjacent-value rationale

    ValueLabelMeaning
    0absentThe characteristic is not expressed for the declared scope.
    1namedOnlyIt is named or implied but not usable as quality evidence.
    2partiallyExpressedForDeclaredUseIt is present but incomplete, fragile, or insufficient for the declared use.
    3sufficientlyExpressedForDeclaredUseIt is usable for the declared scope, with limits visible.
    4wellExpressedForDeclaredUseIt is clear, evidenced, and bounded for the declared scope.
    5exceptionallyExpressedForDeclaredUseIt 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:

    CoordinateValueShortRationale
    <E.21 coordinate><0..5><assigned-value basis; why the lower adjacent value would understate the evidence; why the higher adjacent value would overstate the evidence, or for 5 what evidence makes 4 too weak and what would lower or reopen>

    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.

    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: work, method, role, system, control, architecture, selection, engineering-action, or another pattern whose primary EntityOfConcern is not an episteme or publication. Value 4 requires by-value discharge of selected ingredients in the body or neighboring pattern governing 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.

    Precision-restoration profile

    Before assigning the coordinate table, record one PrecisionRestorationProfile. This is not an optional scan and not a lexical grep result. It is a pattern-text-use attention discharge: the evaluator asks which governed object, claim, relation, and reader use the sentence, table, section, or repeated content family serves in the pattern of concern.

    Use this compact shape:

    PrecisionRestorationProfile:
  overallEffect: <clean | boundedLocal | lowersCoordinates | repairBeforeUse>
  wordHeadUsePrecision: <clean | E.10, E.10.ARCH, F.18, or a concrete pattern contribution needed | lowers coordinates>
  mgdaColdReaderRecoverability: <clean | broad replacement | hidden specialization | defining, constraining, or checking pattern content missing | lowers coordinates>
  kindRestorationCheck: <pre-repair kind, relation, current ontic slot, relation position, use relation, or claim kind, and admissible use -> proposed post-repair kind, relation, current ontic slot, relation position, use relation, or claim kind, and admissible use; preserved | split | intentionally changed | blocker>
  phraseApparatus: <clean | F.19 needed | lowers coordinates>
  repetitionAndNegativeDistribution: <clean | bounded-local | lowers coordinates>
  onticAndSlotRelationClarity: <clean | hidden candidate ontic or slot-relation drift | lowers coordinates>
  descriptionPublicationSourceBoundary: <clean | description-publication-source boundary leakage | lowers coordinates>
  patternApplicationOntology: <clean | application relation unclear | lowers coordinates>
  checkedLoci: <sections, rows, cases, and relations checked>
  affectedCoordinates: <coordinates lowered or protected>
  repairProposal: <repair, no-repair disposition with loci, or owning locus>

    This profile deliberately collapses several small diagnostic checks into one scalar effect. The scalar is the strongest quality effect that any layer requires: clean, bounded local repair, coordinate lowering, or repair-before-use. The layers are diagnostic, not extra coordinates, checklists, or proposal quotas. A new precision-restoration symptom is classified into one of these layers or assigned to the selected restoration locus; it does not mint a new [E.21](/generated/patterns/E.21) coordinate. Details stay with concrete objects and contributions: word, head, and name problems apply [E.10](/generated/patterns/E.10), [E.10.ARCH](/generated/patterns/E.10.ARCH), or [F.18](/generated/patterns/F.18); phrase-level boilerplate and plain-technical rewriting apply [F.19](/generated/patterns/F.19); hidden candidate ontics and ontic-vs-description-vs-publication boundaries apply [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 may locate that content, but it is not merely a locator. 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 evaluation specification does not become an ontic-discovery pattern, and assessment work does not acquire ontic-authoring authority by noticing that defect. The kindRestorationCheck is required whenever a precision-restoration finding or repair proposal changes wording. It records the meaning-bearing object, kind, relation, current ontic slot, relation position, use relation, or claim kind, admissible use, and scope 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). [E.21](/generated/patterns/E.21) does not restate slot discipline, ontic architecture, publication-form discipline, or mathematical-lens ontology; it only checks that the repair preserved or deliberately changed them by value. The check is a bounded complete preservation proof, not a blanket demand to formalize every sentence and not a license to do the least visible work. Complete means every field whose value can drift because of the changed wording receives one explicit disposition: not triggered, ordinary prose, or no FPF-governed phrase changed with checked loci, preserved, split, intentionally changed by accepted decision, or blocker. A no-repair result is valid only as one of those dispositions with loci; “nothing to do” without that discharge is a missing repair. Expand the row only when a kind, relation, claim, current ontic slot, relation position, use relation, claim kind, or admissible use can drift. 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, and bounded non-use.

    RequiredPatternQualityCoordinates

    For every conforming E.21 result, dated assessment work applies the evaluation specification to every coordinate below, and the result episteme states every coordinate value and rationale.

    CoordinateWhat it evaluates
    WorkingSituationAndUseBoundaryRecognizabilityWhether the reader recognises the situation, ordinary use, non-use, harm if missed, and boundary early.
    EntityOfConcernAndClaimScopeStabilityWhether the primary EntityOfConcern and quality-claim scope stay stable across title, Problem frame, Solution, cases, checklist, relations, and status.
    PatternApplicationGuidanceWhether the Solution gives usable pattern-application guidance after the first move is recovered.
    ClosureAndBoundedNonUseRecoverabilityWhether stop conditions, repair conditions, bounded non-use, and any statements assigning a concrete defining, constraining, testing, or restoration contribution to a pattern are recoverable.
    SemanticKindAndNameRecoverabilityWhether names, kinds, relations, qualifiers, and claim boundaries recover the same FPF interpretation.
    NeighborAuthorityAndBoundedUseFitWhether evidence, assurance, measurement, naming, work, gate, decision, publication, release, and project claims stay with the pattern that defines or constrains each claim, relation, or boundary.
    EntityOfConcernPrimacyAndSemioBiasResistanceWhether the pattern leads with its own EntityOfConcern, first useful move, practitioner action, practical delta, and bounded non-use instead of letting description, publication, source, evidence, review talk, standard non-use warnings, precision-repair material, quality or projection evidence, package rationale, or cross-pattern reference boilerplate take over. The PrecisionRestorationProfile supplies the collapsed diagnosis across word, head, and use precision; phrase apparatus; repetition-and-distribution; ontic-slot clarity; description-publication-source boundary separation; and pattern-application ontology. This coordinate consumes that profile by lowering the value when those auxiliary materials compete with the pattern's positive subject and action guidance or ordered first-use actions. Semio-bias is one special case when the displaced content concerns descriptions, sources, publications, notes, records, diagrams, or evidence-like publications.
    PracticalUseDeltaAndHarmPreventionWhether the pattern changes a real reader use, prevents a named misuse, reduces a named cost, or preserves a named boundary.
    UseAffordabilityAndApparatusProportionalityWhether ordinary first use stays affordable and heavier apparatus appears only when it buys admissible use.
    RepairLocalityAndChangeImpactPredictabilityWhether repairs have the smallest locus and predictable downstream impact.
    ProxyForValueSubstitutionResistanceWhether 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.
    ClaimJustificationTraceabilityCurrentnessAndReplayabilityWhether the claim is replayable from pinned text, scope, evidence, currentness basis, limitations, status, and stop reason.
    CaseCountercaseAndTransferCoverageWhether positive cases, near-misses, anti-cases, and transfer cases match the breadth claimed.
    MaturePatternParityAndSelectedContentSufficiencyWhether selected mature-pattern ingredients are present in the body or related patterns for this EntityOfConcern and use.
    SoTABindingAndCurrentnessWhether current best-known practice changes the pattern and has reopen and currentness discipline.
    FormalClaimAdmissibilityAndLensFitWhether 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 or constrains them at the precision the claim needs, or correctly absent.
    FalsifiabilityAndLoweringConditionWhether coordinate values, status, and stop claims say what would raise, lower, or reopen the evaluation.
    CorpusEntryProjectionAndEcologyFitWhether 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.
    EvolutionFrontAndRefreshDisciplineWhether 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 coordinate that owns the content: related-pattern authority, traceability, formal-claim admissibility, falsifiability, affordability, corpus ecology, evolution, or refresh.

    Coupled-flow unity and separation for pattern quality. 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. 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; it does not decide whether a pattern is current, obsolete, under development, or being used. Treat FPF pattern development as the local pilot case: quality-loop proof supports separately performed edits; copying that proof into the pattern does not change the pattern by itself.

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

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

    Coordinate family3 is typical when4 is typical when5 is typical when
    WorkingSituationAndUseBoundaryRecognizabilityThe use situation is recoverable but late, abstract, or missing harm, payoff, or non-use detail.The situation, first move, harm, payoff, and non-use are early and clear.Early recognition is reinforced by a filled or replayable first-use slice showing that a cold practitioner can enter correctly.
    EntityOfConcernAndClaimScopeStabilityThe 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 non-use without any local apparatus stealing attention.
    PatternApplicationGuidanceThe 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.
    ClosureAndBoundedNonUseRecoverabilityNon-use or related-pattern statements are present but not tied to stop, repair, or lowering conditions.Stop, repair, bounded non-use, and concrete defining, constraining, testing, or restoration contributions for specific claims, relations, or boundaries are recoverable for declared use.A worked stop, overturn, or non-use case shows how closure changes status or the next applicable pattern relation.
    NeighborAuthorityAndBoundedUseFitRelated patterns are named but some authority split remains generic, future-pattern-like, ambiguous, role-nicknamed, or too early in the Solution.Related patterns named by value and limited declarative relations are clear enough for declared use and do not replace the pattern's own content.Related-pattern authority is replayable across examples, relations, and overread cases, with pattern application and authority kept explicit.
    EntityOfConcernPrimacyAndSemioBiasResistanceThe pattern is about its object but one or more precision-restoration layers lead or leak into the pattern in a developer, reviewer, or evaluator role.The pattern leads with its own object and application guidance; auxiliary material is compact, declarative, and late; role, slot, publication-form, source, locus, flow, and status words 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.
    PracticalUseDeltaAndHarmPreventionThe prevented harm is named but not demonstrated.The pattern changes a recoverable use and blocks named misuse for declared use.A worked or near-miss case shows the practical delta, cost of the missed pattern, and prevented harm.
    UseAffordabilityAndApparatusProportionalityThe 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.
    RepairLocalityAndChangeImpactPredictabilityRepair 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.
    ProxyForValueSubstitutionResistanceProxy 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 stop.
    ClaimJustificationTraceabilityCurrentnessAndReplayabilityFields 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.
    CaseCountercaseAndTransferCoverageArchetypes 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.
    MaturePatternParityAndSelectedContentSufficiencyMature 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.
    SoTABindingAndCurrentnessSources are relevant and not decorative, but currentness, source-use status, or reopen conditions are compact or incomplete.Decision-governing sources state adopt, adapt, or reject disposition, content mutation, currentness window, and reopen condition.The pattern compares current best-known practice against popular, official, or lineage alternatives and carries the resulting source decisions into solution, cases, boundaries, and refresh.
    FormalClaimAdmissibilityAndLensFitFormal, 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 or constrains them 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.
    FalsifiabilityAndLoweringConditionStop, waiver, or non-use fields exist, 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.
    CorpusEntryProjectionAndEcologyFitHost 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.
    EvolutionFrontAndRefreshDisciplineReopen 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. This is a pattern-text-use evaluation, not a lexical search: 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 owns that work, not in the pattern. Related-pattern statements named by value can be true and still damage the pattern of concern when they appear before the pattern's own EntityOfConcern and application guidance are recoverable. If the opening Problem frame or Solution starts with precision-restoration material before the pattern's own subject and move, this coordinate is at most 2; if a positive action exists but the reader must traverse that material across sections to find it, it is at most 3. Compact related-pattern statements belong in Relations or short late boundary rows and must preserve kind. Local boundary prose is admissible only when it states a documented local confusion and local stop condition not already carried by the owning pattern for that specific distinction or claim boundary. Also lower PatternApplicationGuidance, WorkingSituationAndUseBoundaryRecognizability, PracticalUseDeltaAndHarmPrevention, and UseAffordabilityAndApparatusProportionality when the profile shows that precision-restoration issues displace first-use content. 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

    StatusMeaning
    admissibleForDeclaredUseEvery coordinate meets the declared floor for the scoped use, and bounded non-use is stated.
    repairBeforeUseOne or more coordinate floors fail for the declared use.
    holdForArchitectureDecisionThe defect is not local prose; EntityOfConcern, neighbour authority, split, merge, or placement must be decided.
    refreshNeededA 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. A diagnostic or exploratory request still measures every coordinate and reports values; it does not create an admissible-use shortcut. If the assignment 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. Dated assessment work 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 conditionMandatory E.21 consequence
    A required prior-edition use probe is regressedSet 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 useSet 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 useDo 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 useNo blocker follows from that check. Its evidence may support affected existing coordinates but establishes neither their values nor status by itself.
    The pattern's positive subject, problem, action, and result guidance is absent or unusable: its own EntityOfConcern, first useful move, practitioner action, practical delta, or bounded non-use cannot be recoveredSet 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, or false closure claimSet status to repairBeforeUse. SemanticKindAndNameRecoverability is at most 2; each of EntityOfConcernAndClaimScopeStability, NeighborAuthorityAndBoundedUseFit, FormalClaimAdmissibilityAndLensFit, and PatternApplicationGuidance is also at most 2 when the unresolved member affects that coordinate's claim.
    A required prior-edition use is discoverably transferredNo 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 boundaryNo regression blocker follows. Evaluate the corrected use and harm prevention on their own evidence.
    The material-change trigger is falseApply 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>
    PrecisionRestorationProfileOverallEffectKindRestorationCheckLociAffectedCoordinatesRepairProposal
    <word, head, and use; phrase-apparatus; repetition-and-distribution; ontic-slot; description-publication-source; pattern-application profile>`<cleanboundedLocallowersCoordinatesrepairBeforeUse>`<pre-repair and post-repair kind, relation, current ontic slot, relation position, use relation, or claim kind, and not-triggered, ordinary, preserved, split, changed, or blocker disposition>
    CoordinateValueShortRationale
    <all RequiredPatternQualityCoordinates rows><0..5><assigned-value basis; why not lower; why not higher or what would lower or reopen>
    First repair or stop: <repair | hold | local stop>
Reopen if: <smallest changed locus or condition>

    Status is not assigned from a two-column table, a prose summary, a checklist count, an E.19 pass or fail row, a table missing ShortRationale, a result missing the required PrecisionRestorationProfile, or a result missing the evidence basis needed for its values. Such material can support later assessment work, but it is not the E.21 result episteme. Conversely, the local PatternQualityStatus asserted by that result is not a release crossing: separate E.19 review work and result, plus the authority-bearing release or admission work/decision named by value, govern gate-specific carry-through, projection, monolith, packaging, authority, and non-overread conditions.

    Finding and proposal rows

    E.21 finding:
  Pattern of concern: <PatternOfConcernRef>
  Coordinate or status affected: <coordinate | status | stop>
  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, add finding rows for every below-floor coordinate and proposal rows only for substantive non-dominated improvement opportunities inside the declared scope. 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. A 4 can be the correct stop value only with a checked no-proposal disposition showing why further content movement is dominated, unavailable, or outside scope.

    Archetypal Grounding - worked slices

    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 about architecture, work, system levels, method, P2W, or another non-semio EntityOfConcern tries to introduce the subject through a catalog of other claim kinds or objects that are outside its own subject. That catalog is unbounded because every EoC is outside infinitely many other EoCs. If copied boundary doctrine leads the Problem frame or Solution, EntityOfConcernPrimacyAndSemioBiasResistance falls to 2 or 3 even when every individual boundary is true. Repair by leading with this pattern's own EntityOfConcern, first useful move, practitioner action, practical delta, bounded non-use, and positive subject and action guidance; replace copied boundary doctrine with one relevant pattern ID plus the concrete definition, constraint, test, or repair relation it supplies, unless a documented local confusion needs a local stop condition not already carried there. If the same doctrine is spread across Problem frame, Solution, anti-patterns, checklist, and Relations, classify the aggregate under the profile's repetition-and-distribution layer and repair the distribution, not just each local sentence.

    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. Repair by moving discoverability to README, ToC, E.11, I.2, or retrieval or projection loci, moving compact pattern references and their concrete definition, constraint, test, or repair contribution to Relations or a late boundary row, moving architecture-placement rationale to DRR or architecture documents, and rewriting the Solution to answer “what do I do with this pattern's EoC?” before any statement about another pattern.

    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, or 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, 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 result, E.19 run record, README, ToC, E.11, 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; record no-proposal only with 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

    CheckRequirement
    CC-E21-0Keep the exact checked pattern edition, characteristic space/specification, evaluation configuration, semantic method, evaluator system and obtaining role assignment, dated assessment work, A.6.1 application/bindings, coordinate-result claims, aggregate result episteme, witnesses/evidence-use relations, optional record, local status value, F.10 status use, E.19 admission/refresh decision, assurance, publication, currentness, and later repair independently recoverable. No declaration, profile, checklist, record, or result performs the assessment or grants authority.
    CC-E21-0aConstitute each coordinate value as a quality ascription about the same exact checked pattern edition with recoverable ReferenceScheme, characteristic, scale value, evaluation rule/probe, scope/use/window, assessment application, 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-1Recover ClaimScope from the governing request, E.22 frame, campaign seam, landing check, release check, or review assignment; then name PatternOfConcernRef, ClaimScope, WorkingReaderScope, IntendedUse, QualificationWindow, and EvaluationEvidenceBasis.
    CC-E21-2Evaluate the full RequiredPatternQualityCoordinates set.
    CC-E21-2aBefore assigning coordinate values, record one PrecisionRestorationProfile with word, head, and use; phrase-apparatus; repetition-and-distribution; ontic-slot; description-publication-source; and pattern-application layers. A missing, grouped, or memory-only profile makes the E.21 result incomplete.
    CC-E21-3Use 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-4Let floorEvaluation change floor and evidence cost only, not the coordinate set.
    CC-E21-5Assign values from checked pattern content and named content evidence, not review, landing, popularity, praise, or absence of prior use.
    CC-E21-6For 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-6aKeep 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 govern 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. This is a role test, not a word-list test. 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-7For any 5, name the reinforcing evidence loci required by that coordinate's 5 meaning; otherwise lower the coordinate to 4 or below.
    CC-E21-8For 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-9Make SoTA rows adopt, adapt, or reject current practice and change the pattern.
    CC-E21-10Keep 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 or constrains the claim when the evaluated pattern makes those claims.
    CC-E21-11State floor satisfaction, remaining bounded non-use, and lowering or reopen conditions in any stop claim.
    CC-E21-12Keep coordinate rationale separate from improvement proposal rows.
    CC-E21-13Keep quality results out of project evidence, assurance, gate, work, safety, compliance, release, and publication truth claims.
    CC-E21-14Do 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-15Keep 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 positive subject and action guidance. A no-proposal disposition must name checked loci and why no substantive content improvement remains.
    CC-E21-16When 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-patternRepair
    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 bounded non-use; never raise a value by adding evaluation apparatus that worsens use, locality, affordability, or ecology.
    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.
    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, publication-form, locus, flow, state, status, text-state, package, or process words, 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

    BenefitTrade-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; dated assessment work 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 is deliberately strict because recent short patterns looked formally clean while lacking the worked slices, source carry-through, lowering conditions, and transfer coverage present in mature FPF patterns. The repair is not "make everything long"; it is "carry the selected mature ingredients that the declared use needs."

    SoTA-Echoing

    ClaimSource-use dispositionConcrete E.21 effect
    Feedback connects desired state, current state, next action, and available tactics.Adopt from formative-assessment lineage such as Sadler and Hattie and Timperley.ShortRationale and proposal rows are separated: value now, next improvement when requested, and checked no-proposal when no substantive improvement remains.
    Questions and metrics derive from the goal.Adopt from GQM and GQM+Strategies measurement discipline.Scope, reader, use, and window precede coordinate values.
    Multi-criteria improvement needs explicit trade-offs.Adopt from MCDA, Pareto, ATAM, and current QD and OEE lines.Dominance comparisons and protected trade-offs replace one-score closure.
    Proxy optimization can make intended value worse.Adopt from Goodhart and Campbell, management-accounting surrogation, reward-hacking, and specification-gaming lines.ProxyForValueSubstitutionResistance, PrecisionRestorationProfile, E.13, and stop condition ask what got worse; 5, all-5, discharge count, and proof apparatus cannot replace pattern content or pragmatic value.
    Evaluation results are not governance, safety, or compliance proof.Adopt as non-overread boundary from current evaluation-governance practice.Neighbour authority and status boundaries keep project claims outside E.21.

    Relations

    NeighbourRelation
    A.19, A.19.ECS, A.17, A.18, C.16, and C.16.QGovern 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.ECSPFPublishes an evaluation CharacteristicSpace as an FPF pattern when that form is selected.
    E.8Governs authoring of the pattern body whose exact edition E.21 assessment work evaluates.
    A.15.1, A.6.1, A.2, and A.2.1Govern dated assessment work, actual evaluation application/bindings, evaluator role, and obtaining role assignment. The E.21 specification, characteristic space, profile, result, and optional record perform none of these.
    C.2.1Constitutes 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.3Govern exact evidence use/provenance and any assurance or reliance on the result. Witness presence and a favorable value create neither relation.
    F.10 and G.11Govern 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.29Govern publication occurrence/form/carrier and representation of a result or record; publication does not perform assessment or strengthen its claims.
    E.19Declares 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.22Frames purpose, floor, trade-offs, and proposal expectation before an evaluation; it neither performs assessment nor assigns coordinate values.
    E.23Governs repeated improvement and repair work using E.21 values and stop meanings for pattern versions; it does not become the original assessment or result.
    E.13Governs 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.DADeclares 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.QGovern naming and wording-use precision when quality defects are lexical or ontological.
    A.20, A.21, and A.15Govern project-side local CV state, gates, work, and authority. An E.21 result may be cited only through the exact receiving relation and supplies none of these by itself.
    E.11 and I.2Govern entry-distribution and expanded entry-disambiguation cues; E.21 supplies only the scoped quality result.

    E.21:End

    Last Updated: 2026-08-04 — upstream FPF commit 67092138 (github.com/ailev/FPF)