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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:05:13 UTC

C.2.P:0 - Use this when

Use C.2.P only when one unresolved distinction still prevents the reader from selecting or safely using the direct pattern. The unresolved point must concern a source expression, claim-bearing episteme, publication, publication unit, view, carrier relation, source-to-use relation, or use disposition.

Recognizable situation. A sentence is readable, but it leaves the reader unable to tell whether it refers to claim content, a publication or bounded unit, a carrier or display, a source-bearing relation, or a project-side use of one of those objects.

First useful move.

  1. Say what the sentence is doing: defining, claiming, instructing, comparing, locating a source, describing a publication, or supporting a project use.
  2. Recover the one unresolved episteme, publication, source-to-use, carrier, or use-disposition distinction.
  3. Rewrite the sentence, or hand the remaining claim to the exact pattern that defines, constrains, or tests it. Then stop.

Not this pattern when. If the exact receiving pattern and its current field are already recoverable, apply that pattern directly. A clear ordinary phrase needs no C.2.P record. Use A.6.P for a relation problem whose publication or source-expression side is already clear, F.18 for a stable reusable name, A.7 for EntityOfConcern-description-carrier separation, E.17 for reader-facing publication of an accepted account, and E.24.PUB for publication-occurrence, form, or carrier distinctions.

Smallest outputs.

  • Direct repair: the repaired sentence plus one plain reason or non-use boundary. No record.
  • Compact row: the exact sentence, its function, one recovered kind or relation, the selected wording or disposition, and the reader’s remaining use.
  • Full check: only when several recovery fields interact, a source-to-FPF use is contested, or a reusable ontological or naming decision is being made.
  • Non-use result: reduced-use cue, blocked use, incomplete rewrite, or not triggered.

Changing an FPF pattern is not by itself a reason to use the full check. Use the cheapest product that preserves the live distinction.

Source-expression boundary. External or ordinary prose may be clarified without forcing all of its vocabulary into FPF. If no FPF-governed use is recoverable, keep the phrase as source-local wording, a source-finding cue, or a blocked claim-bearing use.

Source-to-use continuity. Do not close a repair merely by replacing the word source. Name the source expression or selected source episteme, the publication occurrence only when availability matters, the relation or path that carries it into the current use, the permitted use, and the condition that requires return to the source. Keep physical raw material with its constituent, resource-use, supply, transfer, or transformation relation.

Ordinary-language survival. Words such as source, view, support, route, and display may stay ordinary when they make no FPF kind, relation, authority, evidence, gate, work, decision, or reliance claim. Repair by sentence function and consequence, not by trigger word.

What this buys. The practitioner recovers the one distinction that matters without building a second ontology or a second review procedure. The final wording still tells a cold reader what to do and where to stop.