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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 14:45:10 UTC

C.16.Q:11a - Refresh and reopen conditions

Reopen or narrow C.16.Q when any of these current-pattern-language conditions becomes live:

  • a recurring quality or evaluative family appears that is not covered by the current QualitySense starter set and cannot use an existing endpoint form;
  • an endpoint pattern can now handle a class of uses that currently require transitional qualityTermAscription(...);
  • A.7, C.2.P, C.2.1, or bridge-policy vocabulary changes the admissible lane, EntityOfConcern, publication-face, carrier, or ReferencePlane wording used by this pattern;
  • current best-known practice changes a QualitySense, normal-form boundary, action-invitation boundary, scale-legality boundary, or source-use and currentness row used in C.16.Q:11;
  • README, ToC, E.11, retrieval, or local Problem-frame first-entry cues change for quality, characteristic, action-invitation, architecture-description, selector, or explanation wording;
  • other patterns begin copying quality trigger lists, QualitySense rows, or transitional repair-form slots that belong in this first-stage quality-term precision-restoration pattern.

The refresh action is to remove, narrow, or redirect the affected row or exit. Do not preserve a stale QualitySense, endpoint exit, lane wording, or source row as historical compatibility text.