#G.9:0 — Use this when

Preface node heading:g-9-0-use-this-when:118826

#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

• rival method families, method sets, or adaptation paths must be compared under one declared baseline set and freshness window
• you need parity to publish one reproducible report rather than one opaque benchmark score
• downstream selection must recover comparator, normalization, bridge, and evidence pins without relying on one hidden scoring sheet

#G.9:0.1 — What goes wrong if missed

• benchmark reports present numbers from different windows, baselines, or comparator editions as comparable
• reuse across distinct source-local meanings, a reference-plane crossing, or a normalization mapping stays hidden until a disagreement appears downstream
• parity flattens a partial order into one scalar winner and silently changes what the comparison means

#G.9:0.2 — What this buys

• one exact ParityPlanRef that fixes the plan edition, baseline, freshness, comparator, and bridge discipline up front
• one ParityReport that cites that exact plan and echoes its active baseline binding, pins, outcomes, and evidence trace by value
• one harness that downstream selection can consume without inventing a G.9-local CSLC gate or a shadow governance card

Illumination, coverage, and regret remain telemetry by default. If they are promoted into dominance, that promotion must be one explicit policy-bound choice rather than one hidden scoring convenience.

---

Last Updated: 2026-10-12 — upstream FPF commit f2bc67dd (github.com/ailev/FPF)