G.Core:9 - Consequences

Preface node heading:g-core-9-consequences:136043

What this page is

This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

Methodology

Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

Content

  • Positive: Part‑G patterns cite G.Core to find the governing definitions of shared invariants; refactors become safer and easier to audit.
  • Positive: RSCR becomes reason-code driven (typed triggers), improving traceability and preventing semantic drift.
  • Positive: Default conflicts become detectable and resolvable because each DefaultId names one governing definition.
  • Negative: Authors must identify the core obligations their G.x uses. A dedicated linkage section adds work when that form is chosen. Moving shared norms into G.Core entails the checklist changes in §4.5.
  • Negative: Requires careful governance of the trigger catalogue to avoid excessive fragmentation.

Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)