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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 10:17:34 UTC · last check 2026-10-03 10:20:08 UTC

C.2.P:2 - Problem

Without an epistemic precision-restoration discipline for episteme-publication-heavy wording:

  1. broad publication words hide which field family is current: episteme or view, publication form or face, bounded publication unit, carrier relation, named document use, review-state use, or project-side FPF reference;
  2. FPF pattern-application claims and project-side fields for work occurrence, work plan, decision, action invitation, method, record, carrier relation, or front-end relation get mixed in one sentence;
  3. slash lists and heterogeneous rows become false group kinds;
  4. unclear source meaning is guessed into FPF-governed wording rather than blocked or assigned to an accepted FPF extension;
  5. authors copy the same loose wording into DRRs, patterns, source-relation notes, source-ref target notes, or project texts.