E.10.ARCH:4 - Applicability table
Use this reference table to select or author a shared recovery rule for the unresolved question. Apply Required recovery apparatus to the current branch under the receiver-needed rule in section 3, step 4. The trigger and product columns list alternatives; they do not require every listed object or result in one repair.
| 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 any transfer boundary needed by the 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. |
| Interest-or-curiosity recovery; wording hides a participant, engagement, informational contribution or prospective use | E.10.INT when the ambiguity changes the work | interest, interesting, interested, curious, curiosity, or a relied-on appeal to a Goldilocks region | Participant and contribution; combined meanings where needed; model or comparison only when the action depends on it | Clarified claim and continuation through the applicable inquiry, learning, exploration, decision or field method; ordinary wording when already sufficient. |
| Development or evolution wording recovery; primary recoverable use is an exact changed or represented subject, continuity or membership basis, posture, direction or value claim, direct owner, or receiving use hidden by one development- or evolution-family expression | E.10.DEV unless the direct claim and its governing rule are already clear; use E.10.MOVE afterward only for an independent trajectory or path ambiguity | development, develop, evolution, evolve, progress, growth, maturation, adaptation, lineage, development trajectory, and close claim-bearing wording | Changed or represented subject; needed continuity or membership; separation of Work, Method, plan, result, evidence, and representation; posture; any declared direction or value basis; direct owner; receiving use; one-pass overlap stop; and an optional grounded non-use boundary only when F.19 requires it | Repaired direct claim; direct pattern use; ordinary or quoted non-use; exact missing information or architecture gap; blocker; or stop. If the repaired sentence separately exposes known participants but lacks a direct-relation governor, exit to A.6.P or A.6.P.WMR; only that relation-recovery branch may return missing-governor. No generic Development kind, Evolution kind, lifecycle, stage scale, programme, evidence rule, population ontology, or DevelopmentTrajectory kind. |
| 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; and the stop condition. A grounded non-use boundary appears only when it changes the receiving use. | RSIRRepairNote when the full note is needed; otherwise a direct rewrite, use of the recovered rule, reduced-use or quote-only source wording, a grounded non-use disposition, or stop. |
Function-like wording; primary recoverable use is an exact governed object or claim hidden by function, functional, functionality, effect, or similar wording | A.6.F first when the exact object, claim, or 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 receiving use must preserve the identity of that affirmative, negative, or modal claim; 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 current source expression, claim-bearing episteme, EntityOfConcern, publication or source relation, project-side kind, sentence function, and evaluation claim needed to state the exact use; optional fields appear only when current. | Local rewrite, use of the recovered episteme, publication, source, or evaluation rule, grounded non-use disposition, 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, 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; grounded non-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; grounded non-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; grounded non-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. | Visible expression or artifact; exact current object, claim, or relation; representation use or explicit correspondence, or none; defining or testing rule; retained use; and stop. Add further declaration, occurrence, designation, reference, publication, representation, or grounded non-use detail only when a named receiving use needs it. | DeclarativeRepresentationRepair; direct E.18, A.10, E.17, C.29, Method, MethodDescription, Work, gate, authority, or relation result; quote-only cue; grounded non-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; reader use; and any adjacent rule needed by the current claim. | StratificationSourceLabelRepairNote; direct use of the recovered rule; ordinary-prose demotion; quote-only; grounded non-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; a grounded comparability, measurement, or gate boundary when it changes use; ordinary-prose demotion; or stop. |
| Quality characterization and evaluative characterization; primary recoverable use is quality characterization, a single Characteristic, a structured Q-bundle, 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 selection of one Characteristic or, only when several typed contributors jointly determine the claim or action, a structured Q-bundle, E.21 pattern-quality coordinates, and characterization or relation rules named by value. | Quality-term repair note; single-Characteristic, structured quality-bundle or pattern-quality coordinate result; direct use of the recovered characterization or relation rule; relation or bridge split when current; a grounded scalar, gate, or release boundary when it changes use; 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; grounded non-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, with its pattern locator; recover conformance fields only when the receiving use needs them. | 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.