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 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:20:03 UTC

B.3.5:9.4 - Author’s working moves (micro‑playbook, notation‑free)

M‑1. State the relation in Working‑Model form (e.g., “Impeller ComponentOf Pump”). M‑2. If a publication choice or named current requirement elects this profile, pick validationMode; otherwise keep the direct relation claim and stop:

  • For a permitted exploratory claim, choose postulate and state scope plus challenge cues.
  • For a permitted conclusion from known statements, choose inferential and list the short argument.
  • For structural parthood covered by the profile, choose axiomatic and link the applicable current construction account.
  • For collection belonging covered by the profile, choose axiomatic and link one current C.13 set trace that reports the already established relation under the collection’s own rule.

M‑3. Add tv:AliasOf only when a named direct relation principle helps reviewers recognize the intended reading; do not alias the relation to a constructor result. M‑4. If assembly uses two parallel lines, state the actual Method/Work and temporal facts. Add any independently obtaining part relation under its own rule; parallelism alone does not establish it. M‑5. Stop when the selected readable relation and remaining non-use boundary are clear and, if this profile is elected, its validation mode and required current support are recoverable without guessing.