FPF Reference

Wording-Use Ontological Precision Restoration Architecture

E.10.ARCH · Stable · Architectural (E) · Normative unless explicitly marked informative · 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: Architectural (E) Status: Stable Normativity: Normative unless explicitly marked informative

Plain-name. Wording ontology repair architecture.

Intent. Keep FPF wording-use precision restoration distributed without letting every receiving pattern grow its own first-stage trigger registry. E.10 catches one overloaded wording use; E.10.ARCH says which applicability rows exist, how one row selects the first applicable restoration or receiving pattern, and when repeated repair-only prose should be extracted from a subject pattern.

E.10.ARCH is not a generic language-cleanup pattern. Its mechanism is ontological reconstruction: recover what kind of thing is being talked about, which neighboring governed objects are admissibly involved, which relation or source-transfer posture is live, and, when plain ontology is not enough, which mathematical lens under C.29 or which pattern-defined formal apparatus makes the candidate structure checkable. The output returns to wording only after that kind/use structure is recoverable.

Builds on. E.10, A.6.P, A.6.F, C.2.P, A.6.3.CSC, F.18, E.8, E.19, and E.2.

Coordinates with. A.22, C.30, C.30.ASV, exact C.30.* structure/view patterns, C.16, A.17, A.18, A.19, C.25, C.27, C.29, E.21, J.4, and exact evidence, assurance, gate, work, decision, causal-use, release, and publication patterns when those claims are live.

Use this pattern when a recurring FPF-facing wording-use problem cannot be closed by one local E.10 rewrite because the wording hides a stable governed-object-kind/use field set, a stable recovery apparatus, and a useful remaining reader move.

Relations

E.10.ARCHbuilds onLEX-BUNDLE: Unified Lexical Rules for FPF
E.10.ARCHbuilds onRelational Precision Restoration (RPR) — Kind-Explicit Qualified Relation Discipline
E.10.ARCHbuilds onFunction and Functional Precision Restoration (RPR-FUNCTION)
E.10.ARCHbuilds onEpistemic Precision Restoration
E.10.ARCHbuilds onControlled Semantic Coarsening
E.10.ARCHbuilds onLocal-First Unification Naming Protocol
E.10.ARCHbuilds onFPF Authoring Conventions and Style Guide
E.10.ARCHbuilds onPattern Quality Gates: Review and Refresh Profiles
E.10.ARCHbuilds onThe Eleven Pillars
E.10.ARCHcoordinates withArchitecture and Structure Precision Restoration
E.10.ARCHcoordinates withCharacteristic and Scale Precision Restoration
E.10.ARCHcoordinates withQuality-Term Precision Restoration
E.10.ARCHcoordinates withStructure and Structural Views (STRUCT-CAL)
E.10.ARCHcoordinates withArchitecture Description Adequacy (ADA)
E.10.ARCHcoordinates withArchitecture Structural View Adequacy (ASV)
E.10.ARCHcoordinates withMM-CHR — Measurement & Metrics Characterization
E.10.ARCHcoordinates withCharacteristicSpace & Dynamics Hook (A.CHR-SPACE)
E.10.ARCHcoordinates withQ-Bundle: Authoring "-ilities" as Structured Quality Bundles
E.10.ARCHcoordinates withTemporal Claim Adequacy: State Readings, Temporal Trends, and Intervention-Sensitive Temporal Change
E.10.ARCHcoordinates withMathematical Lens Adequacy (MLA)
E.10.ARCHcoordinates withFPF Pattern-Quality Evaluation CharacteristicSpace
E.10.ARCHcoordinates withFirst Practical Entry Neighborhood Index
E.10.ARCHoutline parentLEX-BUNDLE: Unified Lexical Rules for FPF
E.10.ARCHoutline next siblingConceptual Prefixes (policy & registry)
E.10.ARCHexplicit referenceLEX-BUNDLE: Unified Lexical Rules for FPF
E.10.ARCHexplicit referenceRelational Precision Restoration (RPR) — Kind-Explicit Qualified Relation Discipline
E.10.ARCHexplicit referenceFunction and Functional Precision Restoration (RPR-FUNCTION)
E.10.ARCHexplicit referenceEpistemic Precision Restoration
E.10.ARCHexplicit referenceControlled Semantic Coarsening
E.10.ARCHexplicit referenceLocal-First Unification Naming Protocol
E.10.ARCHexplicit referenceFPF Authoring Conventions and Style Guide
E.10.ARCHexplicit referencePattern Quality Gates: Review and Refresh Profiles
E.10.ARCHexplicit referenceThe Eleven Pillars
E.10.ARCHexplicit referenceStructure and Structural Views (STRUCT-CAL)
E.10.ARCHexplicit referenceArchitecture Description Adequacy (ADA)
E.10.ARCHexplicit referenceArchitecture Structural View Adequacy (ASV)
E.10.ARCHexplicit referenceMM-CHR — Measurement & Metrics Characterization
E.10.ARCHexplicit referenceA.CHR-NORM — Canonical “Characteristic” & rename (Dimension/Axis → Characteristic)
E.10.ARCHexplicit referenceA.CSLC-KERNEL — Minimal CSLC in Kernel (Characteristic/Scale/Level/Coordinate)
E.10.ARCHexplicit referenceCharacteristicSpace & Dynamics Hook (A.CHR-SPACE)
E.10.ARCHexplicit referenceQ-Bundle: Authoring "-ilities" as Structured Quality Bundles
E.10.ARCHexplicit referenceTemporal Claim Adequacy: State Readings, Temporal Trends, and Intervention-Sensitive Temporal Change
E.10.ARCHexplicit referenceMathematical Lens Adequacy (MLA)
E.10.ARCHexplicit referenceFPF Pattern-Quality Evaluation CharacteristicSpace
E.10.ARCHexplicit referenceFirst Practical Entry Neighborhood Index
E.10.ARCHexplicit referenceSignature Stack & Boundary Discipline
E.10.ARCHexplicit referenceArchitecture and Structure Precision Restoration
E.10.ARCHexplicit referenceCharacteristic and Scale Precision Restoration
E.10.ARCHexplicit referenceQuality-Term Precision Restoration
E.10.ARCHexplicit referenceImprovement-Oriented Quality-Read Question Framing
E.10.ARCHexplicit referenceDRR Decision-Adequacy Evaluation CharacteristicSpace
E.10.ARCHexplicit referenceU.ActionInvitationPrecisionRestoration — Affordance / Action-Invitation Precision Restoration (ACT-INV)
E.10.ARCHexplicit referenceWork-Relevant Source Restoration
E.10.ARCHexplicit referenceU.BaseDeclarationDiscipline - Kind-explicit, scoped, witnessed base declaration discipline (with base-change lexicon)
E.10.ARCHexplicit referenceEvidence Graph Referring (C-4)
E.10.ARCHexplicit referenceTrust & Assurance Calculus (F–G–R with Congruence)
E.10.ARCHexplicit referenceU.Flow.ConstraintValidity — Eulerian
E.10.ARCHexplicit referenceGateProfilization: OperationalGate(profile) (GateFit core)
E.10.ARCHexplicit referenceRole-Method-Work Alignment (Contextual Enactment)
E.10.ARCHexplicit referenceDecision Theory (Decsn-CAL)
E.10.ARCHexplicit referenceCausalUse-CAL: Causal-Use Questions, Causality-Ladder Rungs, Identification and Realizability

Content

Use this when

Use this pattern when a recurring FPF-facing wording-use problem cannot be closed by one local E.10 rewrite because the wording hides a stable governed-object-kind/use field set, a stable recovery apparatus, and a useful remaining reader move.

Use it especially when a subject or adequacy pattern contains repeated first-stage repair prose such as:

  • architecture-vs-diagram, model, graph, ADR, dashboard, view, or layer triage before the architecture pattern can start;
  • axis, dimension, feature, property, metric, indicator, score, strong, weak, robust, level, coordinate, threshold, or scalar-quality triage before a characteristic or scale pattern can start;
  • quality-term repair that decides between relation construction, quality/evaluative characterization, Q-bundle use, pattern-quality coordinate use, action invitation, bridge, or exact receiving pattern;
  • source, publication, carrier, face, PublicationUnit, dashboard, documentation, or source-return wording whose project-side use is not yet recovered;
  • relation-like, function-like, evidence-like, assurance-like, gate-like, work-like, decision-like, causal-use, release, or naming wording whose exact receiving pattern is already known or must be recovered before the sentence is admitted.

What goes wrong if missed. FPF accumulates many small local trigger lists. One pattern says "architecture is not a diagram", another says "metric is not proof", another says "quality is not one scalar", and a reviewer cannot tell which pattern owns the repair. The text looks more precise, but the reader does not get a stable first move.

What this buys. E.10.ARCH gives one architecture for distributing wording-use repair: E.10 catches; E.10.ARCH selects the row and extraction criterion; a realization pattern or exact neighbor recovers the ontology; the subject pattern returns to its own governed object.

First useful move. Decide whether the wording can close locally under E.10, already has an exact receiving pattern, or needs one applicability row with a stable ontologicalNeighborhood, recovery apparatus, and remaining reader move.

Not this pattern when.

  • If a sentence is repaired locally under E.10, stop there.
  • If the exact receiving pattern and governed object are already recoverable by value, use that receiving pattern directly.
  • If the live object is evidence, assurance, gate, work, decision, causal-use, release, mathematical-lens adequacy, architecture-description adequacy, structural-view adequacy, characteristic-space construction, Q-bundle construction, pattern-quality evaluation, or another exact FPF object, the exact receiving pattern governs its own invariant. E.10.ARCH only governs the wording-use restoration distribution.

Governed object

The governed object is the local FPF architecture of WordingUseRestorationApplicabilityRow rows.

A WordingUseRestorationApplicabilityRow is a pattern-local row over one recurring governedObjectKindUseFields field set and one ontologicalNeighborhood. It states:

  • the trigger source recognized by E.10;
  • the primary governed object kind and encountered object kind;
  • the relation between encountered object and governed object;
  • the exact FPF kind or relation recovered when live;
  • claim posture when live;
  • source-transfer posture when live;
  • sentence role;
  • admissible use;
  • non-use boundary;
  • remaining reader move;
  • first applicable restoration or receiving pattern;
  • recovery product;
  • first return to the subject pattern.

WordingUseRestorationApplicabilityRow is not a U.* kind, not a conformance record, not a process task, not a deontic obligation, and not a durable project record by itself.

WordingUseRestorationApplicabilityTable is the pattern-local publication table of such rows. It is not a pattern cluster, workstream, campaign, module, semantic parent, or authority object.

ontologicalNeighborhood means the FPF applicability neighborhood around the primary governed object kind, admissible adjacent object kinds, relations, descriptions, carriers, source-transfer postures, use boundaries, and the stable apparatus that makes the recovery checkable. It is not textual proximity, filename proximity, ToC proximity, alphabetic proximity, workstream grouping, topic grouping, discipline column, domain label, or pattern-nest placement.

pattern nest means a numbering or placement grouping such as A.6.*, C.16.*, or C.30.*. One applicability row may point to a realization pattern in one pattern nest, but the row and the nest are not the same concept.

Distribution architecture

The standing construction is:

  1. E.10 catches an FPF-force-bearing wording use and either closes it locally or selects an exact receiving pattern, controlled precision-reduction pattern, durable-name path, or fail-closed non-use disposition.
  2. E.10.ARCH maintains the shared recovery algorithm and the WordingUseRestorationApplicabilityTable.
  3. A realization pattern or retained exact pattern such as A.6.P, A.6.F, C.2.P, C.30.P, C.16.P, or C.16.Q unpacks the wording according to the shared algorithm for one selected ontologicalNeighborhood.
  4. Additional applicability rows, and only when needed additional realization patterns, appear when repeated FPF-facing wording hides a stable governed-object-kind/use field set, a stable recovery apparatus, and a useful remaining reader move that no existing exact pattern already carries.
  5. E.8 governs publication-form and placement wording such as ontologicalNeighborhood and pattern nest.
  6. E.19 checks that authored pattern hosts preserve this distribution and do not keep rival first-stage repair doctrine.

This architecture keeps E.10 compact. It also keeps subject receiving patterns centered on their own intensional objects, decisions, characteristics, structures, mathematical lenses, consequences, and worked uses.

Rationale and source posture

This distribution is selected because the recurring failure is not "too few word rules". The failure is that repair-only trigger prose migrates into subject patterns and begins to compete with their governed objects. A workable FPF answer therefore needs three separations at once: a cheap shared trigger scan in E.10, a shared recovery architecture in E.10.ARCH, and local realization only where an ontologicalNeighborhood has its own stable field set and remaining reader move.

BasisSource postureWhat the basis mutates in E.10.ARCH
Current FPF distribution: E.10, A.6.P, A.6.F, C.2.P, C.30.P, C.16.P, C.16.Q, F.18, E.8, E.19, and J.4.Current FPF-internal architecture evidence; this is the primary support for the selected distribution.Keeps E.10 compact, makes E.10.ARCH the single shared algorithm owner, sends relation/source/architecture/characteristic/quality/function/naming cases to exact realization or receiving patterns, and gives E.19 a distribution-preservation check.
Pattern-language locality and FPF governed-object discipline in E.8 / E.19.Current FPF authoring and review support; not an external standard imported as ontology.Forces thin receiving-pattern pointers and blocks local trigger-registry copies inside subject patterns whose real work is architecture, structure, characteristic, quality, evidence, gate, work, decision, or release.
Terminology and controlled-vocabulary practice named in E.10:11a only where it concerns designations, labels, discoverability, and controlled vocabulary publication.Current-standard/reference-only and practice support; it does not define FPF kind ontology.Supports explicit recovered heads and reusable-name discipline, but rejects a central word list or controlled vocabulary as the solution to every wording-use repair.
Current exact receiving-pattern growth in FPF.Reopen pressure, not proof of this pattern's authority.Requires a row to be removed, narrowed, or changed when a new exact receiving pattern can carry the live object directly, or when realization patterns start copying the shared algorithm back into local prose.

The selected architecture is lowered or reopened when one of those bases changes: if E.10 can close the issue locally, if a new exact receiving pattern removes the need for a restoration row, if a realization pattern needs a different stable field set, or if subject patterns again start carrying duplicated first-stage trigger registries.

Shared recovery algorithm

Use this recovery order for FPF-relevant wording-use restoration cases. Each realization pattern may publish a compact local form, but the order stays shared.

  1. Trigger and bounded text. Name the bounded text object, exact trigger span, local sentence role, register posture, and whether the text is conformant FPF, FPF-bound project text, or source text being unpacked before transfer.
  2. Cheap local closure. Check whether the wording has no FPF force or only a small local head/register/morphology repair. If yes, repair locally under E.10, state the remaining reader move, and stop.
  3. Head kind and candidate ontology. Recover the head kind, register posture, I/D/S lane, candidate referents, candidate governed objects, candidate relations, candidate carriers or publications, and live scope, time, viewpoint, or context facets. Include literal and intended candidates when metonymy or compression is plausible.
  4. Ontological neighborhood and receiving-pattern selection. Select the ontological neighborhood and first applicable receiving pattern by governed object kind and admissible adjacent objects: relation construction, function-like carrier recovery, episteme/publication/source-transfer, selected structure or architecture description, characteristic/scale construction, quality characterization, evidence, assurance, gate, work, decision, causal-use, naming, controlled coarsening, or another exact FPF pattern.
  5. Formal apparatus or stable substrate. State the stable apparatus that makes the repair checkable: relation slots, publication stack, source-transfer disposition, selected structure, architecture question, characteristic/scale construction, quality bundle, mathematical lens, evidence path, gate record, work occurrence, decision record, assurance argument, causal-use record, or exact receiving-pattern field set.
  6. Normalized ontology and lexical projection. Produce the repaired wording, compact repair note, record-shaped value, exact receiving-pattern application, or non-use disposition. Do not replace one umbrella word with another.
  7. Admissible use and remaining reader move. State the admissible use, non-admissible stronger or adjacent use, and one useful reader move. If the wording is type-correct but inert, the repair is incomplete.

The sequence is shared; each wording-use restoration case differs by governed object kind/use fields, ontological neighborhood, receiving pattern, substrate, and result.

Applicability table

Ontological neighborhoodFirst applicable patternTrigger familyRequired recovery apparatusTypical recovery product
Relation construction; primary object is relation use or relation-bearing claimA.6.P and retained exact A.6 relation specializationsRelation, endpoint, qualifier, slot, scope, time, viewpoint, evidence-role distinction where live, basedness, service, bridge wording, whole/part, mapping, comparison, dependency, or evaluative ascription when the hidden claim is relation construction.RelationKind, slot discipline, QualifiedRelationRecord, endpoint facets, qualifiers, L/A/D/E hooks, and exact retained relation specializations.relation rewrite, relation record, candidate-set note, exact specialization application, or fail-closed Plain disposition.
Function-like wording; primary object is the carrier hidden by function, functional, functionality, effect, or similar wordingA.6.F first when the carrier is not already recovered; direct exact receiving pattern when it is recovered by valueFunctional architecture, required transformation or effect, holon capability, method, work occurrence or result, role expectation, mathematical function, relation, loss, objective, quality or functionality claim, module allocation, interface/signature relation, or evidence/assurance/gate/decision overread.FunctionUseRepair, carrier-kind recovery, false-carrier list, exact governing-pattern reference, C.30 / C.30.ASV functional-structure boundary, C.29 mathematical-lens boundary, C.16 / C.25 quality boundary, A.6.M module/interface and A.6 signature-stack exits.carrier assignment, exact receiving-pattern application, FunctionFlowModuleAlignmentNote, mathematical-lens exit, quality/characteristic exit, A.6.M module/interface exit, ordinary-prose demotion, or stop.
Episteme/publication/source-transfer; encountered object may be source span, carrier, face, publication, PublicationUnit, or text-work evaluation cueC.2.P first; exact evaluation pattern after recovery when liveSource-expression, episteme/publication, FPF-transfer/conformance wording, and reading, read, or quality-read wording when the word could mean source interpretation, publication use, source-to-current transfer, or evaluation hidden inside text work.source-expression unpacking mode, FPF-transfer/conformance mode, claim-bearing episteme, publication/view/face/carrier stack, PublicationUnit, transfer disposition, project-side exact kind/reference, sentence role, and exact evaluation object when live.local rewrite, compact epistemic precision-restoration row, full check, recovered-by-value, quote-only, reduced-use, blocked-transfer disposition, exact neighboring-pattern application, or exact evaluation-pattern exit such as E.22, E.21, or E.9.DA.
Architecture/structure; primary object is selected structure, architecture-description claim, structural view, or exact C.30 subcaseC.30.PArchitecture/structure-heavy wording whose live object is not yet recoverable.A.22 selected structure carrier, C.30 ArchitectureOf@Context, C.30.ASV structural-view and structure-kind discipline, exact C.30 subpattern exits.architecture-structure repair note, repaired wording, selected-structure naming, architecture question, source-return condition, exact receiving-pattern result, ordinary-prose demotion, or stop.
Characteristic/scale; primary object is characteristic, scale, coordinate, score, comparison, indicator role, or characteristic-space constructionC.16.PCharacteristic, scale, coordinate, value, score, indicator, threshold, comparison, metric, axis, dimension, feature, property, level, strong, weak, robust, or benchmark wording whose construction is not yet recoverable.A.17 Characteristic, A.18 CSLC, C.16 measurement, unit, evidence stub, A.19 CharacteristicSpace, C.25 Q-bundle, C.29 mathematical-lens boundary, and E.21 pattern-quality coordinate discipline.characteristic-scale repair note, declared Characteristic, Scale, Coordinate, Value, Score construction, non-comparability, non-measurement, blocked-gate disposition, exact receiving-pattern result, ordinary-prose demotion, or stop.
Quality/evaluative characterization; primary object is quality characterization or Q-bundle/pattern-quality coordinate useC.16.QQuality or evaluative characterization wording when the hidden claim is not relation construction.C.16.P where bearer/scale construction is hidden, C.25 Q-bundle, E.21 pattern-quality coordinates, and exact characterization or relation exits.quality-term repair note, quality-bundle or pattern-quality coordinate use, relation/bridge split when live, blocked scalar/gate/release overread, exact receiving-pattern result, ordinary-prose demotion, or stop.
Exact neighboring claim force already recoverableExact evidence, assurance, gate, work, decision, causal-use, release, mathematical-lens, naming, controlled-coarsening, action-invitation, A.6.M module/interface, or other governing patternAny trigger family whose recovered object is already exact.Receiving pattern's own ontology and conformance fields.Direct receiving-pattern application; no detour through a new restoration pattern.

Direct known-target rule

If the exact receiving pattern and its governed object are already recoverable by value, use that receiving pattern directly. Do not send direct C.30, C.16, C.29, E.21, evidence, assurance, gate, work, decision, causal-use, release, naming, controlled-coarsening, action-invitation, A.6.M module/interface, or mathematical-lens cases through a restoration pattern only because a familiar trigger word appears.

Apply C.30.P, C.16.P, or C.16.Q only when wording hides the live object, relation, characteristic, scale, score, quality characterization, comparability basis, admissible use, or remaining reader move.

Admission and extraction criterion

Add or retain a WordingUseRestorationApplicabilityRow when all of the following are true:

  • the wording recurs across FPF-facing texts or current pattern work;
  • the hidden governed-object-kind/use field set is stable;
  • the recovery apparatus or field set is stable enough to teach;
  • repeated in-place repair distracts from the subject pattern's governed object;
  • a useful remaining reader move survives after overread removal;
  • no existing exact receiving pattern already carries the row without duplicating repair-only doctrine inside subject patterns.

Do not add a new realization pattern when an existing exact pattern such as A.6.F, A.6.A, A.6.M, A.15.4, A.6.6, A.6.3.CSC, A.10, B.3, A.20, A.21, A.15, C.11, C.28, or another exact pattern already carries the live object. Record that pattern as the receivingPattern.

Extract repair-only material from a subject pattern when the material is only trigger lists, false-friend rows, anti-umbrella prose, or repair fields that must run before the subject pattern can start. Leave a narrow first-use cue or exact receiving-pattern exit in the subject pattern.

Keep material in the subject pattern when it states the subject pattern's own invariant, worked case, conformance condition, characteristic construction, structural construction, mathematical lens, source-return condition, or user action.

Receiving-pattern thin-pointer rule

Receiving patterns keep at most one local first-use cue when the live object is hidden, then send the reader to the selected precision-restoration pattern. They do not copy:

  • the full E.10 trigger registry;
  • this shared algorithm;
  • the WordingUseRestorationApplicabilityTable;
  • broad false-friend lists whose only job is first-stage repair;
  • old migration history as live architecture prose.

A thin pointer is acceptable when it helps the working reader choose the right first move, for example:

  • use C.30.P when architecture or structure wording hides whether the live object is selected structure, architecture description, structural view, source, model, diagram, graph, dashboard, or ordinary prose;
  • use C.16.P when metric, score, axis, dimension, feature, property, indicator, strong, weak, robust, level, coordinate, threshold, or comparison wording hides characteristic/scale construction;
  • use C.16.Q when quality or evaluative characterization wording hides Q-bundle, pattern-quality coordinate, relation construction, action-invitation, bridge, or exact characterization use;
  • use C.2.P when source, publication, carrier, face, PublicationUnit, dashboard, documentation, or text-work wording hides source/current transfer or project-side reliance.

Name and placement discipline

semantic area, meaning area, pattern area, pattern cluster, workstream, campaign, module, and branch are not selected as Tech architecture terms for this distribution.

Plain speech may use "meaning area" or "theme" to help a reader notice that relation, episteme/publication, architecture/structure, characteristic/scale, or quality wording is handled by different patterns. Tech prose must resolve that cue into exact ontologicalNeighborhood, governedObjectKindUseFields, exact receivingPattern, and realization pattern.

pattern nest is allowed for ID and placement grouping such as A.6.*, C.16.*, or C.30.*. It is not a semantic parent relation and not an authority relation.

ReceivingLocusObligationClosure may appear only as the exact current E.9.DA coordinate name. It is not a general obligation kind, locus kind, or restoration vocabulary.

Examples and near misses

WordingApplicable resultBlocked overread
"The architecture is the diagram."C.30.P recovers whether the diagram is publication/carrier, structure view, architecture description, or ordinary source cue; then C.30 or C.30.ASV receives only after object recovery.diagram-as-architecture; diagram-as-proof; diagram-as-gate.
"ArchitectureOf@PlantOps is defined over structures S1/S2 under context C."Direct C.30; no C.30.P unless a hidden object remains.unnecessary restoration detour.
"This score proves readiness."C.16.P recovers characteristic, scale, value, score, threshold, comparison basis, and gate/evidence/decision exits.score-as-proof; score-as-release permission.
"This source supports the claim."C.2.P is used if source/current or publication stack is live; relation slice applies A.6.P; final use states recovered relation or non-transfer disposition.source-as-proof; support-as-generic relation.
"Quality improved."C.16.Q recovers quality/evaluative characterization or exits to C.16.P, C.25, E.21, A.6.P, or exact action/work/bridge patterns.quality-as-one scalar; quality-as-gate.
"The function improved maintainability."A.6.F first recovers carrier kind when hidden; quality or maintainability wording then goes to C.16.P, C.16.Q, C.25, or exact quality pattern when live.function-as-default-architecture; maintainability-as-unscaled verdict.
"Read this pattern for improvement proposals."Recover whether the live object is source/publication use, bounded comparative review unit, or improvement-oriented evaluation. Use E.22 only for improvement-oriented quality review under a declared object-under-improvement evaluation.generic reading as a pattern.
"This summary is enough for action."E.10 checks whether the wording is precision restoration or controlled precision reduction. If coarsened source-to-rendering use is live, A.6.3.CSC names source-bearing side, loss mode, narrower admissible use, non-admissible downstream use, and reopen condition.summary-as-full source; coarsening without declared loss.

Conformance checklist

CheckRequirement
CC-E10ARCH-1E.10 remains the compact trigger-and-applicability pattern; E.10.ARCH carries the shared algorithm and applicability-row architecture.
CC-E10ARCH-2Each WordingUseRestorationApplicabilityRow names governed-object-kind/use fields, ontologicalNeighborhood, first applicable restoration or receiving pattern, recovery product, non-use boundary, and remaining reader move.
CC-E10ARCH-3Direct known-target cases use the exact receiving pattern directly instead of opening a restoration detour.
CC-E10ARCH-4A new realization pattern is added only when no existing exact receiving pattern carries the stable recovery apparatus without duplicating repair-only doctrine inside subject patterns.
CC-E10ARCH-5Subject receiving patterns keep their governed object central and carry only thin first-use cues to precision restoration when wording is hidden.
CC-E10ARCH-6reading/read/quality-read wording remains trigger wording and does not mint ReadingPrecisionRestoration.
CC-E10ARCH-7function/functional/functionality/effect wording keeps A.6.F as first unpacker when carrier is hidden and does not default to architecture.
CC-E10ARCH-8ontologicalNeighborhood and pattern nest follow E.8 placement discipline; neither becomes semantic parent, workstream, campaign, module, or authority object.
CC-E10ARCH-9Repair removes overread and preserves one useful admissible reader move. Type-correct but inert wording is not recovered by value.
CC-E10ARCH-10Validation checks cover duplicate trigger tables, stale quality-term-restoration links, broad U.* heads, shadow restoration apparatus, and entry/index drift.

Common anti-patterns

Anti-patternSymptomRepair
Classification without repairThe text says "this belongs under A.6.P" or "this belongs under C.2.P" but leaves no recovered wording, record, source-transfer disposition, direct exact pattern application, or blocker.Apply the selected pattern or fail closed.
Trigger registry copyingE.19, C.30.P, C.16.P, C.16.Q, or a subject pattern copies the full E.10 trigger list.Keep one thin cue in the receiving pattern and point to E.10 / E.10.ARCH.
Umbrella-to-umbrella replacementsupport becomes basis, surface becomes view, reading becomes evaluation, or function becomes role without recovered kind and use.Recover kind, relation, apparatus, admissible use, and remaining reader move; otherwise demote or block.
Sterile precisionThe wording is ontologically well-formed but no working reader can tell why the distinction matters or what move remains.Restore the didactic or recognition function in admissible wording, or classify as reduced-use cue, quote-only, blocked transfer, or incomplete rewrite.
Shadow precision-restoration patternA subject pattern contains its own first-stage repair algorithm beside this distribution.Extract repair-only material to the applicable realization pattern and leave a first-use cue.
Legacy placement as live proseOld placement or alias text explains history instead of current use.Keep only migration or entry rows where needed; write current pattern prose in the selected live placement.
  • E.10 catches and closes local wording issues or selects the applicable row.
  • A.6.P realizes the shared algorithm for relation construction and retained relation specializations.
  • A.6.F realizes function-like carrier recovery.
  • C.2.P realizes source-expression, episteme/publication, and FPF-transfer/conformance recovery.
  • C.30.P realizes architecture/structure wording recovery.
  • C.16.P realizes characteristic/scale wording recovery.
  • C.16.Q realizes quality/evaluative characterization wording recovery.
  • F.18 governs durable reusable naming after the live object is known.
  • E.8 governs pattern-form and placement wording.
  • E.19 checks distribution preservation during review and refresh.
  • J.4 helps readers enter the correct pattern from broad or old terms.

E.10.ARCH:End

Last Updated: 2026-05-31 — this section last modified in upstream FPF commit 16cd3138 (github.com/ailev/FPF)