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

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

E.10:0.2c.8 - record

Use record only when an FPF pattern or project practice defines the record kind and relation. The nearby wording says which FPF kind the record instantiates or records, for example:

  • an A.10 descriptive evidence-provenance account for a named claim, citing independently established relations;
  • A.21 GateDecisionResult or DecisionLogRef;
  • A.20 constraint or adjudication decision record;
  • C.11 ChoiceResult or decision record;
  • A.15 U.WorkPlan, one A.15.1 dated Work occurrence admitted under U.Work, or a separately identified claim-bearing episteme about that occurrence; use a record-kind name only when its exact kind and defining record rule are recoverable;
  • A.2.8 U.Commitment, exact A.2.8.PER permission result, or A.2.9 SpeechAct publication;
  • a separately identified assignment-assertion or occurrence-description episteme that designates one exact RA : U.SystemRoleAssignment, or a status-register entry under its named status pattern; neither record is the world-side assignment occurrence;
  • E.19 review run record or another named review record whose review target and review relation are explicit;
  • process run record in process documents.

Do not let record mean “any file that remembers something”, “the missing source”, or “the thing to create when support is absent”. If a named support relation cannot be asserted because a required actual participant or value is absent, name that exact missing participant or value. If a reusable declaration is incomplete, name its missing SlotSpec or other missing declaration content and repair that declaration. If a receiving assertion or relation-occurrence-description episteme lacks a participant designation, name the missing designation under that episteme. If a U.WorkPlan lacks a planned participant designation or planned value, name that missing plan content under the WorkPlan. Create a prospective repair request, future decision request, prospective work-plan entry, or explicit missing-source-relation note as applicable; none backdates support, establishes actual participation, or makes the direct relation obtain.