G.9:3 — Forces

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

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. Support justified comparisons across Traditions while preserving their differences in meaning and admissibility.
  • Partial orders. Many targets are only partially ordered; parity reporting must preserve CSLC-admissible outcome shape (often declared set results rather than a single scalar; an archive may supply the compared candidates).
  • Edition sensitivity. A reader must be able to tell which measurement and comparator definitions a parity run used, even after those definitions change. 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. An actual E.18 flow crossing or A.21 gate used by parity retains its required CrossingBundle, pins and checks. Failure blocks the dependent publication or use.
  • 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 correspondence retains its required pins and evidence; any justified numerical loss follows its receiving model and R-channel placement.
  • Refreshability. Parity must emit RSCR-relevant causes as canonical ids, with enough pins to identify the affected use and plan any needed rerun.

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