fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 88989–89020

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:30:20 UTC

E.10.ARCH:2.2 - Ontic-Level and Facet-Level Restoration Distribution

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. After selection, the recovered object’s rule defines the content and its pattern ID locates that rule.

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. Return the corrected or split claims to their direct subject patterns.

For claim-bearing development, develop, evolution, evolve, progress, growth, maturation, adaptation, or lineage wording, use E.10.DEV only while the changed or represented subject, needed continuity or membership, posture, direction or value claim, direct owner, or receiving use is hidden. Use E.10.MOVE afterward only when a separately relied-on trajectory, route, path, order, posture, or representation remains ambiguous. 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.