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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:45:04 UTC

E.17.AUD:4.2 - Publication-unit stability vs whole-unit requirement

Light ordinary output. The ordinary output is one repair choice, not a dossier:

  • stable for current use: the four-part interpretation is explicit enough and none of the neighboring questions named above is live;
  • local lexical-head repair: apply E.17.AUD.LHR to the overloaded head;
  • whole-unit stabilization: apply E.17.AUD.OOTD to the unit;
  • bounded comparison: if the unit is stable, apply E.17.ID.CR;
  • leave publication-unit stability: the live question concerns work, work planning, decision, gate, evidence, explanation, reliance, carrier or front-end work, or another claim that this pattern does not test; apply the relevant pattern and name the exact project object or record.

After choosing the repair, apply E.17.AUD.LHR for one local head, E.17.AUD.OOTD for whole-unit stabilization, E.17.ID.CR for bounded comparison, or the specific neighboring pattern and project record needed by a claim outside publication-unit stability.

Do not repeat or replace the narrower whole-unit check in PublicationUnit Primary-Subject Discipline: can this one unit still keep one stable primary subject, one carried publication move, and one outside boundary to work, work planning, decision, gate, or reliance claim?