FPF Reference

    G.9:3 — Forces

    Preface node heading:g-9-3-forces:105477

    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

    • Pluralism vs comparability. Multiple Traditions must be comparable without semantic collapse.
    • Partial orders. Many targets are only partially ordered; parity reporting must preserve CSLC-admissible outcome shape (often selected sets or archives rather than a single scalar).
    • Edition sensitivity. Parity must be robust to silent drift in measurement and comparator definitions. When DHC, QD, or OEE modes are used, the required definition pins are introduced only through the corresponding Extensions blocks; omit them when unused.
    • Telemetry versus objectives. IlluminationSummary, coverage, and regret are report-only telemetry by default. A dominance change needs an explicit CAL policy id recorded in the audit pins.
    • Crossing visibility. Every crossing used by parity must be visible and auditable through its CrossingBundle and GateCrossing checks; failure blocks publication or use of the parity result.
    • Cross-sense and reference-plane reuse. When expressions have distinct F.17 source-local meanings, recover both cells and establish the required F.9 relation; a ReferencePlane crossing follows its own declared crossing basis. Each actual crossing carries explicit pins, its audit evidence relation, and R-channel penalty placement.
    • Refreshability. Parity must emit RSCR‑relevant causes as canonical ids, with enough pins to re‑run.

    Last Updated: 2026-09-03 — upstream FPF commit b999972c (github.com/ailev/FPF)