G.9:0.1 — What goes wrong if missed
Preface node
heading:g-9-0-1-what-goes-wrong-if-missed:80563
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
- benchmark numbers mix different windows, baselines, or comparator editions and still pretend to be comparable
- cross-context reuse or 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
Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)