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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:15:10 UTC

A.15.8:4.4 - Persist only the account another use needs

When another use must retain, compare, audit, or rely on the result, identify one or more C.2.1 account epistemes explicitly.

  • An actual-branch account selects the exact U.Work occurrence as its one truthful EntityOfConcern.
  • A prospective-branch account selects the exact present U.WorkPlan as its one truthful EntityOfConcern. Its ClaimGraph may designate the declaration-local intended-performance content but does not turn that designator into an entity.
  • The ClaimGraph may also designate independently governed actual or intended performers, supports, state bearers, exact relation claims, and the direct governor’s result. It may record the ordinary A.6.RCD blocker factually unsupported, missing-information, or missing-governor only under that pattern’s three-way split; these phrases are not new kinds or relation values. Probe observations, uncertainty, and the repair or stop remain separate claim content.
  • The effective U.ReferenceScheme always supplies the designation and interpretation rules needed by those claims and adds only the measurement, comparison, or evaluation rules actually used. Any actual measurement, comparison, or evaluation occurrence remains under its direct pattern.
  • If one focus cannot truthfully carry the combined claims, keep claims local or use several epistemes. Do not invent a plural focus.

The account is not the world-side configuration, performed Work, WorkPlan, carrier, evidence, or merely possible future performance.