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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:10:10 UTC

E.10.ARCH:0 - Use This When

Use this pattern when a recurring FPF-governed wording-use problem survives the normal F.19 reading and compact E.10 routing because the wording still hides a stable primary-EntityOfConcern use field set, a stable recovery shape, and a useful reader use.

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. F.19 repairs the normal span, E.10 locates the unresolved FPF use, and E.10.ARCH supplies shared ontological recovery only for what remains. State each recovered claim under its defining or constraining rule; identify its exact ClaimGraph only when the receiving use depends on that identity.

Use it especially when several subject patterns repeat the same first-stage wording recovery before reaching their own invariants. Locate the unresolved wording use through E.10:0.2; section 4 keeps the detailed applicability rows for the selected recovery question.

Failure shape. Repeated local contrasts scatter the same wording repair across subject patterns. The reader cannot locate one stable recovery rule or a useful first move.

Architecture gain. F.19 carries the common semantic and pragmatic repair; E.10 supplies compact cues and routing; E.10.ARCH selects shared ontological recovery only when the object or relation remains unresolved; the defining, constraining, or testing rule then supplies the exact subject assertion and first useful move. Cite the PatternID only to locate that rule.

First useful move. Decide whether F.19 and compact E.10 routing can close the wording, whether the recovered object or claim already has a defining, constraining, or testing rule, or whether one shared applicability row is needed with stable semanticAreaBaseConcept, semanticArea, semanticAreaSenseFamily, ontologicalNeighborhood, recovery apparatus, and reader use.

WordingApplicable resultGrounded distinction in this near-miss
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.”The worked formula’s argument place and the value it represents.

Not this pattern when.

  • If a sentence is repaired locally under F.19 with compact E.10 routing, 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 wording problem is phrase-level apparatus around an already recoverable kind, use F.19 rather than creating a new wording-use restoration row.