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

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:00:10 UTC

A.16.0:4.3 - Use threshold and core trajectory record

A single local A.16 move note is sufficient when no load-bearing branch, loss, or supersession structure needs publication and no actual responsibility handoff depends on upstream history. An existing version history can also supply the answer when the needed source-use, continuity and loss facts are already recoverable there; the form does not require copying them into another document.

Use the LanguageStateMoveTrajectory account form when at least one of the following changes the receiving use:

  • derivation, supersession, fork, merge, or retirement structure;
  • multi-step loss notes or reopen conditions that would be hidden by a compressed move note;
  • an actual responsibility handoff whose legitimacy or interpretation depends on upstream history;
  • bridge or viewpoint entry that depends on upstream route, loss, or lineage structure.

An account using this form identifies its own subject, claim content and effective ReferenceScheme. It makes the following history content explicit to the extent needed by the selected use:

  • the current selected episteme edition;
  • predecessor, sibling, or ancestor editions when the current reading depends on lineage;
  • the lineage link kind (derivedFrom, supersedes, forkedFrom, mergedFrom, retiredWithSuccessor, retiredWithoutSuccessor, or another explicitly typed link);
  • the current position claim and any load-bearing predecessor position claims;
  • the typed move or move sequence;
  • the publication form and, when availability matters, the publication occurrence;
  • the MVPK face only when rendering matters;
  • the next question or use, the applicable pattern, and its concrete contribution;
  • when an actual responsibility handoff is load-bearing, the separate participants, relation, object or action, scope, interval, and instituting-act references required by A.16.0:4.6;
  • the grounds or witnesses and still-live rivals needed to justify the entries, with any loss note, reopen condition, branch-specific authority note or bridge-sensitive note that matters.