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. Use E.10 to recognize overloaded wording, E.10.ARCH to find the applicable row and choose the first restoration or the rule for an already recovered claim, and extraction only when repair-only prose is repeated inside a subject pattern.

E.10.ARCH is not a generic language-cleanup pattern. Its mechanism is ontological reconstruction: recover the object or relation at issue, the use that makes the wording consequential, and the pattern text that defines or constrains that object, relation, 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 explicitly restricted direct-relation claim, first name the obtaining relation and its actual participants as specified by the ClaimGraph that defines the predicate. 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 a defining rule establishes another object and an explicit correspondence. Use an E.24 onticSlotRelation only after durable ontic settlement makes that direct relation current. A mathematical tuple or argument position stays representation-side until an explicit correspondence relates it to a declared SlotSpec. Using E.10.ARCH creates none of those objects; the author returns to the rules that define, constrain, or test them, with the PatternIDs serving only as locators. 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. In DPF authoring, enter through E.4.DPF only when recurring domain wording prevents reliable use of named DPF patterns. The shared method remains in FPF; each domain entry remains in the DPF that uses it.

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 pattern that defines or constrains the object, relation, or use.

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: recover the typed object, use its defining, constraining, or testing rule when available, and keep only a thin pointer in a subject pattern instead of repeated repair doctrine.

Builds on. E.10, E.10.MOVE, 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 the evidence, assurance, gate, work, decision, causal-use, release, and publication passages that define or constrain those claims when they are current.

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 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 siblingRecovering What “Role” Means in the Current Claim

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 referenceMove and Readiness Wording Precision Restoration

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 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 referenceRecovering What “Learning” Means in the Current Claim

E.10.ARCHexplicit referenceRecovering What “Role” Means in the Current Claim

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 referenceEpisteme viewing - EntityOfConcern-preserving episteme construction

E.10.ARCHexplicit referenceEntityOfConcern retargeting

E.10.ARCHexplicit referenceSystem-Role–Method–Work Alignment

E.10.ARCHexplicit referenceThe Agential Role & Agency Spectrum

E.10.ARCHexplicit referenceU.SystemRoleAssignment - Contextual System-Role Assignment

E.10.ARCHexplicit referenceSystemRoleAssignment and Performed-Work Attribution Check

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

E.10.ARCHexplicit referenceTransformation Ontic Precision Restoration

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

E.10.ARCHexplicit referenceRelation Obtaining and Individuated Relation Occurrences

E.10.ARCHexplicit referenceModule Relation Repair

E.10.ARCHexplicit referenceSystemRoleAssignmentStateRelation - Assignment-State Recognition and Work Admission

E.10.ARCHexplicit referenceWork-Entry Readiness and Full-Kit Preparation

E.10.ARCHexplicit referenceGate Decisions from Independent Check Results

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 referenceAction-Invitation Precision Restoration (ACT-INV)

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

E.10.ARCHexplicit referenceBase Declaration Discipline - Direct relation first; reusable declaration only when needed

E.10.ARCHexplicit referenceTrust and Assurance Calculus

E.10.ARCHexplicit referenceConstraint Validity for Transformation Steps

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

E.10.ARCHexplicit referencePublicationUnit Primary-Subject Discipline

E.10.ARCHexplicit referenceDomain Principle Framework Authoring and Publication-or-Access Carrier Assembly

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, an author uses the recovery architecture described here, and every recovered object remains the subject of its own exact assertion under its defining or constraining ClaimGraph.

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 another recovered claim and the rule that defines or tests it;
state-family wording such as state, status, posture, readiness, stance, or currentness before the bearer, state frame, value set, admissible use, and defining or testing rule are 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 the defining or testing rule 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;
bare claim-bearing role before its work-facing or use-facing object is recovered; E.10.ROLE is the bounded first entry. For relation, signature, interface, assignment, enactment, slot, field, parameter, argument, endpoint, port, API, protocol, connector, capability, affordance, method, function, concern, or interest wording, use A.6.RSIR only while the direct relation, declaration, interface, operation, representation position, or defining or testing rule remains hidden;
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 exact object, claim, and defining or testing rule are 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: use E.10 to recognize the wording-use row; use E.10.ARCH to select the row and extraction criterion; use the defining, constraining, or testing rule for the recovered object together with its practical guidance; and state the exact subject assertion, primary EntityOfConcern, and first useful move. Cite the PatternID only to locate that rule.

First useful move. Decide whether E.10 can close the wording locally, whether the recovered object or claim already has a defining, constraining, or testing rule, or whether one applicability row is needed 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 governed object, exact direct relation, or claim-bearing episteme and its defining or testing rule are already recoverable by value, state the claim under that rule and cite the pattern containing it.
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, state the exact assertion under its invariant or predicate and cite the pattern containing that rule. E.10.ARCH defines only 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.
Known rule vs restoration detour	Use the rule that defines, constrains, or tests an already recovered object or claim; do not route it through another restoration pass.
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 and E.10.ARCH for the shared distribution architecture. Once the object, relation, or claim is recovered, use its defining, constraining, or testing rule and cite the pattern that contains it. Add an applicability row only when recurring wording hides a stable recovery shape and a useful surviving reader use that no existing rule 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 rule that defines or constrains that object, relation, or representation, and the pattern ID that locates the rule;
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, subject patterns, 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:

The author uses E.10 to recognize an FPF-governed wording use, close it locally when possible, or select a defining or testing rule, controlled precision-reduction pattern, durable-name application, or fail-closed non-use disposition.
The E.10.ARCH text contains the shared recovery algorithm and the WordingUseRestorationApplicabilityTable.
The author applies a bounded entry or realization pattern such as E.10.LRN, E.10.ROLE, 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, or A.3.1, or directly uses the rule for an evidence, graph, method, mechanism, work, gate, authority, release, or publication-use claim. The selected content unpacks the wording for one named semanticArea and its ontologicalNeighborhood. Use E.10.LRN only while claim-bearing learning wording hides the changed subject, Work, Method, result, evidence, or use. Use E.10.ROLE only for bare claim-bearing role. Use A.6.P.WMR after generic relation recovery only when one Method and Work boundary claim remains hidden; use A.6.RCD only after exact participants are recovered and no current direct relation or already admitted local relation-bearing claim closes the 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 subject pattern already carries.
E.8 defines pattern-form and placement requirements for wording such as pattern nest, and requires authoring prose that uses ontologicalNeighborhood to expose the relevant semanticAreaBaseConcept, semanticArea, and semanticAreaSenseFamily rather than treating neighborhood as the semantic unit.
An author or reviewer uses E.19 to check 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 defines episteme identity and the identified EntityOfConcern participant of EpistemeConstitutionRelation; A.6.5 defines EntityOfConcernSlot only inside a reusable constitution RelationSignature; direct reference rules define or constrain 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.
When an evidence, assurance, gate, work, decision, architecture, characteristic, mathematical-lens, or project-side claim is already recoverable, use the rule that defines or constrains that exact claim or its admissible-use boundary.

This selected-family case is the standing example for recurring hidden-field architecture. When a new hidden-field family recurs, do not add local warning prose to every pattern. Use an existing defining or testing rule when one fits, add one applicability row when shared recovery is needed, and justify 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. The author uses it to identify an FPF wording-use problem and choose the first applicable restoration or the rule that already defines or tests the recovered object or claim. E.10.ARCH supplies the distribution rule. A specialized restoration pattern contains only the defining content for stable ontological recovery in one selected ontic, semantic area, or high-pressure facet.

When the governed object, exact direct relation, claim-bearing episteme, representation use, or claim kind is already recoverable by value, use its defining, constraining, or testing rule directly and cite the pattern containing that rule. A clear A.3.4, A.6.F, C.29, E.18, C.30, A.15, A.10, gate, decision, publication, or evidence claim needs no restoration detour merely because a familiar trigger word appears.

For bare claim-bearing role, use E.10.ROLE to recover the sentence's work-facing or use-facing object and stop when one exact object or relation and its defining rule are clear. Use A.6.RSIR only for the narrower relation-signature-interface-assignment-slot cluster, including direct-relation, declaration, interface, operation, and representation branches recovered under E.10.ROLE. Neither entry is a new ontology; after selection, the recovered object's rule defines the content and its pattern ID is only a locator.

For claim-bearing learn, learning, learned, taught, or trained wording, use E.10.LRN only while the participant, changed subject, Work, Method, result, evidence, or receiving use is hidden. It returns corrected or split claims to their direct capability, Work, model-fitting, inference, information-acquisition, representation, cultural-change, product, evidence, or decision owners. It defines no generic learning process, result, role kind, progress scale, or UTS value. 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 subject 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 existing rule 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 A.22, A.19, C.30, A.3.4, C.2.1, or another pattern already contains the defining or testing rule for the recovered object or claim, use that rule directly and cite E.24.CD or E.24.PUB only for the relevant thin boundary.

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 selected FPF kind or direct relation use, and would otherwise force repeated first-stage repair prose. Otherwise use the rule that defines the direct relation and apply A.6.5 only when reusable declaration is current.

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 subject 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 object, any direct relation use, any current claim-bearing episteme or representation, the rule that defines or constrains each, and the pattern ID that locates that rule;
the defining, constraining, or testing rule to use directly when the value is already recoverable;
any facet restoration pattern whose ClaimGraph defines or constrains a narrower recurring ambiguity;
the temporary recovery product and the retained user-facing move after wording repair.

DPF-local application

When authoring or maintaining a DPF, use this shared method only when the E.4.DPF entry condition holds: recurring domain wording obstructs a named reader use. Identify the domain object or relation, the relied claim, and its use boundary in the affected DPF subject pattern; use E.10.ARCH for the recovery method and F.19 for the final plain technical rewrite. Conceptual synthesis and wording restoration remain separate: restoration preserves the meaning of an identified claim in the current DPF edition; it neither establishes nor revises that claim.

Write the resulting domain entry beside the DPF claim whose wording it restores. The entry identifies the recurring wording, the relied DPF claim, the DPF edition in which that claim is current, the recovered domain object or relation, the surviving reader use, the repaired wording, the blocked overread, and the condition that reopens either the entry or its relied claim. Do not copy the domain trigger into the FPF-wide applicability table. One isolated wording failure stays a local E.10 repair or a direct rewrite under the DPF claim's defining or constraining rule.

Identify a separate DPF-local profile only when several entries are consumed together by a named maintained use. Identify the profile as a claim-bearing episteme, state its receiving use and edition, and keep the constituent entries independently revisable; if a table publishes the profile, keep the table as its publication form. Existing local profiles remain local applications of this method. A DPF without a demonstrated recurring wording problem creates neither an entry nor a no-profile result.

If the attempted repair exposes a missing or unstable domain distinction, stop the wording route. Return to the DPF source, conceptual-synthesis, or content decision that can establish the missing claim; only then resume the 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 and intended candidates explicit until their defining or testing rules and exact relations or claims distinguish the uses or rule one out; shared wording does not license premature single-referent closure.
Bypass restoration when the subject and predicate are clear. Once the object, relation, assertion, description, publication, representation, work, result, structure, or architecture claim has a clear predicate and ClaimGraph, state or use that subject claim under its defining or constraining rule and stop the restoration detour. A pattern locator establishes no performer, responsibility, Method, MethodDescription, Work, assignment, or F.6 attribution. If actual authoring or repair Work is part of the claim, recover each exact performer through A.13 and let A.15.1 independently admit the dated Work. Add A.2.1 and F.6 only when this architecture account also consumes precise assignment-bound attribution; missing or failed F.6 leaves the Work intact. State Method, MethodDescription, and responsibility claims separately only when they matter.
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 item under the rule that defines its identity or use, and cite the pattern containing that rule. 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 predicates; 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 the defining or testing rule selected for the claim. 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 claim-rule 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 locally used U.Method; a U.MethodDescription episteme that describes that method; exact method-side relations and, only when a named use depends on their organization, the A.22-selected structure locally designated MethodRelationStructure; a mechanism or formal-substrate declaration; a mathematical-lens or other representation use; a U.WorkPlan; dated U.Work; an actual transformation; a production, inception, or completion claim; a changed-referent relation; a measurement, evaluation, choice, or decision result; an evidence, source, gate, publication, temporal, delivery, or acceptance relation; a selected structure; an obtaining C.30 ArchitectureRelation with its actual holon and structure participants; a separate ArchitectureClaim episteme; an architecture-description episteme only when that use is current; or another object named under its defining or testing rule. A.15 keeps system-role classification, assignment, Method, MethodDescription, WorkPlan, dated Work, and F.6 attribution separate. Unresolved role wording still uses E.10.ROLE.

When wording concerns a relation among methods or method families, recover the relation itself—for example, serial or parallel composition, guarded choice, iteration, refinement, substitution, decomposition, parameterization, family membership, selection, or fallback. Use A.3.1, G.5, or the rule that defines or constrains that relation. If a named use depends on how several such relations are organized, use A.22's criterion to select the structure and call it MethodRelationStructure locally; that name creates neither a U-kind nor another relation. A graph, algebra, tuple, or other notation is a C.29 representation or mathematical-lens use of the structure, not itself a Method. A claim-bearing episteme that describes the relation remains separate from it. U.MethodDescription still means an episteme that describes one Method; it is not a method family, relation structure, mechanism, plan, Work occurrence, transformation, result, architecture, or representation. Do not classify one value as both U.Method and U.Mechanism unless the defining rules for those two kinds independently admit both claims.

The authoring note may record the affected entity; the exact source or practice boundary, effective scheme, model-use structure, situation, scope, or frame when it changes the claim; a change or maintained-condition claim; any current state or delta predicate; and the exact objects and relations exposed by the wording together with the rules that define or constrain them. 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 relation or claim, architecture description, representation, publication relation, or temporal relation, use its defining or testing rule and keep each identity separate; the pattern ID remains a locator.

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 pattern for a dated Work occurrence; A.3.4.P and the direct transformation pattern for an actual transformation participant; A.15.PROD, the measurement or evaluation pattern, or the delivery or acceptance pattern 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 rule is missing-information; an absent relation kind and defining ClaimGraph or declaration for the health-effect claim between Patient_8472 and HE-8472 is missing-governor. Only the last names an affected receiving use and a needed future relation rule or declaration. 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 a participant meaning stated in a direct-relation rule, keep it local unless E.24 supplies durable identity, action-facing gain, and the exact relation involved. 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 pattern containing the kind's defining rule must precede current citation.

Applicability table

Semantic area and ontological neighborhood	First rule or recovery entry	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 ClaimGraph or declaration that defines the exact predicate; `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; use of the predicate's defining or testing rule; `A.6.RCD` result; or fail-closed Plain disposition.
Bare claim-bearing role; primary recoverable use may be an exact local system-role kind, one direct assignment occurrence, direct-relation participation, a declaration place, representation position, another object or relation, episteme use, or ordinary wording	`E.10.ROLE` unless the object and the rule defining or testing it are already clear	Bare role, title-like `role`, `plays a role`, `role in`, or close wording on which an FPF claim relies	Ordinary sentence naming the recognizable object and action or relation; one exact selected object or relation; the rule defining, constraining, or testing it; no default system-role reading; no fixed expansion	Local rewrite, direct use of the recovered rule, ordinary or quoted non-use, exact `missing-governor`, blocker, or stop.
Learning-word recovery; primary recoverable use is an exact changed subject, Work, Method, result, evidence claim, or receiving use hidden by one learning-family expression	`E.10.LRN` unless the direct claim and its governing rule are already clear	learn, learning, learned, taught, trained, learning progress, learned representation, and close claim-bearing wording	Participants; changed subject; Work and Method only when current; direct result; evidence and blocked transfer; receiving use; direct governing pattern; and split boundary for unlike claims	Repaired or split direct claims; direct pattern use; ordinary or quoted non-use; exact missing-information or missing-governor result; blocker; or stop. No generic Learning ontology, result, progress scale, or UTS row.
Relation, declaration, interface, assignment, or slot wording; the sentence may hide a direct relation, reusable declaration, interface claim, bundle of boundary claims, assignment, port, another governed object or claim that belongs under a neighboring rule, or a source label that should remain reduced-use wording	`A.6.RSIR` until the direct relation, declaration, interface, or other governed object is clear; then use the rule that defines, constrains, or tests the recovered claim	Wording that may denote a relation, its reusable declaration, an interface or representation position, or a neighboring governed object—for example relation, signature, interface, assignment, enactment, slot, field, parameter, argument, endpoint, port, API, protocol, connector, capability, affordance, method, function, concern, or interest—plus the direct-relation, declaration, interface, operation, or representation branch recovered under `E.10.ROLE`.	Project concern; the governed object or claim at issue; its defining, constraining, or testing rule and pattern locator; A.6.5 `SlotSpec` only when a reusable declaration is needed; any source label to retain; the overread to block; and the stop condition.	`RSIRRepairNote` when the full note is needed; otherwise a direct rewrite, use of the recovered rule, reduced-use or quote-only source wording, a blocked-overread 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 its defining or testing rule is not already recovered; otherwise use that rule directly	Functional architecture, required transformation or effect, method, Work occurrence, direct subject effect, measurement-result episteme, evaluation result, `C.11` `ChoiceResult` or decision record, system-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 its defining or testing rule; 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 recovered relation'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` values only when reusable declaration is needed.	Short statement naming the exact object or claim and the rule used; direct predicate with actual participants when a relation is involved; `C.2.1` assertion only when claim identity must be preserved; occurrence distinction under the recovered relation's identity rule only when one obtaining episode must be distinguished; `FunctionFlowModuleAlignmentNote`; mathematical-lens, quality, characteristic, or `A.6.M` result; 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; use the rule for the recovered evaluation claim only when that 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, use of the recovered episteme, publication, source, or evaluation rule, or stop.
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 the ontic-description and publication-form boundary; use the recovered object's defining or testing rule directly when already known	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, rule and pattern locators, 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 use of the recovered rule; 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 the exact claim, not a generic admissibility object	Use the claim's defining or testing rule when recoverable. If `readiness` or `ready` still hides which governed value is meant, use `E.10.MOVE`; it returns to `A.19.SPR` only for a hidden bearer and state frame. Use `A.6.P` only when relation construction is hidden.	`admissible`, `lawful`, `legal`, `allowed`, `permitted`, `authorized`, `valid`, `pass`, `fail`, `ready`, `conformant`, `eligible`, and close compounds.	Exact object and claim, direct rule, and any material use boundary or reopen condition; for readiness, the recovered A.19.SPR state claim, A.2.5 assignment-state claim, A.15.5 work-entry result, A.21 gate decision, or another direct claim.	Direct use of the rule; wording repair only while the governed value remains hidden; quote-only cue; reduced-use cue; blocked-use disposition; or stop.
Method-like wording—for example, 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 Method or a separate method-side relation, description, mechanism, Work, transformation, result, structure, architecture, representation, or direct relation	`A.3.1` only while the method-side object or relation is hidden; `A.22` only when a named use depends on organization among several exact method-side relations; then use the rule that defines or constrains the recovered object; use `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 `U.Method`; exact method-side relations; an A.22-selected structure locally designated `MethodRelationStructure`; one `U.MethodDescription` episteme describing one Method; formal-substrate declaration; C.29 representation; mechanism; WorkPlan; dated Work; actual transformation; production, inception, or completion claim; measurement or evaluation result; delivery or acceptance claim; selected structure; architecture relation; architecture-description episteme; or an evidence, source, gate, choice, decision, or other direct relation. Identify each under its predicate and the ClaimGraph that defines or constrains it.	Short object-and-relation sentence under the recovered defining or constraining rule and practical guidance; one `U.Method`, exact method-side relations, optional `MethodRelationStructure`, 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; use the defining or testing rule directly when already recoverable; use `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 result family: short positive or governed-negative direct subject-relation sentence; exact A.6.1 application binding; exact local A.15.PROD or 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 result family.
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 defining or testing rule already closes the claim; otherwise use that rule directly	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: visible expression or artifact; exact current object, claim, or relation; 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 defining or testing rule, retained use, and stop.	`DeclarativeRepresentationRepair`; direct E.18, A.10, E.17, C.29, Method, MethodDescription, Work, gate, authority, or relation result; quote-only cue; reduced-use cue; blocked-use disposition; or stop.
Architecture and structure; primary recoverable use is a selected structure, obtaining `ArchitectureRelation`, `ArchitectureClaim` episteme, architecture-description use, structural view, or named C.30 subcase	`C.30.P`	Architecture-heavy or structure-heavy wording whose EntityOfConcern, relation, claim, or current use is not yet recoverable.	A.22 selection criterion and selected structure; C.30 `ArchitectureRelation` and separate `ArchitectureClaim`; C.30.ASV structural-view and structure-kind discipline; named C.30 subpattern rules; C.30.AD when full architecture-description use is current.	Architecture-structure repair note; repaired wording; selected structure; obtaining `ArchitectureRelation`; separate `ArchitectureClaim`; structural-view or architecture-description result when current; architecture question; source-return condition; 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` while the governed object, claim, or its defining rule is hidden; otherwise use that rule directly	Engineering, mathematical, publication, project, control, module, neural-network, or architecture prose uses a source label as if it named the FPF kind directly.	Source label; literal source wording; candidate primary EntityOfConcern; recovered FPF kind; recovered relation and claim-use; source-relation disposition; defining or testing rule and pattern locator; admissible use; non-use boundary; and any current adjacent rule from `C.30.P`, `C.30.LCA`, `A.6.M`, `C.30.TFS-REL`, `E.18`, `C.16.P`, `C.29`, `C.2.P`, gate, Work, or decision content.	`StratificationSourceLabelRepairNote`; direct use of the recovered rule; ordinary-prose demotion; quote-only; reduced-use; 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; use of the rule that defines or tests the recovered value; non-comparability; non-measurement; blocked-gate disposition; 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 rules named by value.	Quality-term repair note; quality-bundle or pattern-quality coordinate result; direct use of the recovered characterization or relation rule; relation or bridge split when current; blocked scalar, gate, or release overread; ordinary-prose demotion; or stop.
State-family hidden claim; primary recoverable use is an exact object with a state-like value or local finite field whose frame is hidden	`A.19.SPR`; for `readiness` or `ready`, use `E.10.MOVE` first unless the exact direct claim is already known	State, status, posture, stance, currentness, validity, stable, accepted, blocked, candidate, admissible, degraded, and readiness-like wording after E.10.MOVE has recovered a hidden bearer/state-frame case.	Exact object; claim or value; direct rule; and a predicate only when that rule defines or needs one.	Direct use of the recovered rule; A.19.SPR repair only while object or state frame remains hidden; 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 exact claim	Any trigger family whose recovered FPF kind, relation, claim-use, source-relation disposition, or admissible-use boundary is already recoverable by value.	The defining, constraining, or testing rule for that exact claim, plus its pattern locator and conformance fields.	Apply that rule directly; do not 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 hidden. After recovery, use C.30.P's architecture or structure rule, C.30.AD's architecture-description and source-return rule, C.30.ASV's structural-view adequacy rule, C.32's architecture synthesis or decision rule, or the exact rule for a current evidence, assurance, gate, Work, decision, publication, or currentness claim.

Direct known claim-rule use

If the governed object, exact direct relation, claim-bearing episteme, representation use, or claim kind and its defining or testing rule are recoverable by value, use that rule directly and cite the pattern containing it. Do not send 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 claims through a restoration pattern merely because a familiar trigger word appears. Use A.6.P.WMR only while the exact Work and Method boundary relation or exact non-assertability result remains hidden. Keep known-predicate failure, unavailable fact, and absent rule or declaration separately factually unsupported, missing-information, and missing-governor; only the last is a blocker that names the needed future relation rule or declaration.

Apply E.10.ROLE only when bare claim-bearing role still hides its object or relation. 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, system-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 and 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 subject pattern already carries the row without duplicating repair-only doctrine inside subject patterns.

Do not add a new realization pattern when an existing subject 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 subject pattern already contains the rule that defines, constrains, or tests the EntityOfConcern under repair, relation, claim, or field. Record the PatternID that locates that rule as subjectPatternLocator and state the rule's contribution.

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 subject-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 E.10.MOVE while readiness or ready still hides which governed value is meant; use A.19.SPR for state, status, posture, stance, currentness, or a readiness case returned by E.10.MOVE only while its exact object or state frame remains hidden;
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 current one-method U.MethodDescription, mechanism, plan, dated Work, transformation, result, structure, architecture, representation, or direct relation; then use that object's defining or testing rule;
use E.10.ROLE when bare claim-bearing role hides its work-facing or use-facing object; use A.6.RSIR when relation, signature, interface, assignment, enactment, slot, field, parameter, argument, endpoint, port, API, protocol, connector, capability, affordance, method, function, concern, or interest wording hides the current direct relation, declaration, interface, operation, representation position, or claim kind and no defining or testing rule 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 defining or testing rule 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;
for admissibility-like, legal, lawful, validity, pass-looking, fail-looking, readiness, conformance, or authority wording, use the recovered claim's defining or testing rule; use E.10.MOVE first while readiness-like wording still hides that claim, and use A.19.SPR only when a hidden state-family object or frame remains;

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, a subjectPatternLocator for the defining, constraining, or testing rule, and a realization pattern when one is needed.

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 exact mereology predicate 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 exact defining `ClaimGraph`. If it instead needs the installation act that established the condition, first identify a separate dated Work occurrence under A.15.1. Add an actual transformation under A.3.4 only when a current claim says that the installation changed a continuing referent, and state the exact direct relation between Work and transformation when that relation is also claimed. Neither object nor their coexistence is the parthood occurrence or supplies that relation.	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 subject and predicate are 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 predicate for dated Work; A.3.4.P plus the direct transformation predicate for an actual transformation participant; the exact production, measurement, evaluation, delivery, or acceptance predicate 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 established by that predicate; 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."	Use `C.30.P` to recover whether the diagram is publication form, structure view, architecture description, source relation, or ordinary source-finding cue; then state a C.30 or C.30.ASV subject assertion only after the selected architecture or structural-view use is recovered.	diagram-as-architecture; diagram-as-proof; diagram-as-gate.
"For PlantOps use U, selected structure S1 organizes holon H in the declared way; C.30 records the obtaining `ArchitectureRelation` and a separate `ArchitectureClaim` about it."	Direct `C.30`; no `C.30.P` unless another 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."	Use `C.30.STRAT` to treat `layers` as a source label until the recovered FPF kind, relation, claim-use, or source-relation disposition is clear: control-layer relation, neural-network block sequence, publication relation set, mathematical scale or coarse-graining relation, or ordinary source wording. Then state the recovered subject assertion under its defining or constraining rule.	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, state its exact A.10 assertion; if authorization or release is current, state the separate authority, gate, or release assertion under its defining rule. Use `C.2.P.DR` 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."	Use `A.3.1` to recover whether the wording denotes one exact method or a direct method-side relation. A current A.3.2 assertion obtains only when one exact episteme describes that Method. Formal substrate, C.29 representation, mechanism declaration or realization, Work, result, and quote-only wording remain separate subject assertions under their own defining or constraining rules.	algorithm-as-default-method; method-as-mechanism by vocabulary.
"This record is admissible."	Recover bearer, claim kind, source relation, value frame, admissible use, exact subject assertion, and its defining or constraining rule. Use `A.19.SPR` only if hidden state-family wording remains; otherwise state the exact evidence, gate, mechanism, temporal, authority, release, or source-relation assertion.	admissible-as-generic status; pass-looking word as gate.
"This score proves readiness."	Use `C.16.P` to recover characteristic, scale, value, score, threshold, and comparison reference set; state gate, evidence, and decision assertions separately under their own defining or constraining rules.	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."	Use `C.16.Q` to recover quality characterization or evaluative characterization, or state the exact characteristic, evaluation, relation, action, Work, or bridge assertion under the rule located through `C.16.P`, `C.16.Q`, `C.25`, or the pattern that defines or tests the recovered assertion.	quality-as-one scalar; quality-as-gate.
"The function improved maintainability."	Use `A.6.F` to recover the FPF kind, relation, or claim when hidden; then state the exact quality or maintainability assertion under the rule located through `C.16.P`, `C.16.Q`, `C.25`, or the pattern that defines or tests the recovered assertion.	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 the defining or constraining rule and practical guidance located through `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.	Recover one exact Method, each exact method-side relation, and an A.22-selected `MethodRelationStructure` only when a named use depends on their organization; recover a 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; then state the exact evidence, gate, authority, or release assertion under its own defining or constraining `ClaimGraph`.	Graph and provenance relations remain legitimate when they are not overread as routes, calls, permissions, or releases.
A candidate Systems Engineering DPF repeatedly encounters the guide term `целевая система`, while its subject pattern distinguishes the project system-of-interest from other transformed holons.	The system authoring the DPF cites that identified domain claim in a local entry, keeps the source term quoted where needed, and uses `F.19` to write the practitioner sentence. If the DPF has not yet settled which holon is at issue, the wording route stops and returns to the DPF content decision.	The example demonstrates placement and return; it does not establish a Systems Engineering claim in FPF or add the guide term to the shared trigger table.

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, the defining or testing rule and its PatternID locator, and the 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 description; the rule content located at `E.10.ARCH` states 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 recovered object, exact claim or use, exact subject assertion, `subjectPatternLocator`, 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 subject-pattern boundaries.
`CC-E10ARCH-4`	A new realization pattern is added only when no existing defining or constraining `ClaimGraph` and subject-pattern guidance supply the stable recovery shape without duplicating repair-only doctrine. Neither the locator nor that guidance establishes a `U.Method` or qualifying `U.MethodDescription`.
`CC-E10ARCH-5`	Each subject description keeps its primary `EntityOfConcern` and first useful move central and retains only thin first-use cues to precision restoration when wording is hidden. Generic guards about description and publication use stay in a named boundary section or in exact description/publication-use rule content; 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 rule-content split: `E.10` recognizes the wording-use row; the defining `ClaimGraph` located at `C.2.1` states episteme identity and the identified `EntityOfConcern` participant; A.6.5 rule content defines `EntityOfConcernSlot` only as a `SlotSpec` inside a reusable constitution `RelationSignature`; direct-reference `ClaimGraph` sources define or constrain `entityOfConcernRef`, `EntityOfConcernRef`, and related reference uses; `C.2.P` supplies the recovery rule and practical guidance for episteme, publication, source-wording, and source-relation wording; `F.18` settles durable heads and source-string decisions; `E.17.AUD.OOTD` rule content states publication-unit primary entity of concern; and every remaining claim or admissible-use boundary is a separate exact subject assertion. Neither declaration nor designation constitutes the participant, and selecting `C.2.P` establishes neither a `U.Method` nor a `U.MethodDescription`.
`CC-E10ARCH-6b`	State-family wording follows one path: E.10 recognizes it; E.10.MOVE first resolves ambiguous readiness-like wording; A.19.SPR repairs only a remaining hidden object or state frame; and the direct pattern states the recovered relation, assertion, result, decision, or field. A predicate appears only when that direct pattern defines or needs one.
`CC-E10ARCH-6c`	Stratification and source-label wording follows the selected distribution: `E.10` recognizes the wording-use row, `C.30.STRAT` supplies the recovery rule and practical guidance for recurring source-label repair, and exact subject assertions state 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. Selecting `C.30.STRAT` establishes no Method, MethodDescription, performer, or Work.
`CC-E10ARCH-6d`	Admissibility-like, legal, lawful, validity, pass-looking, fail-looking, readiness, conformance, and authority wording mints no generic admissibility or readiness object. E.10.MOVE resolves ambiguous readiness-like wording; A.19.SPR is used only for a remaining hidden object or state frame; otherwise use the claim's direct rule.
`CC-E10ARCH-6e`	Method-like wording may recover one `U.Method` or one or more exact method-side relations. Only when a named use depends on their organization should the practitioner use A.22's criterion to select a structure that may be locally designated `MethodRelationStructure`; a `U.MethodDescription` separately describes one admitted Method. Mechanism, plan, dated Work, transformation, production, inception, completion, result, delivery or acceptance, architecture relation, architecture description, and representation remain separate objects or relations under their defining or testing rules. One source label may expose several such values, but none gains dual `U.Method` and `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 defines or constrains 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: recover source-ontology labels only when they affect the governed object, direct relation kind, participant meaning, actual participant kind, declaration-local SlotSpec, assertion-side participant designation, exact use, admissible use, or selection of the claim's defining or testing rule; otherwise stable ordinary prose stays ordinary. Relation-shaped material follows the relation-use recovery rule, and `interface` is used only under a boundary, module-interface, signature, port, publication, or source-label disposition named by value.
`CC-E10ARCH-6h`	For bare claim-bearing role, use `E.10` to recognize the trigger and `E.10.ROLE` to recover the ordinary sentence and one exact object or relation. Use the defining rule located by the selected pattern. Use `A.6.RSIR` only while a direct-relation, declaration, interface, operation, representation, or other relation-signature-interface-assignment-slot branch remains hidden. Neither application mints generic `U.Interface`, universal Role, a standalone slot ontic, `U.Concern`, `U.Interest`, or episteme-role ontology.
`CC-E10ARCH-6i`	Work and Method boundary wording uses `C.2.P` first for an epistemic source side, bypasses to a clear defining or testing rule, and otherwise uses `A.6.P.WMR` for exactly one of its four result families. Use `F.18` to name 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, claim-bearing episteme, view, or defining or testing rule is hidden; it 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.
`CC-E10ARCH-11`	A DPF-local entry begins only from a demonstrated recurring wording problem and identifies the DPF claim, DPF edition, defining or constraining rule, and the PatternID that locates that rule. The entry stays beside the claim whose wording it restores; `F.19` supplies the final rewrite. A separate profile is a claim-bearing episteme with a named receiving use and edition, and exists only when several entries are maintained together; any table that publishes it remains a publication form. No domain trigger is copied into the FPF-wide table, and wording repair does not establish or revise domain doctrine.

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 defining or testing rule; 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 the exact C.29 or publication predicate, state the represented object and explicit correspondence, and test the direct relation predicate 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`; state every other current object and direct relation separately under its defining or testing rule.
Authoring row becomes a practitioner form	Engineers are required to complete an applicability row before using a clear rule.	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 concrete predicate and its rule are clear.
Classification or type-correct-designation fallback without repair	The text names a restoration pattern, generic result label, MethodDescription field, planned use, compatible type, or designation but leaves no exact governed object, direct relation, claim-bearing episteme, defining or testing rule, truthful WMR result family, or blocker.	Apply the recovered defining or testing rule 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`.
DPF entry promoted to FPF vocabulary	A domain trigger or its local repair is copied into the shared applicability table merely because one DPF uses it.	Keep the entry beside the DPF claim whose wording it restores; propose an FPF amendment only when the same participants, relation, failure, move, and use remain meaningful across domains.
DPF wording profile by default	A DPF creates a trigger registry, profile, table, or package-wide no-profile result before recurring wording or a maintained multi-entry use has been shown.	Repair one case locally; create entries only for demonstrated recurrence, identify a separate profile only for a named maintained multi-entry use, and keep any table that publishes it as a publication form.
Wording repair settles domain doctrine	An author changes a domain claim while presenting the work as lexical repair.	Stop and reopen the DPF source, conceptual-synthesis, or content decision; resume wording restoration only after the relied domain claim is current.
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 is different.	Recover the source ontology, governed object, exact direct relation, any declaration-local SlotSpec or assertion-side designation, and the rule that defines or tests the claim; keep the source word only when that rule 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 subject 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; use `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. DPF authors reuse that architecture without moving domain meanings or trigger lists into FPF.

Costs. Authors must decide whether the current case is local E.10, a subject 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

Recoverable source or practice line	Decision and effect in `E.10.ARCH`	Limit or reopen boundary
FPF August 2026 edition distribution: `E.10`, `E.10.ARCH`, `E.10.MOVE`, `E.4.DPF`, `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`, `F.19`, `E.8`, `E.19`, `E.11`, and `I.2`.	Adopt as the internal architecture basis. Keep local recognition in `E.10`, the shared recovery algorithm here, DPF-local entry in `E.4.DPF`, and each stable subject family in the named realization or subject pattern.	This internal distribution is not external SoTA evidence. Reopen it when a named pattern changes its contribution or the shared recovery split no longer fits.
FPF August 2026 `E.8` and `E.19` rules for pattern locality and the primary `EntityOfConcern`.	Adopt as the internal authoring and review basis. Keep subject-pattern references thin and keep copied trigger tables out of patterns whose practical concern is architecture, structure, characteristic, quality, evidence, gate, work, decision, state-family precision, or release.	These internal rules do not supply a terminology ontology or an external practice claim.
`E.10:18` external-practice row for Miles and Bechhofer (eds.), SKOS Simple Knowledge Organization System Reference, W3C Recommendation, 18 August 2009.	Adapt narrowly. Use SKOS for controlled-vocabulary publication, designations, labels, and label relations when those are the actual objects; use F.18 and the relevant subject pattern for reusable FPF names and claims.	This stable reference is not the current-best answer to every wording repair and does not define FPF kinds. Reject a central word list or controlled vocabulary as the universal solution.
FPF August 2026 subject-pattern coverage named in `E.10.ARCH:4` and `E.10.ARCH:14`.	Adopt as the applicability boundary. Use the existing pattern when it already defines, constrains, or tests the object, relation, claim, or local field being repaired.	Existing coverage does not prove that this architecture settles every wording-use case; reopen it 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 subject 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.4.DPF defines the DPF entry condition and the placement rule: each domain entry remains beside the DPF claim whose wording it restores; a separate local profile exists only for a named maintained multi-entry use, and any table that publishes it remains a publication form.
Use E.10 to recognize and close local wording issues or select the applicable row; use E.10.LRN only while claim-bearing learning wording hides the changed subject, Work, Method, result, evidence, or use; use E.10.ROLE for bare claim-bearing role, which has no default Tech reading.
E.10.ROLE provides the thin first entry from bare claim-bearing role. A.6.RSIR realizes first-level recovery for the narrower relation, signature, interface, assignment, declaration-slot, operation, and representation cluster only until the defining or testing rule for the recovered object is clear.
A.6.P realizes the shared algorithm for generic relation construction and retained relation specializations. An A.6.P.WMR application records exactly one result family for a current Work and Method boundary claim: 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 exact non-assertability as factually unsupported, missing-information, or missing-governor. Only the last names the affected receiving use and needed future relation rule or declaration. Use A.6.RCD only for the residual needed-claim derivation and relation-kind admission question after exact participants are known and no lighter current rule 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 defines one exact U.Method and the method-side relations within its scope. When a named use depends on organization among several such relations, use A.22's criterion to select the structure, which may be locally designated MethodRelationStructure. Enter through the method-like wording row only while the actual object or relation remains hidden.
A.3.2 defines membership for a U.MethodDescription episteme that describes one exact U.Method; that membership absorbs no mechanism, plan, Work occurrence, transformation, result, structure, architecture, or representation.
A.6.0 defines reusable signature identity and A.6.5 defines SlotSpec declarations; C.29 defines representation use and explicit correspondence for tuples, arguments, edges, diagrams, and similar forms; A.6.1 defines operation application and E.20 defines governing-definition assignment. An exact onticSlotRelation exists only after its E.24 durable ontic settlement is current.
Use A.15.2 for planned work, A.15.1 for dated Work, and A.10 for evidence or provenance relations that method-like or path-like wording may otherwise hide; use A.15.PROD for the local production-work, entity-identity-inception, or production-completion claim when that exact WMR result family is current.
E.18 defines graph paths, path slices, flow valuations, and graph relations over a 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 the recovered claim is handled under its defining or testing rule.
C.16.P realizes characteristic and scale wording recovery.
C.16.Q realizes quality characterization and evaluative characterization wording recovery.
E.10.MOVE resolves ambiguous readiness-like wording and exits to the direct pattern.
A.19.SPR realizes state-family wording recovery only while the exact object, state frame, value, or direct rule remains hidden.
Use F.18 for durable reusable naming after the kind under repair or relation is known.
F.19 supplies phrase-level ontology-first plain technical rewriting after the kind under repair is recovered or while proving it is still hidden.
E.8 states the pattern-form and placement rules.
E.19 checks distribution preservation during review and refresh.
E.11 states the entry-distribution rules for broad or old-term cases across README scenarios, ToC query cues, local Problem frames, and I.2 expanded entry-disambiguation cases.

E.10.ARCH:End

Last Updated: 2026-08-30 — upstream FPF commit e400eab3 (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

#DPF-local application

#Shared recovery algorithm

#Method, work, and P2W claim-rule constellation in wording restoration

#Applicability table

#Direct known claim-rule use

#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

DPF-local application

Shared recovery algorithm

Method, work, and P2W claim-rule constellation in wording restoration

Applicability table

Direct known claim-rule use

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