FPF Reference

    G.12:3 — Forces

    Preface node heading:g-12-3-forces:84225

    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

    • Legality and comparability are governed by CN-Spec and CG-Spec. Dashboards must not invent local legality/acceptance/normalization “mini‑specs”; they pin and cite CN‑Spec and CG‑Spec surfaces as required by G.Core conformance.
    • Ordinal discipline is non‑negotiable. The most common dashboard failure mode is illicit arithmetic on ranks/categories; the kit must make “compare‑only” enforceable.
    • Set‑returning discipline survives into views. Dashboards must not silently scalarize partial orders or selector selected-set results; any scalarization/promotion is an explicit governing-pattern policy cited through G.Core conformance; semantics are governed by the relevant pattern or policy.
    • Edition‑awareness is the difference between “trend” and “drift”. If the method definition changes, the dashboard must either (i) fork series edition, or (ii) emit telemetry and refresh slices under pinned conditions.
    • RSCR must be actionable. Causes are emitted as canonical ids (typed trigger kinds + id‑valued pins), not prose.

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