FPF Reference

    G.Core:9 - Consequences

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

    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‑wide invariants cite G.Core as their governing definition; 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: Adds an extra authoring step (linkage sections and CoreRef CC item) to each G.x.
    • Negative: Requires careful governance of the trigger catalogue to avoid excessive fragmentation.

    Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)