Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

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:35:20 UTC

C.2.P:11.1 - Relevant FPF Patterns

The current FPF corpus already has patterns that contribute to this discipline:

  • E.10 supplies word/head, morphology, register, and naming cues and routes within the connected F.19 reading.
  • E.10.D2 gives the “thing vs words vs rules” discipline and the carrier humility rule.
  • F.18 gives the local-first naming protocol: governed value and kind; the pattern and contribution that define or constrain them; by-value scheme; local-sense claim; intended use; candidate comparison; and any separately obtaining relation.
  • A.6.P gives the relation-precision restoration method: restore generic head kind, build candidate sets for endpoint kinds and relation kinds, select kind-explicit slots and qualifiers, then allow guardrailed wording.
  • C.2.1 gives episteme identity through exact claim content, EntityOfConcern, and effective ReferenceScheme and keeps empirical grounding and edition continuity as distinct direct relations.
  • A.7 keeps EntityOfConcern, Description episteme, and publication carrier distinct.
  • E.17.0 tests view conformance to a viewpoint; E.17 governs reader-facing publication forms for an accepted account; E.24.PUB distinguishes publication occurrence, form, and carrier.
  • A.15.4 shows how to keep an encountered publication, display, or low-articulation cue distinct from the project-side FPF kind and reference used for work or reliance.
  • A.16 coordinates language-state moves; A.16.0 supplies an optional trajectory account when their history matters; A.19 defines the CharacteristicSpace and its reusable predicates; B.2.5 governs supervisor-subholon feedback; C.27 distinguishes state or rate readings from intervention-sensitive temporal claims; A.3.3 defines the reusable state-space and transition-law episteme.
  • E.19 already treats terminology and sentence-level precision restoration as required review checks, not editorial polish.
  • A.6.A carries action-invitation discipline when a publication, representation, or cue invites an action without itself becoming authority, evidence, gate passage, or work completion.
  • C.11 carries decision-making and decision-record discipline when the question under repair is a decision rather than generic action.
  • A.15 and A.15.4 split system-role kind and assignment, Method, WorkPlan, and actual-Work alignment from appearance-based reliance repair; do not use A.15 as a universal repair for episteme-publication wording.
  • E.9 is the campaign DRR pattern for campaign-level content decisions; E.11 is only for entry-discoverability situations and must not organize an episteme and publication repair by default.

These internal FPF patterns remain primary:

Claim needRelevant FPF pattern(s)Alignment with C.2.PAdoption result
Head-kind disciplineE.10Use head-kind recovery before accepting a phrase.Adopt.
Stable namingF.18Run a name card when a reusable head is being minted.Adopt.
Relation precisionA.6.PRecover relation kind, endpoints, slots, qualifiers, and scope when a relation or use-boundary claim is current.Adopt.
Carrier and EntityOfConcern-description humilityA.7Keep EntityOfConcern, Description episteme, and carrier apart before treating a publication as evidence, work, gate, or authority.Adopt.
Episteme and publication ontologyC.2.1, E.17.0, E.17, MVPK, E.24.PUBSeparate episteme, publication, view, generic publication face, MVPK face under E.17 constraints, publication unit, carrier, and rendering.Adopt.
Project-side downstream useA.6.A, A.10, A.15, A.15.4, B.3, A.20, A.21, C.11When a publication, display, cue, or explanation is treated as evidence, gate, decision, work permission, method, assurance, or engineering justification, name the applicable FPF pattern and the project-side FPF kind and reference.Adopt.

This reduced external-practice set changes the Solution in one practical way: epistemic precision restoration cannot close merely because the replacement sounds cleaner. The FPF kind, relation, declared use boundary, and any needed pattern application must be recoverable by value; otherwise the wording is blocked or becomes a candidate for a separate FPF-kind decision.