Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:20:20 UTC

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

The author SHALL emit typed RSCR triggers through the RSCR subject pattern when a MIP-run changes any of the following:

  • 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

The author 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.

Trigger identifiers. Trigger kind identifiers (e.g., RSCRTriggerKindId) SHALL be selected from the RSCR trigger catalogue governed by G.Core. Authors SHALL NOT create ad hoc trigger kinds (“reason kinds”) in individual patterns or modules.

Recommended manifest contents. The MIP-run manifest SHOULD list emitted trigger types and changes to the regression envelope as checkable items.