FPF Reference

    G.Core:12 - Relations

    Preface node heading:g-core-12-relations:78865

    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

    • Builds on:

      • E.8 pattern template and section discipline
      • E.10 lexical/ontological rules (strict distinction; twin naming; kind‑suffix discipline)

    • E.18 CrossingBundle (crossing visibility bundle)

      • E.19 conformance discipline
      • A.6.7 SuiteObligations + suite protocol pins (delegation support)
      • A.15.3 SlotFillingsPlanItem (planned baseline anchor)
      • A.19 CN‑Spec governance card
      • G.0 CG‑Spec legality gate
      • A.19.CHR CHR suite boundary and "governance cards and legality gates are cited as pins, not copied locally" discipline
      • C.23 SoS‑LOG (tri‑state branches; sandbox/probe‑only)
      • F.17 UTS (identifier registry; alias/deprecation discipline)
      • F.15 RSCR (regression/conformance loop)

    • Used by:

      • G.0…G.13 patterns (each adds Builds on: G.Core, linkage section, CoreRef CC item)

    • Constrains:

      • Part‑G authoring: no shadow specs, no silent scalarization, tri‑state guards, penalties routing, typed RSCR causes, defaults with one governing definition, and ID‑continuity refactors.

    Last Updated: 2026-06-17 — upstream FPF commit 646b0b9b (github.com/ailev/FPF)