FPF Reference

    G.12:8 — Consequences

    Preface node heading:g-12-8-consequences:107045

    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

    Benefits. Dashboard claims can be read quickly and replayed from exact result and definition refs. Historical results remain distinct from changed definitions, and refresh can be local when needed.

    Costs. A relied-on trend needs exact result, scope, window, and replay identities. Publication and refresh add their own conditional work.

    Risks avoided. Screenshot-as-result, context-container resurrection, scope/slice collapse, hidden method drift, illicit ordinal arithmetic, scalarization by view, and carrier-as-publication are blocked.

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