G.Core:5 - Archetypal grounding

Preface node heading:g-core-5-archetypal-grounding:135971

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

Tell. A Part G pattern can present a short normative Core linkage section alongside its pattern-scoped Extensions. A direct reference with its use conditions also suffices (§4.2). Authors cite the governing definitions of universal obligations, including A.6.7, A.15.3, A.19, G.0, and A.19.CHR. Typed RSCR trigger kinds and DefaultGoverningDefinitionRef references point to named definitions.

Show 1: Refresh triggers without semantic drift. G.11 uses trigger tokens T0…T7. G.Core keeps them as aliases and maps them to canonical trigger kinds (e.g., TelemetryDelta, EditionPinChange, CrossingBundleEdit). This makes RSCR reason codes consistent across patterns and avoids re-explaining trigger semantics in every pattern.

Show 2: Resolving competing defaults. If several patterns imply a default for PortfolioMode, the Default Governing Definition Index points to the governing definition, CC‑G5.23. Other patterns, including bundle and log patterns, must leave the definition there and cite or delegate to it. A separate local wording could change how their readers interpret the default.


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