#G.9:3 — Forces

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

#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/comparator definitions. When DHC/QD/OEE modes are used, the required definition pins are introduced only via the corresponding Extensions blocks (nil‑elision when unused).
• Telemetry vs objectives. IlluminationSummary and coverage/regret are telemetry: report‑only by default; dominance changes require explicit CAL policy ids (recorded in audit pins).
• GateCrossing visibility. Any crossings/gates used by parity must be visible and auditable via CrossingBundle + GateCrossing checks; failures block parity publication/consumption.
• Cross‑Context reuse. Any reuse across contexts or reference planes must carry explicit crossing pins, 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-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)