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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:30:10 UTC

E.20:4.10 - Step 10: RSCR triggers + regression envelope

A MIP-run that changes any of:

  • mechanism signatures,
  • suite membership/protocols,
  • planned baseline pins,
  • shared operation-member vocabulary or declaration-local operation, argument, or result designators,
  • terminology/alias docking that changes citeable tokens,
  • or other reference loci

SHALL emit typed RSCR triggers via the RSCR subject pattern and SHALL extend the regression envelope over the affected uses:

  • reference resolution for changed citeable references;
  • membership set semantics and protocol closure when a suite changes;
  • guard/gate separation when that boundary changes; and
  • the P2W planning-to-work boundary when planned-baseline content changes.

Guard (normative). Trigger kind identifiers (e.g., RSCRTriggerKindId) SHALL be selected from the RSCR trigger catalogue governed by G.Core. A MIP-run SHALL NOT mint ad hoc trigger kinds (“reason kinds”) scattered in arbitrary patterns/modules.

Manifest hook (recommended). The MIP-run manifest SHOULD list emitted trigger types and the regression envelope deltas as checkable items.