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 pattern of concern or subject pattern grow its own first-stage wording-recognition table. E.10 recognizes overloaded wording use; E.10.ARCH says which applicability rows exist, how one row selects the first applicable restoration or governing 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 the current governed object, the exact use that made the wording consequential, and the pattern governing that object or use. Recover a claim-bearing episteme, publication object, source-relation disposition, state-family value, or mathematical lens only when that object is current. The output returns to wording after those objects and their direct relations are recoverable. When the kind is recoverable but phrase-level apparatus still hides it, use F.19 for ontology-first plain technical rewriting.

Relation-use recovery rule. When wording hides a positive or governed-negative direct relation claim, first name the obtaining direct relation and the actual governed participants under the participant meanings stated by its direct pattern. Individuate one U.Relation occurrence only when a named receiving use needs to distinguish it. Add a reusable RelationSignature and A.6.5 SlotSpec values only when reusable typed declaration is current. Add participant designations only inside a current assertion or relation-occurrence-description episteme; the designations do not replace the actual participants. A filled project row that states the claim is a claim-bearing episteme. A field, edge, diagram element, or table cell remains a publication form or C.29 representation element unless its direct owner establishes another object and an explicit correspondence. Use an E.24 onticSlotRelation only after durable ontic settlement makes that exact direct relation current. A mathematical tuple or argument position stays representation-side until an explicit correspondence relates it to a declared SlotSpec. E.10.ARCH owns none of those objects; it only routes the authoring repair to their direct owners. Use this pattern when a recurring wording-use problem hides stable ontological recovery work that should be shared instead of copied into each subject pattern.

What goes wrong if missed. Subject patterns accumulate local wording-repair catalogues and stop foregrounding their own governed object, invariant, and first useful move.

What this pattern buys. One distribution architecture keeps recognition in E.10, recovery architecture in E.10.ARCH, and object-specific ontology in the direct governing or realization pattern.

Rationale. Precision restoration needs an ontology-first distribution rule because a recurring trigger word may hide different governed objects, direct relations and participants, declaration-local SlotSpec values, claim-bearing epistemes, publication objects, or mathematical lenses in different places.

SoTA-Echoing. The pattern follows FPF's current ontology-first restoration practice: typed object recovery, direct governing-pattern use when available, and thin pointers in subject patterns instead of repeated repair doctrine.

Builds on. E.10, A.6.P, A.6.P.WMR, A.6.RCD, A.6.F, C.2.P, C.2.P.DR, C.30.STRAT, A.19.SPR, A.6.3.CSC, A.3.1, A.3.2, A.6.0, A.6.1, E.20, A.15.PROD, E.24, E.24.CD, E.24.PUB, F.18, E.8, E.19, and E.2.

Coordinates with. A.22, C.30, C.30.P, C.30.STRAT, C.30.ASV, named C.30.* structure or view patterns, C.16, A.17, A.18, A.19, C.25, C.27.TA, C.27, C.29, A.3.1, A.3.2, A.3.3, A.3.4, A.6.0, A.6.1, A.6.P.WMR, E.18, E.20, A.15.PROD, E.24, E.24.CD, E.24.PUB, A.15.2, A.15.1, A.10, F.19, E.21, E.11, I.2, and evidence, assurance, gate, work, decision, causal-use, release, and publication patterns governing those claims when those claims are being made.

Use this pattern when a recurring FPF-governed wording-use problem cannot be closed by one local E.10 rewrite because the wording hides a stable primary-EntityOfConcern use field set, a stable recovery shape, and a useful remaining reader use.

Relations

E.10.ARCHbuilds onUnified Lexical Rules for FPF

E.10.ARCHbuilds onRelational Precision Restoration — Recovering Direct Relations from Under-Specified Claims

E.10.ARCHbuilds onRelation-Declaration Slot Discipline - SlotKind, ValueKind, RefKind, and participant-designation discipline

E.10.ARCHbuilds onExact Relation Recovery for Method and Work Claims

E.10.ARCHbuilds onNeeded Relation Claim Derivation and Relation-Kind Admission

E.10.ARCHbuilds onFunction and Functional Precision Restoration (RPR-FUNCTION)

E.10.ARCHbuilds onEpistemic Precision Restoration

E.10.ARCHbuilds onDeclarative Representation Precision Restoration

E.10.ARCHbuilds onStratification Wording Precision Restoration

E.10.ARCHbuilds onState-Family Precision Restoration

E.10.ARCHbuilds onControlled Semantic Coarsening

E.10.ARCHbuilds onU.Method: Reusable Way of Doing with Explicit Applicability

E.10.ARCHbuilds onU.MethodDescription: Description Episteme for a Way of Doing

E.10.ARCHbuilds onU.Signature - Reusable Law-Governed Declaration Episteme

E.10.ARCHbuilds onU.Mechanism - Reusable Law-Governed Operation Declaration

E.10.ARCHbuilds onMechanism Introduction Protocol (MIP)

E.10.ARCHbuilds onProduction Work, Entity-Identity Inception, and Production Completion Recovery

E.10.ARCHbuilds onU.Ontic and Ontic Introduction Discipline

E.10.ARCHbuilds onOntic Candidate Detection and First-Use Disposition

E.10.ARCHbuilds onOntic Description and Publication Discipline

E.10.ARCHbuilds onLocal-First Unification Naming Protocol

E.10.ARCHbuilds onOntology-First Plain Technical Rewriting

E.10.ARCHbuilds onFPF Authoring Conventions & Style Guide

E.10.ARCHbuilds onPattern Quality Gates: Review and Refresh Profiles

E.10.ARCHbuilds onThe Eleven Pillars

E.10.ARCHcoordinates withU.Episteme: Constitution, Empirical Grounding, and Edition Relations

E.10.ARCHcoordinates withStructure and Structural Views (STRUCT-CAL)

E.10.ARCHcoordinates withGrounded Architecture and Selected-Structure Adequacy

E.10.ARCHcoordinates withArchitecture and Structure Precision Restoration

E.10.ARCHcoordinates withArchitecture Structural View Adequacy (ASV)

E.10.ARCHcoordinates withMeasurement & Metrics Characterization (MM‑CHR)

E.10.ARCHcoordinates withA.CHR-NORM — Canonical “Characteristic” & rename (Dimension/Axis → Characteristic)

E.10.ARCHcoordinates withA.CSLC-KERNEL — Minimal CSLC in Kernel (Characteristic/Scale/Level/Coordinate)

E.10.ARCHcoordinates withCharacteristicSpace & Dynamics Hook (A.CHR‑SPACE)

E.10.ARCHcoordinates withQ-Bundle: Authoring "-ilities" as Structured Quality Bundles

E.10.ARCHcoordinates withTemporal Aspect: Time Windows, Rhythm, Cadence, and Currentness

E.10.ARCHcoordinates withTemporal Claim Adequacy: State Readings, Temporal Trends, and Intervention-Sensitive Temporal Change

E.10.ARCHcoordinates withMathematical Lens Use

E.10.ARCHcoordinates withU.Dynamics: State-Space and Transition-Law Episteme

E.10.ARCHcoordinates withU.Transformation: Bounded Change Under Conditions

E.10.ARCHcoordinates withU.Work: Dated Performed Work Occurrence

E.10.ARCHcoordinates withU.WorkPlan: The Schedule of Intent

E.10.ARCHcoordinates withEvidence Graph Referring (C-4)

E.10.ARCHcoordinates withFPF Pattern-Quality Evaluation CharacteristicSpace

E.10.ARCHcoordinates withFirst-Practical Entry and Pattern-Use Discoverability Discipline

E.10.ARCHcoordinates withExpanded Entry Disambiguation Cases

E.10.ARCHoutline parentUnified Lexical Rules for FPF

E.10.ARCHoutline prev siblingMove and Readiness Wording Precision Restoration

E.10.ARCHoutline next siblingConceptual Prefixes (policy & registry)

E.10.ARCHexplicit referenceUnified Lexical Rules for FPF

E.10.ARCHexplicit referenceRelation-Declaration Slot Discipline - SlotKind, ValueKind, RefKind, and participant-designation discipline

E.10.ARCHexplicit referenceRelational Precision Restoration — Recovering Direct Relations from Under-Specified Claims

E.10.ARCHexplicit referenceExact Relation Recovery for Method and Work Claims

E.10.ARCHexplicit referenceNeeded Relation Claim Derivation and Relation-Kind Admission

E.10.ARCHexplicit referenceFunction and Functional Precision Restoration (RPR-FUNCTION)

E.10.ARCHexplicit referenceEpistemic Precision Restoration

E.10.ARCHexplicit referenceDeclarative Representation Precision Restoration

E.10.ARCHexplicit referenceStratification Wording Precision Restoration

E.10.ARCHexplicit referenceState-Family Precision Restoration

E.10.ARCHexplicit referenceControlled Semantic Coarsening

E.10.ARCHexplicit referenceU.Method: Reusable Way of Doing with Explicit Applicability

E.10.ARCHexplicit referenceU.MethodDescription: Description Episteme for a Way of Doing

E.10.ARCHexplicit referenceU.Signature - Reusable Law-Governed Declaration Episteme

E.10.ARCHexplicit referenceU.Mechanism - Reusable Law-Governed Operation Declaration

E.10.ARCHexplicit referenceMechanism Introduction Protocol (MIP)

E.10.ARCHexplicit referenceProduction Work, Entity-Identity Inception, and Production Completion Recovery

E.10.ARCHexplicit referenceU.Ontic and Ontic Introduction Discipline

E.10.ARCHexplicit referenceOntic Candidate Detection and First-Use Disposition

E.10.ARCHexplicit referenceOntic Description and Publication Discipline

E.10.ARCHexplicit referenceLocal-First Unification Naming Protocol

E.10.ARCHexplicit referenceFPF Authoring Conventions & 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 referenceGrounded Architecture and Selected-Structure Adequacy

E.10.ARCHexplicit referenceArchitecture and Structure Precision Restoration

E.10.ARCHexplicit referenceArchitecture Structural View Adequacy (ASV)

E.10.ARCHexplicit referenceMeasurement & Metrics Characterization (MM‑CHR)

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 Aspect: Time Windows, Rhythm, Cadence, and Currentness

E.10.ARCHexplicit referenceTemporal Claim Adequacy: State Readings, Temporal Trends, and Intervention-Sensitive Temporal Change

E.10.ARCHexplicit referenceMathematical Lens Use

E.10.ARCHexplicit referenceU.Dynamics: State-Space and Transition-Law Episteme

E.10.ARCHexplicit referenceU.Transformation: Bounded Change Under Conditions

E.10.ARCHexplicit referenceTransformation Flow Structure

E.10.ARCHexplicit referenceU.WorkPlan: The Schedule of Intent

E.10.ARCHexplicit referenceU.Work: Dated Performed Work Occurrence

E.10.ARCHexplicit referenceEvidence Graph Referring (C-4)

E.10.ARCHexplicit referenceOntology-First Plain Technical Rewriting

E.10.ARCHexplicit referenceFPF Pattern-Quality Evaluation CharacteristicSpace

E.10.ARCHexplicit referenceFirst-Practical Entry and Pattern-Use Discoverability Discipline

E.10.ARCHexplicit referenceExpanded Entry Disambiguation Cases

E.10.ARCHexplicit referenceSignature Stack & Boundary Discipline

E.10.ARCHexplicit referenceRelation, Signature, Interface, Role, and Slot Precision Restoration

E.10.ARCHexplicit referenceCharacteristic and Scale Precision Restoration

E.10.ARCHexplicit referenceQuality-Term Precision Restoration

E.10.ARCHexplicit referenceU.Episteme: Constitution, Empirical Grounding, and Edition Relations

E.10.ARCHexplicit referenceU.EpistemicViewing — EntityOfConcern-preserving morphism

E.10.ARCHexplicit referenceU.EpistemicRetargeting — EntityOfConcern retargeting morphism

E.10.ARCHexplicit referenceRole-Method-Work Alignment (Contextual Enactment)

E.10.ARCHexplicit referenceMulti‑Method Dispatcher & MethodFamily Registry

E.10.ARCHexplicit referenceTransformation Ontic Precision Restoration

E.10.ARCHexplicit referenceRole Taxonomy

E.10.ARCHexplicit referenceU.RoleAssignment - System Role Assignment

E.10.ARCHexplicit referenceModule Relation Repair

E.10.ARCHexplicit referenceAction-Invitation Precision Restoration (ACT-INV)

E.10.ARCHexplicit referenceDecision Theory (Decsn-CAL)

E.10.ARCHexplicit referenceRelation Obtaining and Individuated Relation Occurrences

E.10.ARCHexplicit referenceImprovement-Oriented Quality Evaluation Question Framing

E.10.ARCHexplicit referenceDRR Decision-Adequacy Evaluation CharacteristicSpace

E.10.ARCHexplicit referenceMulti‑View Publication Kit

E.10.ARCHexplicit referenceArchitecture Description Adequacy

E.10.ARCHexplicit referenceControl Structure View Adequacy (LCA)

E.10.ARCHexplicit referenceArchitecture Candidate Synthesis

E.10.ARCHexplicit referenceWork-Relevant Appearance-Based Reliance Repair

E.10.ARCHexplicit referenceBase Declaration Discipline - Kind-explicit, scoped, witnessed base declaration discipline (with base-change lexicon)

E.10.ARCHexplicit referenceTrust & Assurance Calculus (F–G–R with Congruence)

E.10.ARCHexplicit referenceFlow Constraint Validity — Eulerian

E.10.ARCHexplicit referenceGateProfilization: OperationalGate(profile) (GateFit core)

E.10.ARCHexplicit referenceCausalUse-CAL: Causal-Use Questions, Causality-Ladder Rungs, Identification and Realizability

E.10.ARCHexplicit referencePublicationUnit Stability Discipline and PublicationUnit Primary EntityOfConcern Discipline

Content

Use This When

Early failure cue. FPF accumulates many small local wording-recognition lists, and subject patterns start teaching repair doctrine instead of their own EntityOfConcern, invariants, and first useful move.

Early gain cue. E.10.ARCH gives one architecture for distributing wording-use repair: E.10 recognizes the row, this pattern selects the recovery architecture, and the governing subject pattern stays centered on its own object.

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, layer, level, tier, stack, block, expert, cache, router, or gate triage before the architecture, structure, control, module-interface, flow, scale, publication, or gate pattern can state its own invariant;
axis, dimension, feature, property, metric, indicator, score, strong, weak, robust, level, coordinate, threshold, or scalar-quality triage before a characteristic or scale pattern can state its own invariant;
quality-term repair that decides between relation construction, quality characterization, evaluative characterization, Q-bundle use, pattern-quality coordinate use, action invitation, bridge, or governing pattern;
state-family wording such as state, status, posture, readiness, stance, or currentness before the bearer, state frame, value set, admissible use, or governing pattern is recovered;
admissibility-like, legal, lawful, authority, validity, readiness, pass-looking, fail-looking, or conformance wording before bearer, claim kind, source relation, value frame, bounded use, and direct governing pattern are recovered;
method, algorithm, program, proof, solver, workflow, process, procedure, access path, query plan, control strategy, or programming-paradigm wording before one exact method, one-method description episteme, method-side relation, mechanism, plan, dated Work, transformation, result, structure, architecture, representation, and their exact direct relations are recovered;
input, raw-material, source-data, source-material, output, result, outcome, deliverable, handoff, or work-name wording before the exact entity, related object, four orthogonal claim dimensions (claim subject; modality and exact temporal extent; polarity; recovery/support state), governor or reason-specific non-assertability basis, and any performed-work occurrence basis are recovered;
relation, signature, interface, role, assignment, enactment, slot, field, parameter, argument, endpoint, port, API, protocol, connector, capability, affordance, method, function, concern, or interest wording before the current governed object or claim kind is recovered and before the direct governing pattern can carry the recovered claim;
graph, path, query, table, dashboard, checklist predicate, publication face, evidence-path wording, or pattern-relation wording overread as a route, call, dispatch, invocation, work sequence, permission, release, evidence result, or pattern application;
source, publication, publication form, 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 governing pattern is already known or must be recovered before the sentence is admitted.

Failure shape. FPF accumulates many small local wording-recognition lists. One pattern says "architecture is not a diagram", another says "metric is not proof", another says "quality is not one scalar", another says "a path is not a route", and a reader cannot tell which pattern carries the repair. The text looks more precise, but the reader does not get a stable first move.

Architecture gain. E.10.ARCH gives one architecture for distributing wording-use repair: E.10 recognizes the wording-use row; E.10.ARCH selects the row and extraction criterion; a realization pattern or governing neighboring pattern recovers the ontology; the governing subject pattern carries its own primary EntityOfConcern and first useful move.

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

Not this pattern when.

If a sentence is repaired locally under E.10, stop there.
If the governing pattern and current governed object, exact direct relation use, or claim-bearing episteme are already recoverable by value, use that governing pattern directly.
If the kind under repair is evidence, assurance, gate, work, decision, causal-use, release, mathematical-lens use, grounded architecture adequacy, structural-view adequacy, characteristic-space construction, Q-bundle construction, pattern-quality evaluation, one exact method, a one-method description episteme, mechanism, formal substrate, graph path, evidence or provenance relation, publication face, or another FPF kind named by value, the governing pattern governs its own invariant. E.10.ARCH only governs the wording-use restoration distribution.
If the wording problem is phrase-level apparatus around an already recoverable kind, use F.19 rather than creating a new wording-use restoration row.

Problem Frame

Precision restoration in FPF is ontology-first, not word-substitution-first. A recurring wording family is important only when it hides a stable governed object, direct relation kind, actual participant or relation-participant meaning, declaration-local SlotSpec, assertion-side participant designation, claim kind, publication-use relation, source-relation disposition, mathematical lens, or neighboring-pattern boundary.

Problem

Without a shared distribution architecture, subject patterns collect first-stage repair catalogues and lose their object focus. The same false friend is then repaired differently in architecture, characteristic, evidence, publication, method, relation, and state-family patterns.

Forces

Force	Tension
Shared repair vs subject-pattern focus	FPF needs recurring trigger recognition, but each subject pattern must stay centered on its own EntityOfConcern.
Ontology-first repair vs lexical cleanup	The repair must recover the exact governed object, direct relation and actual participants, or claim-bearing episteme before choosing wording.
Direct governing pattern vs restoration detour	A direct pattern should govern when the object is already recoverable by value.
Local cue vs duplicated doctrine	Subject patterns may need one first-use cue, not a copied repair table.
Semantic area vs placement nest	A semantic area, ontological neighborhood, and pattern nest are different objects.

Solution

Use E.10 for recognition, E.10.ARCH for the shared distribution architecture, and the direct governing pattern for the recovered object or relation. Add a new applicability row only when recurring wording hides a stable object-recovery shape and a useful surviving reader use that no direct governing pattern already carries.

Primary EntityOfConcern and applicability-row scope

The primary EntityOfConcern for this pattern use is the pattern-local authoring and publication architecture of WordingUseRestorationApplicabilityRow rows. The row is not the project object exposed by the wording and is not a practitioner artifact.

A row may use semanticAreaBaseConcept, semanticArea, semanticAreaSenseFamily, and ontologicalNeighborhood as author-facing routing coordinates. Its minimum semantic content is:

the recurring wording use recognized by E.10;
the exact governed entity, value, episteme, obtaining direct relation, or representation exposed by that use;
the exact claim or use being made;
the direct pattern governing that object, relation, or representation;
the repaired wording;
the admissible reader use that survives; and
the blocked stronger reading.

Declaration, designation, reference, publication, or representation fields are optional and appear only when the current repair needs them. A reusable relation declaration names its RelationSignature and A.6.5 SlotSpec values. A current assertion or relation-occurrence-description episteme may carry participant designations. A publication form or C.29 representation element names its represented object and explicit correspondence. An E.24 onticSlotRelation appears only when durable ontic settlement is itself current. None of these optional objects becomes a field of the governed entity merely because the authoring row cites it.

WordingUseRestorationApplicabilityRow is not a U.* kind, conformance object, process task, deontic obligation, or durable project artifact. Ordinary engineers do not fill it. They receive the shortest practitioner-facing sentence that identifies the governed object, direct relation or claim, and remaining action-facing use.

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

semanticAreaBaseConcept is the Base concept, source wording span, or already settled row cue by which an author first recognizes the candidate semantic unit.

semanticArea is the Part-F semantic unit used by one wording-use restoration row: one Concept-Set row, one UTS row, or an explicitly bounded row-set whose rows remain sense-uniform enough for one recovery architecture.

semanticAreaSenseFamily is the Part-F senseFamily or FPF kind named by value-family discriminator that prevents the row from becoming a theme, domain, workstream, or pattern-nest label.

ontologicalNeighborhood means the FPF applicability neighborhood around that named semanticArea: the exact governed objects, admissible adjacent objects and relations, direct owners, use boundaries, and optional declaration, description, publication, reference, or representation objects needed by the current repair. It is not textual, filename, ToC, alphabetic, topic, discipline, domain, workstream, or pattern-nest proximity.

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:

E.10 recognizes an FPF-governed wording use and either closes it locally or selects a governing pattern, controlled precision-reduction pattern, durable-name application, or fail-closed non-use disposition.
E.10.ARCH maintains the shared recovery algorithm and the WordingUseRestorationApplicabilityTable.
A realization pattern or retained governing pattern such as A.6.RSIR, A.6.P, A.6.P.WMR, A.6.RCD, A.6.F, C.2.P, C.2.P.DR, C.30.P, C.30.STRAT, C.16.P, C.16.Q, A.19.SPR, A.3.1, or a direct evidence, graph, method, mechanism, work, gate, authority, release, or publication-use governing pattern unpacks the wording according to the shared algorithm for one named semanticArea and its ontologicalNeighborhood. A.6.P.WMR is selected after generic relation recovery when one method/work-boundary claim remains hidden; A.6.RCD is selected only after exact participants are recovered and no current direct relation or already governed local relation-bearing claim closes the named receiving claim.
Additional applicability rows, and only when needed additional realization patterns, appear when repeated FPF-governed wording hides a stable primary-EntityOfConcern use field set, a stable recovery shape, and a useful remaining reader use that no existing governing pattern already carries.
E.8 governs publication-form and placement wording such as pattern nest, and requires authoring prose that uses ontologicalNeighborhood to expose the governing semanticAreaBaseConcept, semanticArea, and semanticAreaSenseFamily rather than treating neighborhood as the semantic unit.
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 patterns centered on their own primary EntityOfConcern values, decisions, characteristics, structures, mathematical lenses, consequences, and worked uses.

EntityOfConcern and recurring hidden-field distribution

For wording such as EntityOfInterest, EoI, EoIClass, describedEntity, DescribedEntityRef, and primary described entity, or for selected EntityOfConcern-family heads such as EntityOfConcern, entityOfConcernRef, EntityOfConcernRef, EntityOfConcernClass, and publicationUnitPrimaryEntityOfConcern, the repair is distributed by the current FPF-governed use:

EntityOfInterest, EoI, EoIClass, describedEntity, DescribedEntityRef, and primary described entity are active repair triggers. FPF-governed wording must recover the EntityOfConcern-family use named by value, publication-unit primary-EoC use, or local FPF kind, then rewrite to EntityOfConcern, entityOfConcernRef, EntityOfConcernRef, EntityOfConcernClass, publicationUnitPrimaryEntityOfConcern, or the local FPF kind named by value. If no use is recoverable by value, the wording remains quoted source or trigger wording and cannot be used for reliance.

C.2.1 governs episteme identity and the identified EntityOfConcern participant of EpistemeConstitutionRelation; A.6.5 governs EntityOfConcernSlot only inside a reusable constitution RelationSignature; direct reference patterns govern entityOfConcernRef, EntityOfConcernRef, and related reference use.
C.2.P carries episteme, publication, source-wording, and source-relation precision restoration when the sentence still hides source wording, claim-bearing episteme, publication construction, publication-form construction, project-side reliance, pattern-application wording, or use or non-use disposition.
F.18 carries durable naming, selected head settlement, and source-string and durable-name discipline after the kind under repair and use are recovered.
E.17.AUD.OOTD carries publicationUnitPrimaryEntityOfConcern for one bounded publication unit with one carried move and one outside-work boundary; that publication-use designation adds no participant to EpistemeConstitutionRelation.
A.6.3, its retained entityOfConcernRef-preserving specializations, and A.6.4 carry preservation or retargeting of the EntityOfConcern across episteme morphisms.
Evidence, assurance, gate, work, decision, architecture, characteristic, mathematical-lens, or project-side patterns govern their own claim being made or admissible-use boundary directly when it is already recoverable.

This selected-family case is the standing example for recurring hidden-field architecture. When a new hidden-field family recurs, it is not solved by adding local warning prose to every subject pattern. It either uses an existing governing pattern, gets one applicability row in this table, or justifies a new realization pattern only when the hidden field set, recovery apparatus, and remaining reader use recur across FPF-governed texts.

Use this distribution before adding or specializing a wording-use precision-restoration pattern.

E.10 is the shared recognition scan. It recognizes an FPF-governed wording-use problem and selects the first applicable restoration or governing pattern. E.10.ARCH owns the distribution rule. A specialized restoration pattern owns only the stable ontological recovery for one selected ontic, semantic area, or high-pressure facet.

Use a direct governing pattern when the current governed object, exact direct relation use, claim-bearing episteme, representation use, or claim kind is already recoverable by value. A direct A.3.4, A.6.F, C.29, E.18, C.30, A.15, A.10, gate, decision, publication, or evidence use does not need a restoration detour only because a familiar trigger word appears.

A.6.RSIR is the selected first-level realization pattern for the relation-signature-interface-role-slot cluster. Use it only when wording such as relation, signature, interface, role, assignment, enactment, slot, field, parameter, argument, endpoint, port, API, protocol, connector, capability, affordance, method, function, concern, or interest hides which governed object or claim kind is current. The first-level product is not a new ontology; it is a compact recovery of project concern, current EntityOfConcern or claim kind, selected direct governing pattern, slot-discipline need, retained source-label use, and blocked overread. After that selection, the direct pattern owns the repair.

Use an ontic-level restoration pattern only when recurring wording hides a candidate durable ontology unit whose primary governed subject kind, stable identity, core direct relation, named neighboring direct relations, and governing patterns need joint recovery before wording repair. The restoration recovers the exact current governed objects and direct relation uses; it does not treat declaration-local SlotKinds or assertion-side participant designations as parts of the ontic.

Use E.24.CD only when recurring wording exposes a candidate subject that may need an E.24 ontic-introduction decision: a potential primary governed subject kind, stable identity, core direct relation, named neighboring direct relations, and action-facing gain that no direct governing pattern already carries. Use E.24.PUB only when the repair must distinguish ontic, ontic-description episteme, publication form, view, record, card, table, schema, data-structure expression, rendering, or source relation. If the subject ontology is already governed by a pattern such as A.22, A.19, C.30, A.3.4, or C.2.1, use that pattern directly and cite E.24.CD or E.24.PUB only as the relevant thin boundary reference.

Use a facet-level restoration pattern only when one recurring facet cuts across several ontics or subject patterns and has its own stable ambiguity. Function-like wording under A.6.F is the standing example: function wording may point to transformation behavior, performed-work action or another actor-side claim under an exact direct governor, a separately typed architecture or other influence source under its exact relation, mathematical function, module allocation, capability, quality, role, work, method, evidence, assurance, gate, or decision. That facet is too broad to duplicate inside every ontic-level restoration pattern and too specific to leave as ordinary prose.

Do not create one precision-restoration pattern per relation-participant meaning or declaration-local SlotKind. A separate restoration pattern is justified only when the same ambiguity recurs across several patterns, changes the governing FPF kind or direct relation use, and would otherwise force subject patterns to carry repeated first-stage repair prose. Otherwise, apply the direct relation pattern and, when reusable declaration is current, A.6.5.

When both an ontic-level restoration pattern and a facet restoration pattern are applicable, apply them by recovered question, not by word order. The ontic-level pattern asks which candidate subject, governed objects, core and neighboring direct relations, and governing patterns are current. The facet pattern asks how the overloaded facet word is assigned after that recovery. For example, transformation wording that includes function, functional, or functioning may use a transformation-ontic restoration pattern to recover U.Transformation, TransformationFlowStructure, its exact participants and direct relations, or FunctioningRef?; detailed function-kind discrimination remains with A.6.F.

A conforming specialized restoration pattern states:

the ontic, semantic area, or facet-neighborhood under repair;
the recognition wording family selected by E.10;
the recovered governed object, any exact direct relation use, any current claim-bearing episteme or representation, and the pattern governing each;
any direct governing pattern that should apply instead when the value is already recoverable;
any facet restoration pattern that owns a narrower recurring ambiguity;
the temporary recovery product and the retained user-facing move after wording repair.

Shared recovery algorithm

Use this five-step object-preserving order for every E.10.ARCH authoring case:

Bound the wording and use. Name the exact text span or publication unit, the recurring wording, its sentence function and register, and the working claim or use that makes it consequential. Keep semanticAreaBaseConcept, semanticArea, and semanticAreaSenseFamily as author-facing routing coordinates rather than as candidate project ontology.
Recover the exact subject and claim. Identify the exact governed entity, value, or episteme; the obtaining direct relation and its actual participants when that is the claim; or the exact claim-bearing episteme when the encountered row, report, or card states the claim. When representation is current, identify both the represented object and the representation use without treating the representation as obtaining. When metonymy or compression is plausible, keep both the literal candidate and the intended candidate explicit until their direct owners and exact relations or claims either distinguish the two uses or rule one out; shared wording does not license premature single-referent closure.
Bypass restoration when the owner is clear. Apply the direct governing pattern immediately once it can carry the recovered object, relation, assertion, description, publication, representation, work, result, structure, or architecture claim. Use E.10.ARCH or a realization pattern only while wording still hides that selection.
Add only receiver-needed apparatus. Add a reusable RelationSignature and A.6.5 SlotSpec values, relation-occurrence identity, participant designations, designators, references, publication forms, or C.29 representation elements only when a named later use needs that additional object. Keep each apparatus item under its direct owner. Use an E.24 onticSlotRelation only after durable ontic settlement makes that exact relation current. If the same entity participates in several direct relations, is designated in several assertion or occurrence-description epistemes, or corresponds to several representation elements, keep those uses distinct under their separate governors; shared entity identity does not merge the relations, epistemes, designations, or representation correspondences.
Write the shortest usable sentence. State the governed object, direct relation or claim, admissible action-facing use, and blocked stronger reading so the working reader need not consult the applicability row. A type-correct but inert sentence is not a completed repair.

Perform a terminology-source audit only when source ontology can change the governed object, direct relation kind, participant meaning, actual participant kind, declaration-local SlotSpec, assertion-side participant designation, exact use, admissible use, or governing-pattern selection. Stable ordinary prose remains ordinary. A source tuple or argument place remains representation-side until an explicit correspondence to a declared SlotSpec is current.

Method, work, and P2W governing-pattern constellation in wording restoration

Use this branch when one source label, project handle, or project concern points to changing, producing, selecting, deriving, controlling, or maintaining an EntityOfConcern rather than to one typed FPF value.

Do not name a new recovery object. Recover each current value and claim separately: one exact context-local U.Method; a U.MethodDescription episteme that describes that one exact method; MethodRelationStructure@BoundedContext; a mechanism declaration or realization; a formal-substrate declaration; a mathematical-lens or other representation use; a U.WorkPlan; one dated Work occurrence admitted under U.Work; one actual transformation; a local production-work, entity-identity-inception, or production-completion claim; a direct changed-referent relation; a measurement-result or evaluation-result episteme; a C.11 ChoiceResult or decision episteme; an evidence, source, gate, publication, or temporal relation; a delivery or acceptance relation or claim; a selected structure; an ArchitectureOf@Context relation; an architecture-description episteme; or another exact governed object named by its direct owner. The A.15 role-method-plan-Work alignment remains a set of separately governed direct relations; it does not merge those values into one object.

When the concern is a relation among methods or method families, recover MethodRelationStructure@BoundedContext: serial or parallel composition, guarded choice, iteration, refinement, substitution, decomposition, parameterization, method-family membership, selector relation, fallback relation, or another exact method-side relation. Govern it through A.3.1, G.5, or its exact direct owner. A graph, algebra, tuple, categorical notation, process calculus, effect calculus, matrix, embedding, distributed notation, or neural notation used to present it is a C.29 representation or mathematical-lens use, not itself a method. Do not name that representation U.MethodAlgebra. A description of the relation is a separately governed claim-bearing episteme; U.MethodDescription does not widen to a method family, relation structure, mechanism, plan, Work occurrence, transformation, result, architecture, or representation. Do not type one value as both U.Method and U.Mechanism unless their direct owners independently admit both claims.

The authoring note may record the affected entity, bounded context, change or maintained-condition claim, any current state or delta predicate, the exact objects and relations exposed by the wording, and their direct owners. It is not a project object. If the project needs a method, description episteme, mechanism, plan, Work occurrence, transformation claim, result episteme, evidence or source relation, gate decision, choice result, structure, architecture description, representation, publication relation, or temporal relation, apply that direct pattern and keep each independently governed identity.

Treat input, raw material, epistemic source data or source material, output, result, outcome, deliverable, handoff, and work-name wording as triggers only while their exact relation is hidden. Once clear, bypass E.10.ARCH: use A.3.2 only for a description episteme about one exact method; A.15.2 for an intended participant or use in planned work; A.15.1 and the exact resource or participation owner for a dated Work occurrence; A.3.4.P and the direct transformation owner for an actual transformation participant; A.15.PROD, the measurement or evaluation owner, or the delivery or acceptance owner for the exact result claim; and C.29 when the word names only an argument, tuple component, graph element, or other representation place. Use C.2.P first for an epistemic source expression and source-to-use relation. Keep physical material under its direct physical governor.

If the exact method/work-boundary relation is still hidden after generic relation recovery, apply A.6.P.WMR. Its result remains exactly one family: a positive or governed-negative direct subject-relation claim; an exact A.6.1 operation-application binding; an exact local A.15.PROD or A.6.RCD claim; or reason-specific non-assertability as factually unsupported, missing-information, or missing-governor. A failed known predicate such as EpistemeUsedByReviewWorkAsReference is factually unsupported; an unavailable ETL receiving-use fact under a known governor is missing-information; and an absent relation kind and owner for the named Patient_8472 / HE-8472 health-effect receiving use is missing-governor. Only the last names an affected receiving use and future owner. Classification, a generic result label, a type-correct designation, planned use, or inferred opposite polarity does not close the branch.

Durable naming follows the governed value. F.18 may name a performed Work occurrence only after its A.15.1 occurrence basis is established, and it names neighboring production, measurement, evaluation, delivery, and acceptance results separately. If a proposed U.* name merely repeats a declaration-local SlotSpec label or direct-pattern participant meaning, keep it local unless E.24 supplies durable identity, action-facing gain, and the exact governing relation. If repeated method, Work, or process material is proposed as durable ontology, its E.24 ontic decision and, for any public U.* kind, E.24.UK admission plus the governing head pattern must precede current citation.

Applicability table

Semantic area and ontological neighborhood	First applicable pattern	Trigger family	Required recovery apparatus	Typical recovery product
Relation construction; primary recoverable use is an obtaining direct relation or a relation-bearing claim	`A.6.P` only while recovery is needed, then the exact direct relation pattern; `A.6.RCD` only after exact participants are recovered and no current direct relation closes the named receiving claim	Relation, endpoint, qualifier, slot, scope, time, viewpoint, evidence-use distinction, basedness, service, bridge wording, whole or part, mapping, comparison, dependency, or evaluative ascription when the hidden claim is relation construction.	Exact direct relation kind; participant meanings and actual governed participants; obtaining predicate; occurrence identity only for a named receiving use. A reusable `RelationSignature` and A.6.5 `SlotSpec` values appear only when typed declaration is current. A claim-bearing assertion or occurrence-description episteme and its participant designations appear only when that claim is current.	Short direct-relation sentence; exact claim-bearing episteme; reusable predicate-definition episteme; separately settled relation kind; direct-pattern application; `A.6.RCD` result; or fail-closed Plain disposition.
Relation-signature-interface-role-slot semantic area; primary recoverable use is hidden among direct relation wording, reusable declaration, interface claim, role value, role assignment, role description, port, boundary claim bundle, neighboring candidate value, or reduced-use source label	`A.6.RSIR` when the direct governing pattern is not already clear; direct governing pattern when recovered by value	Relation, signature, interface, role, assignment, enactment, slot, field, parameter, argument, endpoint, port, API, protocol, connector, capability, affordance, method, function, concern, interest, role-holder grammar, or close source wording.	Project concern; exact governed object or claim; direct governing-pattern selection; A.6.5 `SlotSpec` only for reusable declaration; retained source-label use; blocked overread; and stop condition. Direct owners include `A.6.P`, `A.6.5`, `A.6.0`, `A.2`, `A.2.1`, `A.15`, `A.6.M`, `A.6.F`, `A.6.A`, and the exact method, work, publication, evidence, status, gate, problem, or characteristic-space pattern.	`RSIRRepairNote`, direct governing-pattern application, reduced-use source label, quote-only cue, blocked-use disposition, or stop.
Function-like wording; primary recoverable use is an exact governed object or claim hidden by `function`, `functional`, `functionality`, `effect`, or similar wording	`A.6.F` first when the exact object, claim, or direct owner is not already recovered; direct governing pattern when it is recovered by value	Functional architecture, required transformation or effect, method, work occurrence, direct subject effect, measurement-result episteme, evaluation result, `C.11` `ChoiceResult` or decision record, role expectation, mathematical function, relation, loss, objective, quality or functionality claim, module allocation, interface or signature relation, or evidence, assurance, gate, or decision overread.	`FunctionUseRepair`; exact governed object or claim and direct owner; admitted direct predicate and actual participants when a relation is involved; one exact `C.2.1` relational-assertion episteme only when the text makes an affirmative, negative, or modal claim about that predicate; one occurrence distinction under the direct owner's identity rule, applied through `A.6.REL`, only when the task must distinguish one obtaining episode from another; `C.30` or `C.30.ASV` functional-structure boundary; `C.29` mathematical-lens boundary; `C.16` or `C.25` quality boundary; `A.6.M` module-interface relations; and an `A.6.0` `RelationSignature` with `A.6.5` `SlotSpec`s only when reusable declaration is needed.	Short statement naming the exact object or claim and its direct owner; direct predicate with actual participants when a relation is involved; `C.2.1` assertion only when the claim about that predicate must be preserved; occurrence distinction under the direct owner's identity rule, applied through `A.6.REL`, only when one obtaining episode must be distinguished; governing-pattern application; `FunctionFlowModuleAlignmentNote`; mathematical-lens, quality, characteristic, or `A.6.M` application; ordinary-prose demotion; or stop.
Episteme, publication, source wording, and source-relation wording; encountered entity or construction may be source span, publication form, face, publication, `PublicationUnit`, EntityOfConcern-like head, old EntityOfConcern-family wording, or text-work evaluation cue	`C.2.P` first; evaluation pattern governing the recovered evaluation claim after recovery when the corresponding claim is being made	Source-expression, episteme or publication wording, FPF-governed wording, `EntityOfConcern` or `describedEntity`-family wording, and `reading`, `read`, or `quality-read` wording when the word could mean source interpretation, publication use, FPF-governed use, or evaluation hidden inside text work.	The required recovery apparatus is a set of possible fields, not one kind: source-expression clarification, FPF-governed use disposition, claim-bearing episteme, EntityOfConcern, publication relation, view, face, publication-form relation, `PublicationUnit`, `publicationUnitPrimaryEntityOfConcern`, project-side kind named by value or reference, sentence function, and evaluation claim or bundle named by value when current.	local rewrite, compact epistemic precision-restoration row, full check, recovered-by-value, reduced-use, blocked-use disposition, neighboring-pattern application, or evaluation-pattern application such as `E.22`, `E.21`, or `E.9.DA`.
Ontic candidate and publication-form confusion; primary recoverable use is a candidate durable subject, an exact E.24 `onticSlotRelation` after settlement, an ontic-description episteme, or a publication or representation form hidden behind record, card, schema, table, data structure, view, or source-material wording	`E.24.CD` for candidate detection; `E.24.PUB` for ontic-description and publication-form boundary; direct subject pattern when the ontic or governing pattern is already recovered	ontic, concept cluster, semantic area, ontological neighborhood, source slot or field wording, schema, record, card, table, data structure, publication form, description, view, or source-material wording.	Candidate subject, possible primary governed kind, stable identity, possible core direct relation, named neighboring relations, governing patterns, publication and C.29 representation boundary, admissible use, blocked overread, and remaining reader use. An `onticSlotRelation` and its actual participants appear only after E.24 durable settlement makes that exact direct relation current.	Ontic-candidate note, direct E.24 or subject-pattern application, E.24.PUB boundary note, C.29 representation use, ordinary-prose demotion, quote-only cue, reduced-use cue, blocked-use disposition, or stop.
Admissibility-like, legality-like, authority, validity, readiness, pass-looking, fail-looking, and conformance wording; primary recoverable use is bearer, claim kind, source relation, value frame, bounded use, and governing pattern, not a generic admissibility object	Direct governing pattern when the claim is recoverable by value; `A.19.SPR` only when a hidden state-family bearer and value frame are the problem; `A.6.P` only when relation construction is hidden	`admissible`, `lawful`, `legal`, `legality`, `allowed`, `permitted`, `authorized`, `valid`, `pass`, `fail`, `ready`, `conformant`, `eligible`, and close compounds.	bearer, claim kind, source relation, value frame, admissible use, non-admissible overread, validity window or reopen condition when current, and direct governing pattern for mechanism admissibility predicate, signature applicability, evidence, assurance, gate, work, decision, authority-bearing record, release, temporal validity, or source-relation disposition.	direct governing-pattern application; state-family repair note only when hidden state wording is current; recovered gate, evidence, authority, temporal, mechanism, or source-relation boundary; quote-only cue; reduced-use cue; blocked-use disposition; or stop.
Method, algorithm, program, solver, proof, recipe, workflow, process, procedure, access path, query plan, control strategy, method algebra, method graph, selector calculus, or programming-paradigm wording; primary recoverable use is one exact method or a separately governed method-side relation, description, mechanism, work, transformation, result, structure, architecture, representation, or direct relation	`A.3.1` only while the method-side object is hidden; then the exact direct owner; `C.2.P.DR` when representation overread is the current problem	algorithm, program, solver, proof, recipe, method, workflow, process, procedure, access path, query plan, control strategy, imperative, functional, logical, constraint, object-centric event, effect-handler, pipeline, orchestration, method algebra, method graph, selector calculus, fallback composition, or similar wording.	One exact `U.Method`; `MethodRelationStructure@BoundedContext` for exact method-side relations; one `U.MethodDescription` episteme describing one exact method; formal-substrate declaration; C.29 representation; mechanism; WorkPlan; dated Work; actual transformation; production/inception/completion claim; measurement or evaluation result; delivery or acceptance claim; selected structure; architecture relation; architecture-description episteme; or exact evidence, source, gate, choice, decision, and other direct relation. Each remains under its own owner.	Short exact object-and-relation sentence; direct governing-pattern application; one exact `U.Method`, `MethodRelationStructure@BoundedContext`, or one-method `U.MethodDescription`; formal-substrate, mechanism, Work, result, structure, architecture, or C.29 representation result; quote-only cue; reduced-use cue; blocked-use disposition; or stop.
Work/method-boundary relation recovery and performed-work naming basis	`A.6.P.WMR` after generic relation recovery only while the exact relation is hidden; `C.2.P` first for epistemic source data or source material; direct subject pattern when already recoverable; `F.18` only after the governed value is known	Input, raw material, source data, source material, output, result, outcome, deliverable, handoff, or action-nominal wording whose exact claim about a method, plan, dated Work, transformation, result, delivery, transfer, representation, or receiving use is hidden	Exact entity and related governed object; claim subject, modality and exact temporal extent, polarity, recovery or support state; and either the exact direct relation or reason-specific non-assertability. A performed-work name additionally requires its A.15.1 occurrence basis, and neighboring results remain separate.	Exactly one WMR exit family: short positive or governed-negative direct subject-relation sentence; exact A.6.1 application binding; exact local A.15.PROD/A.6.RCD claim; or exact non-assertability as `factually unsupported`, `missing-information`, or `missing-governor`. A later occurrence-grounded F.18 name is not a fifth exit.
Declarative representation and imperative-metaphor overread; primary recoverable use is a visible expression or artifact, direct object, claim, graph object, publication face, evidence relation, or pattern relation being treated as action, route, call, dispatch, permission, release, work, evidence result, or direct relation obtaining	`C.2.P.DR` when no direct governing pattern already closes the claim; direct governing pattern when recovered by value	graph path, `PathSlice`, flow valuation, state predicate, checklist predicate, SQL-like query, table, dashboard, publication face, evidence-path wording, pattern relation, representation, route, path, workflow, lifecycle, dispatch, exit, receiver, call, invoke, run, flow, send, move, or `EvidencePath` wording.	Four C.2.P.DR distinctions stated by value: the visible expression or artifact; the exact current direct object, claim, or relation; the exact representation use or explicit correspondence, or `none`; and the stronger action or inference that stays blocked. Add reusable declaration, relation-occurrence identity, participant designation, reference, publication, or further representation detail only when a named receiving use needs that separate object. Name the direct owner, retained use, and stop.	`DeclarativeRepresentationRepair`; direct E.18, A.10, E.17, C.29, method, method-description, work, gate, authority, or relation application; quote-only cue; reduced-use cue; blocked-use disposition; or stop.
Architecture and structure; primary recoverable use is selected structure, `ArchitectureOf@Context` relation, conditional `ArchitectureDescription@Context` use, structural view, or named C.30 subcase	`C.30.P`	Architecture-heavy or structure-heavy wording whose EntityOfConcern under repair, relation, or claim is not yet recoverable.	`A.22` selected structure and structural-view discipline, `C.30` `ArchitectureOf@Context`, `C.30.ASV` structural-view and structure-kind discipline, named C.30 subpattern applications, and `C.30.AD` only when full architecture-description mechanism is current.	architecture-structure repair note, repaired wording, selected-structure naming, architecture question, source-return condition, governing-pattern result, ordinary-prose demotion, or stop.
Stratification and source labels; primary recoverable use is hidden behind `layer`, `level`, `tier`, `stack`, `ladder`, `rung`, `block`, `expert`, `cache`, `router`, `gate`, or close engineering source labels	`C.30.STRAT` when the governing pattern is not already recovered; direct governing pattern when it is recovered by value	Engineering, mathematical, publication, project, control, module, neural-network, or architecture prose uses a source label as if it named the FPF kind directly.	The required recovery apparatus is a row of fields for one source-label repair: source label, literal source wording, candidate primary EntityOfConcern, recovered FPF kind, recovered relation, recovered claim-use, recovered source-relation disposition, governing-pattern selection, admissible use, non-use boundary, and adjacent governing-pattern applications to `C.30.P`, `C.30.LCA`, `A.6.M`, current Architecture Transformation-Flow Structure Relation (`C.30.TFS-REL`), `E.18`, `C.16.P`, `C.29`, `C.2.P`, gate, work, or decision patterns, or ordinary source label.	`StratificationSourceLabelRepairNote`, direct governing-pattern application, ordinary-prose demotion, quote-only, reduced-use, or blocked-use disposition, or stop.
Characteristic and scale; primary recoverable use is characteristic, scale, coordinate, score, comparison, indicator role, or characteristic-space construction	`C.16.P`	Characteristic, 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`, and `Score` construction, non-comparability, non-measurement, blocked-gate disposition, governing-pattern result, ordinary-prose demotion, or stop.
Quality characterization and evaluative characterization; primary recoverable use is quality characterization, Q-bundle use, or pattern-quality coordinate use	`C.16.Q`	Quality or evaluative characterization wording when the hidden claim is not relation construction.	`C.16.P` where bearer or scale construction is hidden, `C.25` Q-bundle, `E.21` pattern-quality coordinates, and characterization or relation applications named by value.	quality-term repair note, quality-bundle or pattern-quality coordinate use, relation or bridge split when current, blocked scalar, gate, or release overread, governing-pattern result, ordinary-prose demotion, or stop.
State-family hidden claim; primary recoverable use is a bearer with a state-like value, status, readiness, currentness, or local finite field whose frame is hidden	`A.19.SPR`	State, status, posture, readiness, stance, currentness, validity, stable, accepted, blocked, candidate, admissible, ready, degraded, or close state-family compounds.	bearer kind, state frame or governing pattern, value set or classification source, admissible use, non-admissible overread, validity window or reopen condition, and direct governing-pattern application for source, evidence, assurance, gate, work, decision, temporal, lens-use, pattern-quality, or process cases.	state-family repair note, retained local field with bearer, value set, and admissible use named by value, direct governing-pattern application, quote-only cue, reduced-use cue, blocked use, ordinary-prose demotion, or stop.
Neighboring claim or admissible-use boundary already recoverable by value	Evidence, assurance, gate, work, decision, causal-use, release, mathematical-lens, naming, controlled-coarsening, action-invitation, `A.6.M` module-interface, or another governing-pattern application	Any trigger family whose recovered FPF kind, relation, claim-use, source-relation disposition, or admissible-use boundary is already recoverable by value.	The governing pattern's own ontology and conformance fields.	Direct governing-pattern application; no detour through a new restoration pattern.

Architecture source-word recovery note. When architecture prose says that a source, document, view, ADR, diagram, dashboard, model, publication face, or source-return condition carries an architecture claim, do not mint an architecture-local Source kind. Use C.2.P first only while source expression, publication construction, carrier-relation construction, source relation, project-side reference, or non-use disposition is still hidden. After recovery, the governing pattern is selected declaratively: C.30.P for architecture or structure wording, C.30.AD for architecture-description and source-return use, C.30.ASV for structural-view adequacy, C.32 for architecture synthesis or decision claims, or the governing pattern for direct evidence, assurance, gate, work, decision, publication, or currentness when that is the actual claim.

Direct known governing-pattern rule

If the governing pattern and current governed object, exact direct relation use, claim-bearing episteme, representation use, or claim kind are already recoverable by value, use that governing pattern directly. Do not put direct C.30, C.16, C.29, E.21, E.18, A.10, A.3.1, A.3.2, A.6.0, A.6.1, E.20, A.15.PROD, evidence, assurance, gate, work, decision, causal-use, release, naming, controlled-coarsening, action-invitation, A.6.M module-interface, publication-face, or mathematical-lens cases through a restoration pattern only because a familiar trigger word appears. A.6.P.WMR is used only while the exact work/method-boundary relation or exact non-assertability result remains hidden. Its known-predicate failure, unavailable-fact, and absent-governor reasons stay separately factually unsupported, missing-information, and missing-governor; only the last is a blocker that names a future owner.

Apply A.6.RSIR, A.6.P, A.6.P.WMR, A.6.F, C.2.P, C.2.P.DR, C.30.P, C.30.STRAT, C.16.P, C.16.Q, A.19.SPR, or A.3.1 only when wording hides the EntityOfConcern under repair, direct relation use, role assignment, signature declaration, interface claim, declaration-local SlotKind, characteristic, scale, score, quality characterization, comparison reference set, source-relation disposition, state-family value, method-side governed object, work/method-boundary claim, declarative-representation use, admissible use, or remaining reader use.

Admission and extraction criterion

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

the wording recurs across FPF-governed texts or project text deliberately using FPF-governed terms, pattern references, relation names, or conformance claims;
the hidden primary-EntityOfConcern 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 primary EntityOfConcern and first useful move;
a useful remaining reader use survives after overread removal;
no existing governing pattern already carries the row without duplicating repair-only doctrine inside subject patterns.

Do not add a new realization pattern when an existing governing 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 governing pattern already carries the EntityOfConcern under repair, relation, claim, or field. Record that pattern as the governingPattern.

Extract repair-only material from a subject pattern when the material is only wording-recognition lists, false-friend rows, anti-umbrella prose, or repair fields that must run before the subject pattern can state its own invariant. Leave a narrow first-use cue or governing-pattern relation 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.

Subject-pattern thin-pointer rule

Subject patterns keep at most one local first-use cue when the EntityOfConcern under repair, relation, claim, or field is hidden, then name the selected precision-restoration pattern as a pattern through ordinary references or Relations. They do not turn that reference into local reference boilerplate, and they do not copy:

the full E.10 wording-recognition table;
this shared algorithm;
the WordingUseRestorationApplicabilityTable;
broad false-friend lists whose only job is first-stage repair;
past placement or repair history written in place of current 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 use under repair is selected structure, architecture-description use, structural-view use, source, model, diagram, graph, dashboard, or ordinary prose;
use C.30.STRAT when layer, level, tier, stack, ladder, rung, block, expert, cache, router, gate, or a close source label hides whether the use under repair is a control-layer relation, module-interface relation, architecture-to-TransformationFlowStructure relation, scale or coarse-graining relation, publication relation set, gate relation, neighboring use named by value, ordinary source label, quote-only cue, or blocked use;
use C.16.P when metric, score, axis, dimension, feature, property, indicator, strong, weak, robust, level, coordinate, threshold, or comparison wording hides characteristic or scale construction;
use C.16.Q when quality or evaluative characterization wording hides Q-bundle, pattern-quality coordinate, relation construction, action-invitation, bridge, or characterization use named by value;
use A.19.SPR when state, status, posture, readiness, stance, currentness, or a local state-like field hides bearer, state frame, value set, admissible use, or governing pattern;
use C.2.P when source, publication, publication form, face, PublicationUnit, dashboard, documentation, or text-work wording hides source-currentness relation or project-side reliance;
use A.3.1 only while method, algorithm, program, proof, solver, workflow, process, procedure, access-path, query-plan, control-strategy, method-algebra, method-graph, selector-calculus, or programming-paradigm wording still hides one exact U.Method or a separately governed one-method U.MethodDescription, mechanism, plan, dated Work, transformation, result, structure, architecture, representation, or direct relation; then apply that object's direct owner;
use A.6.RSIR when relation, signature, interface, role, assignment, enactment, slot, field, parameter, argument, endpoint, port, API, protocol, connector, capability, affordance, method, function, concern, or interest wording hides the current governed object or claim kind and no direct governing pattern is yet clear;
use A.6.P.WMR only while input, raw-material, source-data, source-material, output, result, outcome, deliverable, handoff, or work-name wording still hides one exact method, plan, Work, transformation, result, delivery, transfer, representation, or receiving-use relation; use C.2.P first for the epistemic source side, bypass to the direct owner when clear, and never close through classification or a merely type-correct designation;
use C.2.P.DR when a declarative representation, graph relation, evidence-path wording, publication face, checklist predicate, query, dashboard, or pattern relation is being overread as an imperative route, call, dispatch, work sequence, permission, release, evidence result, or pattern application;
use the direct governing pattern, with A.19.SPR only when hidden state-family wording remains, when admissibility-like, legal, lawful, validity, pass-looking, fail-looking, readiness, conformance, or authority wording already recovers its bearer, claim kind, source relation, value frame, and admissible use.

Name and placement discipline

semanticArea is the selected Part-F Tech term for the semantic unit used by a wording-use restoration row. Plain speech may say "semantic area" or "meaning area" only as a gloss for that declared Part-F row or bounded row-set.

meaning area, theme, pattern area, pattern cluster, workstream, campaign, module, and branch are not selected as Tech architecture terms for this distribution. Tech prose must resolve those cues into semanticAreaBaseConcept, semanticArea, semanticAreaSenseFamily, entityOfConcernUseFields, ontologicalNeighborhood, governingPattern named by value, 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.

SelectedLocusObligationClosure is the current E.9.DA coordinate name for selected-locus obligation closure. Do not reintroduce ReceivingLocusObligationClosure as a general obligation kind, locus kind, pattern role, or restoration vocabulary.

Examples and near misses

Wording	Applicable result	Blocked overread
`MaintenanceReport_42` says “Bearing_B is installed in Pump_P.”	The direct mereology pattern is already clear, so bypass E.10.ARCH. State `Bearing_B isPartOf Pump_P`; keep `MaintenanceReport_42` as the claim-bearing episteme that asserts that exact predicate. If a named later use needs occurrence identity, identify the obtaining parthood occurrence or its temporal extent under the direct relation owner. If it instead needs the installation act that established the condition, recover a separate dated Work occurrence under A.15.1 and/or an actual transformation under A.3.4 plus their exact direct relations; neither the act nor the transformation is the parthood occurrence.	report-as-relation; assertion-as-obtaining; report fields as world-side participants; parthood occurrence as installation Work or transformation.
Graph edge `Edge_17(Bearing_B, Pump_P)` presents that assertion.	The representation use is already clear, so bypass E.10.ARCH to C.29. Keep `Edge_17` as a representation element with an explicit correspondence to the represented assertion or direct-relation claim; the edge does not make `Bearing_B isPartOf Pump_P` obtain or identify its occurrence.	edge-as-world-relation; adjacency-as-obtaining; graph identity as relation-occurrence identity.
A reusable `RelationSignature` declares `ParticipantSlot`, and a row shows `Bearing_B_Ref`.	The declaration use is already clear, so bypass E.10.ARCH to A.6.5. `ParticipantSlot` is a `SlotSpec`; `Bearing_B` is the actual governed participant; `Bearing_B_Ref` is a participant designation only inside the current assertion or occurrence-description episteme.	SlotSpec-as-participant; designation-as-participant; type-correct filling as obtaining.
`MethodDescription_NormalizeCustomer`, which describes one exact `U.Method` `NormalizeCustomer`, says “input x is CustomerRow_17” beside the worked formula `normalize(x)`.	The current use is the worked formula's argument representation, so bypass E.10.ARCH to C.29. Keep `Arg_x` as the representation element and state the explicit correspondence from `Arg_x` to the described value `CustomerRow_17`. The repaired practitioner sentence is: “In the worked formula `normalize(x)`, argument `x` represents `CustomerRow_17`.” That correspondence neither asserts a universal input relation nor establishes participation in dated Work or an actual transformation.	universal input ontology; argument place as world-side participant; method description as actual Work or transformation; representation correspondence as obtaining.
Another source calls something `input`, but its exact object or use remains hidden.	Bound the exact sentence, then use the wider dispatch only until its owner is clear: A.3.2 for a declared or represented value inside a `U.MethodDescription` about one exact method; A.15.2 for intended planned use; A.15.1 plus the exact participation or resource owner for dated Work; A.3.4.P plus the direct transformation owner for an actual transformation participant; the exact production, measurement, evaluation, delivery, or acceptance owner for a result claim; or C.29 for an argument, tuple component, edge, or other representation place. The repaired sentence states the exact direct relation or representation correspondence returned by that owner; naming only the pattern is incomplete. Use A.6.P.WMR only while that relation remains hidden.	routing list as repair; universal input ontology; one generic result relation; premature Work or transformation actuality.
"The architecture is the diagram."	`C.30.P` recovers whether the diagram is publication form, structure view, architecture description, source relation, or ordinary source-finding cue; then `C.30` or `C.30.ASV` applies only after the selected architecture or structural-view use is recovered.	diagram-as-architecture; diagram-as-proof; diagram-as-gate.
"`ArchitectureOf@PlantOps` is defined over structures S1 and S2 under context C."	Direct `C.30`; no `C.30.P` unless selected structure, architecture-description use, structural-view use, source relation, model relation, diagram relation, graph relation, dashboard relation, or ordinary prose remains hidden.	unnecessary restoration detour.
"The model has three layers."	`C.30.STRAT` treats `layers` as a source label until the recovered FPF kind, relation, claim-use, or source-relation disposition is recovered: control-layer relation, neural-network block sequence, publication relation set, mathematical scale or coarse-graining relation, or ordinary source wording. Then the governing pattern applies to the recovered result.	layer-as-universal-kind; source label as proof of structure.
"The query plan calls the next pattern."	`C.2.P.DR` recovers whether the query plan is a representation, a one-method description episteme, formal substrate, evidence or provenance relation, or ordinary source wording; if a pattern relation is current, state it declaratively rather than as a call.	query-as-work sequence; pattern relation as invocation.
"The evidence path authorizes release."	If a provenance relation for a claim is current, use `A.10`; if authorization or release is current, use the authority, gate, or release pattern. `C.2.P.DR` applies only when `path` wording turns the relation into an action route or permission.	evidence path as permission; graph relation as release.
"The solver algorithm is the mechanism."	`A.3.1` first recovers whether the wording denotes one exact method or a direct method-side relation. `A.3.2` applies only when a current episteme describes that one method. Formal substrate, C.29 representation, mechanism declaration or realization, Work, result, and quote-only wording remain separate direct-owner exits.	algorithm-as-default-method; method-as-mechanism by vocabulary.
"This record is admissible."	Recover bearer, claim kind, source relation, value frame, admissible use, and governing pattern. Use `A.19.SPR` only if hidden state-family wording remains; otherwise use the direct evidence, gate, mechanism, temporal, authority, release, or source-relation pattern.	admissible-as-generic status; pass-looking word as gate.
"This score proves readiness."	`C.16.P` recovers characteristic, scale, value, score, threshold, comparison reference set, and gate, evidence, and decision pattern applications.	score-as-proof; score-as-release permission.
"This source supports the claim."	`C.2.P` is used if source-currentness relation or publication relation set is current; relation slice applies `A.6.P`; final use states recovered relation or non-use disposition.	source-as-proof; support-as-generic relation.
"Quality improved."	`C.16.Q` recovers quality characterization or evaluative characterization, or names the `C.16.P`, `C.25`, `E.21`, `A.6.P`, action, work, or bridge pattern application governing the recovered claim.	quality-as-one scalar; quality-as-gate.
"The function improved maintainability."	`A.6.F` first recovers the FPF kind named by value, relation, or claim when hidden; quality or maintainability wording is then governed by `C.16.P`, `C.16.Q`, `C.25`, or the quality pattern governing the current claim.	function-as-default-architecture; maintainability-as-unscaled verdict.
"Read this pattern for improvement proposals."	Recover whether the current FPF-governed use is source-publication use, bounded comparative review unit, or improvement-oriented evaluation. Use `E.22` only for improvement-oriented quality review under a declared pattern-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 current, `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.

Archetypal Grounding

Situation	E.10.ARCH move	Boundary
Architecture text repeatedly says diagrams, ADRs, dashboards, and views are not architecture.	Use the architecture and structure row, then apply `C.30.P` or `C.30.AD` according to the recovered architecture field.	C.30 remains about architecture and selected structures, not a generic diagram-warning pattern.
Method text uses algorithm, workflow, solver, proof, and program as one family.	Use the method, work, and P2W constellation row and recover one exact method, `MethodRelationStructure@BoundedContext`, one-method description episteme, formal substrate, mechanism, work plan, dated Work, result, or representation separately.	Do not assign one typed value to several kinds because one source label was shared.
A dashboard or evidence-path wording is treated as permission or release.	Use the declarative-representation row or the direct evidence, gate, authority, or release pattern.	Graph and provenance relations remain legitimate when they are not overread as routes, calls, permissions, or releases.

Bias-Annotation

This pattern blocks semio-bias in two directions. It prevents subject patterns from becoming patterns about descriptions, records, and wording guards. It also prevents word-replacement bias by requiring recovery of the ontological neighborhood, direct governing pattern, and admissible reader use before a new term is selected.

Conformance Checklist

Check	Observable conformance condition
`CC-E10ARCH-1`	`E.10` remains the compact trigger-and-applicability pattern; `E.10.ARCH` carries the shared algorithm and applicability-row architecture.
`CC-E10ARCH-2`	Each applicability row is an authoring/publication construct whose minimum content is recurring wording, exact governed object, exact claim or use, direct owner, repaired wording, surviving reader use, and blocked stronger reading. Optional declaration, designation, reference, publication, and representation fields appear only when current. Ordinary engineers are not required to fill the row.
`CC-E10ARCH-3`	Direct known cases bypass restoration. The installed-bearing report, C.29 graph edge, reusable `ParticipantSlot`, and source-word `input` cases preserve direct relation, assertion, declaration, actual participant, representation, method/work/transformation/result, and direct-owner boundaries.
`CC-E10ARCH-4`	A new realization pattern is added only when no existing governing pattern carries the stable recovery shape without duplicating repair-only doctrine inside subject patterns.
`CC-E10ARCH-5`	Subject patterns of concern keep their primary `EntityOfConcern` and first useful move central and carry only thin first-use cues to precision restoration when wording is hidden. Generic guards about description and publication use are kept in a named description and publication-use boundary section or description-publication pattern governing that use; they do not become the subject Solution.
`CC-E10ARCH-6`	`reading`, `read`, and `quality-read` wording remains trigger wording and does not mint `ReadingPrecisionRestoration`.
`CC-E10ARCH-6a`	EntityOfConcern-like hidden fields follow the selected ownership split: `E.10` recognizes the wording-use row; `C.2.1` governs episteme identity and the identified `EntityOfConcern` participant; A.6.5 governs `EntityOfConcernSlot` only as a `SlotSpec` inside a reusable constitution `RelationSignature`; direct reference patterns govern `entityOfConcernRef`, `EntityOfConcernRef`, and related reference uses; `C.2.P` restores episteme, publication, source-wording, and source-relation wording; `F.18` settles durable heads and source-string decisions; `E.17.AUD.OOTD` carries publication-unit primary entity of concern; and governing patterns carry their own claim or admissible-use boundary. Neither declaration nor designation constitutes the participant.
`CC-E10ARCH-6b`	State-family wording follows the selected distribution: `E.10` recognizes the wording-use row, `A.19.SPR` realizes recurring hidden bearer, state-frame, value, and use recovery, and governing patterns carry already-recovered evidence, assurance, gate, work, decision, temporal, mathematical-lens, pattern-quality, source-relation, or process cases directly.
`CC-E10ARCH-6c`	Stratification and source-label wording follows the selected distribution: `E.10` recognizes the wording-use row, `C.30.STRAT` realizes recurring source-label repair, and governing patterns carry already-recovered control-layer, module-interface, architecture-to-`TransformationFlowStructure`, scale or coarse-graining, publication relation set, gate, work, decision, or ordinary non-use cases directly.
`CC-E10ARCH-6d`	Admissibility-like, legal, lawful, validity, pass-looking, fail-looking, readiness, conformance, and authority wording does not mint a generic admissibility object. The repair recovers bearer, claim kind, source relation, value frame, admissible use, non-admissible overread, and the direct governing pattern; `A.19.SPR` is used only when hidden state-family wording remains.
`CC-E10ARCH-6e`	Method-like wording recovers one exact `U.Method`, while `MethodRelationStructure@BoundedContext` keeps exact method-side relations separate and a `U.MethodDescription` describes one exact method. Mechanism, plan, dated Work, transformation, production/inception/completion claim, result, delivery or acceptance, selected structure, architecture relation, architecture description, and representation remain separately governed objects and direct relations. One source label may expose several such values, but no value acquires dual `U.Method`/`U.Mechanism` typing and no declaration-local `SlotSpec` or participant label becomes a second ontology without independent admission.
`CC-E10ARCH-6f`	Declarative representation overread follows `C.2.P.DR` unless a direct graph, evidence, publication, method, work, gate, authority, or pattern-relation pattern already governs the recovered claim by value. Graph paths remain legitimate graph relations when that is the current claim; evidence-path wording is legitimate only after recovery as an evidence or provenance relation. They become repair triggers when read as routes, calls, dispatches, permissions, releases, work sequences, or evidence results by metaphor.
`CC-E10ARCH-6g`	Terminology-source audit is bounded: source-ontology labels are recovered when they affect the governed object, direct relation kind, relation-participant meaning, actual participant kind, declaration-local SlotSpec, assertion-side participant designation, exact use, admissible use, or governing-pattern selection; otherwise stable ordinary prose stays ordinary. Relation-shaped material follows the relation-use recovery rule, and `interface` is used only under a governing boundary, module-interface, signature, port, publication, or source-label disposition.
`CC-E10ARCH-6h`	Relation-signature-interface-role-slot wording follows the selected two-level architecture: `E.10` recognizes the trigger row, `E.10.ARCH` places the row, `A.6.RSIR` recovers project concern and current EntityOfConcern or claim kind only until a direct governing pattern is clear, and the direct pattern owns the final repair. Do not mint generic `U.Interface`, a standalone role-slot ontic, `U.Concern`, `U.Interest`, or episteme-role ontology.
`CC-E10ARCH-6i`	Work/method-boundary wording uses `C.2.P` first for an epistemic source side, bypasses to a clear direct owner, and otherwise lets `A.6.P.WMR` return exactly one of its four families. `F.18` names performed Work only after occurrence grounding. Classification, a generic result label, or a designation that merely type-checks against a declaration does not close the case.
`CC-E10ARCH-7`	`function`, `functional`, `functionality`, and `effect` wording keeps `A.6.F` as first unpacker when the governed FPF object, direct relation use, claim-bearing episteme, view, or governing-pattern application is hidden and does not default to architecture.
`CC-E10ARCH-8`	`semanticArea`, `ontologicalNeighborhood`, and `pattern nest` follow `E.8` placement discipline: `semanticArea` is the Part-F semantic unit, `ontologicalNeighborhood` is its applicability neighborhood, and `pattern nest` is placement. None of them becomes workstream, campaign, module, or authority-bearing record.
`CC-E10ARCH-9`	Repair removes overread and preserves one useful admissible reader use. Type-correct but inert wording is not recovered by value.
`CC-E10ARCH-10`	Validation covers duplicate recognition tables, broad placeholder heads, declaration/participant collapse, representation-as-obtaining, one-description/many-object collapse, optional apparatus without a receiver, practitioner-row bureaucracy, shadow restoration apparatus, and entry or index drift.

Common Anti-Patterns and How to Avoid Them

Anti-pattern	Symptom	Repair
Generic container recovery	A record, row, field, or slot-shaped placeholder is presented as the recovered ontology although the current object could be a direct relation, assertion episteme, declaration, participant designation, publication form, or representation.	Name the exact governed object and its direct owner; add declaration, assertion, reference, publication, or representation apparatus only for a named receiving use.
Representation becomes obtaining	A graph edge, tuple component, diagram element, or table cell is treated as the world-side relation or its occurrence identity.	Keep the element under C.29 or its publication owner, state the represented object and explicit correspondence, and apply the direct relation pattern separately.
Method description becomes a project constellation	One `U.MethodDescription` is made to contain a method family, mechanism, plan, Work occurrence, transformation, result, architecture, and representation as if they were one object.	Let one `U.MethodDescription` describe one exact `U.Method`; enumerate every other current object and direct relation under its own governing pattern.
Authoring row becomes a practitioner form	Engineers are required to complete an applicability row before using a clear direct pattern.	Keep the row inside E.10.ARCH authoring and publication architecture; give practitioners the shortest exact object-and-relation sentence and bypass restoration when the owner is clear.
Classification or type-correct-designation fallback without repair	The text names a restoration pattern, generic result label, method-description field, planned use, compatible type, or designation but leaves no exact governed object, direct relation, claim-bearing episteme, direct owner, truthful WMR exit, or blocker.	Apply the selected direct pattern to one truthful result or fail closed; type correctness and designation do not establish actuality.
Trigger registry copying	`E.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 subject pattern of concern and cite `E.10` and `E.10.ARCH` through ordinary references or `Relations`.
Umbrella-to-umbrella replacement	`support` becomes `basis`, `display` becomes `view`, `reading` becomes `evaluation`, or `function` becomes `role` without a recovered governed object and exact use.	Recover the governed object, any direct relation use, admissible use, and remaining reader use; otherwise demote or block.
Source-ontology smuggling	`interface`, `schema`, `record`, `profile`, `path`, or another familiar source-domain word is used because it sounds precise, but the recovered governed object or direct relation use is different.	Recover the source ontology, governed object, exact direct relation use, any declaration-local SlotSpec or assertion-side designation, and governing pattern; keep the source word only when that pattern makes the meaning current.
Over-annotated restoration	A clear subject sentence is expanded into type labels or source-ontology commentary even though no object, kind, relation, slot, admissible use, or governing pattern changes.	Keep the ordinary wording; annotate only the claim-governing term under repair and use `F.19` if phrase apparatus remains.
Sterile precision	The wording is ontologically well-formed but no working reader can tell why the distinction matters or what reader use remains.	Restore the didactic or recognition function in admissible wording, or classify as reduced-use cue, quote-only, blocked use, or incomplete rewrite.
Shadow precision-restoration pattern	A 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.
Reference boilerplate in subject pattern	A subject pattern explains where the repair belongs, why the package was split, or what this text does not contain instead of stating the subject pattern's own repaired wording or first move.	Move architecture-placement rationale to `DRR` or architecture notes; replace routing prose with a normal pattern id, citation, or `Relations` row.
Apparatus-preserving paraphrase	A repair changes wording but keeps phrase-level apparatus around a recoverable kind.	Apply `F.19` first; return to `E.10.ARCH` only for remaining word, head, or use precision.
History placement as pattern prose	Past placement or old naming text explains history instead of current use.	Keep only current entry or repair rows where needed; write current pattern prose in the selected placement.

Consequences

Benefits. Wording-use restoration stays distributed but coherent; subject patterns stay object-centered; recurring hidden-field families get one recovery architecture instead of many local catalogues.

Costs. Authors must decide whether the current case is local E.10, a direct governing pattern, an existing restoration row, or a new row with a stable recovery shape.

Risks avoided. The main avoided risks are semio-bias in subject patterns, lexical substitution without kind recovery, and pattern-nest or placement language masquerading as semantic-area architecture.

Rationale

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 primary EntityOfConcern and first useful moves. A common symptom is a non-semio pattern whose Solution mainly teaches that a description, view, publication, record, card, diagram, source, or file is not a permission, promise, prescription, evidence record, assurance verdict, decision, gate passage, release, work occurrence, or authority source. Those guards are often correct, but their ontology is publication pragmatics, description pragmatics, and neighboring-pattern assignment, not the subject matter of the architecture, method, role, evidence, or characterization pattern. 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 a named semanticArea has stable row identity, a stable field set, an ontologicalNeighborhood, and a remaining reader use.

SoTA-Echoing

Source or practice line	Source-use function or relation	What the line changes in `E.10.ARCH`
Current FPF distribution: `E.10`, `E.10.ARCH`, `A.6.P`, `A.6.F`, `C.2.P`, `C.30.P`, `C.30.STRAT`, `C.16.P`, `C.16.Q`, `A.19.SPR`, `F.18`, `E.8`, `E.19`, `E.11`, and `I.2`.	Current FPF-internal architecture source line for the selected distribution.	Keeps `E.10` compact, puts the shared recovery algorithm in `E.10.ARCH`, assigns relation, source-relation, architecture, stratification-source-label, characteristic, quality, state-family, function-like, naming, entry-distribution, and expanded entry-disambiguation cases to realization or governing patterns named by value, and gives `E.19` a distribution-preservation check.
Pattern-language locality and FPF primary-EntityOfConcern discipline in `E.8` and `E.19`.	Current FPF authoring and review source line; not an external standard imported as ontology.	Forces thin governing-pattern pointers and blocks local wording-recognition-table copies inside patterns of concern whose real work is architecture, structure, characteristic, quality, evidence, gate, work, decision, state-family precision, 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 and reference-use source line; it does not define FPF kind ontology.	Provides 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 governing-pattern coverage in FPF.	Applicability boundary for this architecture, not evidence that E.10.ARCH owns every wording-use case.	Uses the direct governing pattern when that pattern can carry the EntityOfConcern under repair, relation, claim, or local field directly; reopens E.10.ARCH only when the shared distribution rule itself no longer fits.

The selected architecture is lowered or reopened when one of those source lines changes: if E.10 can close the issue locally, if a new governing 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.

Relations

E.10 recognizes and closes local wording issues or selects the applicable row.
A.6.RSIR realizes first-level recovery for the relation, signature, interface, role, and slot cluster only until the direct governing pattern is clear.
A.6.P realizes the shared algorithm for generic relation construction and retained relation specializations; A.6.P.WMR specializes one current method/work-boundary relation-bearing claim and returns exactly one family: an exact direct subject-relation claim, positive or governed negative; an exact A.6.1 operation-application binding; a local A.15.PROD claim or another local relation-bearing claim selected under A.6.RCD disposition 2; or an exact non-assertability result independently reasoned as factually unsupported, missing-information, or missing-governor; only the last names the affected receiving use and future owner. A.6.RCD owns only the residual needed-claim derivation and relation-kind admission question after exact participants are known and no lighter current governor closes the receiver.
A.6.F realizes function-like kind and relation recovery.
C.2.P realizes source-expression, episteme, publication, and FPF-governed-use recovery.
C.2.P.DR realizes declarative representation and imperative-metaphor overread repair.
A.3.1 governs one exact U.Method and MethodRelationStructure@BoundedContext for exact method-side relations once recovered; method-like wording reaches it only while that governed object remains hidden.
A.3.2 governs a U.MethodDescription episteme that describes one exact U.Method; it does not absorb a mechanism, plan, Work occurrence, transformation, result, structure, architecture, or representation.
A.6.0 and A.6.5 govern reusable signatures and SlotSpec declarations; C.29 governs tuple, argument, edge, diagram, and other representation use plus explicit correspondence; A.6.1 and E.20 govern mechanism meaning and governing-definition assignment. E.24 alone introduces an exact onticSlotRelation when durable ontic settlement is current.
A.15.2, A.15.1, and A.10 govern planned work, dated work, and evidence or provenance relations that method-like or path-like wording may otherwise hide; A.15.PROD governs the local production-work, entity-identity-inception, or production-completion claim when that exact WMR exit is current.
E.18 governs graph paths, path slices, flow valuations, and graph relations over selected TransformationFlowStructure when the graph claim is current.
C.30.P realizes architecture and structure wording recovery.
C.30.STRAT realizes stratification and source-label wording recovery for layer, level, tier, stack, ladder, rung, block, expert, cache, router, gate, and close source labels before return to the governing pattern.
C.16.P realizes characteristic and scale wording recovery.
C.16.Q realizes quality characterization and evaluative characterization wording recovery.
A.19.SPR realizes state-family wording recovery when bearer, state frame, value set, admissible use, or governing pattern is hidden.
F.18 governs durable reusable naming after the kind under repair or relation is known.
F.19 governs phrase-level ontology-first plain technical rewriting after the kind under repair is recovered or while proving it is still hidden.
E.8 governs pattern-form and placement wording.
E.19 checks distribution preservation during review and refresh.
E.11 governs entry-distribution and assigns broad or old-term entry cases to README scenarios, ToC query cues, local Problem frames, or I.2 expanded entry-disambiguation cases.

E.10.ARCH:End

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

#Wording-Use Ontological Precision Restoration Architecture

#About this pattern

#How to use this pattern

#Relations

#Content

#Use This When

#Problem Frame

#Problem

#Forces

#Solution

#Primary EntityOfConcern and applicability-row scope

#Distribution architecture

#EntityOfConcern and recurring hidden-field distribution

#Ontic-Level and Facet-Level Restoration Distribution

#Shared recovery algorithm

#Method, work, and P2W governing-pattern constellation in wording restoration

#Applicability table

#Direct known governing-pattern rule

#Admission and extraction criterion

#Subject-pattern thin-pointer rule

#Name and placement discipline

#Examples and near misses

#Archetypal Grounding

#Bias-Annotation

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

#Rationale

#SoTA-Echoing

#Relations

#E.10.ARCH:End

Wording-Use Ontological Precision Restoration Architecture

About this pattern

How to use this pattern

Relations

Content

Use This When

Problem Frame

Problem

Forces

Solution

Primary EntityOfConcern and applicability-row scope

Distribution architecture

EntityOfConcern and recurring hidden-field distribution

Ontic-Level and Facet-Level Restoration Distribution

Shared recovery algorithm

Method, work, and P2W governing-pattern constellation in wording restoration

Applicability table

Direct known governing-pattern rule

Admission and extraction criterion

Subject-pattern thin-pointer rule

Name and placement discipline

Examples and near misses

Archetypal Grounding

Bias-Annotation

Conformance Checklist

Common Anti-Patterns and How to Avoid Them

Consequences

Rationale

SoTA-Echoing

Relations

E.10.ARCH:End