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

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 05:55:15 UTC

A.6.H:4.6 - Use wording as a cue, not as ontology

The following recurring expressions are useful review cues:

  • whole, entire, integrated, coherent, holistic — ask whether there is an actual candidate whole, a measurement or assurance claim, or only rhetoric;
  • part, piece, component, module, element, subsystem, includes, contains, comprises — recover the object and direct relation rather than accepting the noun;
  • phase, version, revision, edition, lifecycle — apply the direct identity pattern before any history label;
  • complete, turnkey, end-to-end, fully specified — recover the exact coverage or completion claim;
  • pipeline, workflow, process, step, stage — distinguish Method, MethodDescription, WorkPlan, performed Work, order relation, and publication representation;
  • collection, group, team, set — distinguish who or what belongs under the collection’s own rule, an acting system, system-role assignments, and a selected collection structure;
  • context, environment, discipline as a whole — name the actual bounded context, episteme family, community, organization, or other subject before making a boundary or nesting claim.

When a cue occurs inside a defined term of art, retain the definition and its PatternID locator when needed. Open A.6.H only if the sentence also makes an unresolved whole, part, structure, coverage, or completion claim.