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

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:7 - Subject-pattern thin-pointer rule

Subject patterns keep the minimum local first-use cues needed to resolve independent hidden questions about the EntityOfConcern, relation, claim, or field, then name the selected precision-restoration 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. Illustrative cases:

  • Use E.10.ROLE while bare claim-bearing role hides its work-facing or use-facing object; return to the object’s rule once it is clear.
  • Use C.30.STRAT while a stratification source label hides the FPF kind, relation, or claim-use; return the recovered claim to its defining or testing rule.
  • Use A.6.P.WMR only while an exact Method or Work boundary relation remains hidden after generic relation recovery. Use C.2.P first for an epistemic source side and bypass restoration when the direct rule is clear.

The full routing conditions remain in E.10:0.2a and the applicability table in section 4. A subject pattern keeps only the pointer needed for its current ambiguity.