FPF Reference

    Migration playbook (informative)

    Preface node heading:migration-playbook-informative:82906

    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

    1. Inventory scope‑like phrases across your Context (search: applicability, envelope, generality, capability envelope, valid*).
    2. Classify each occurrence as Claim scope (episteme) or Work scope (capability); replace any “scope characteristic(s)” with “scope object”, “scope type”, or “USM scope object” depending on sentence grammar.
    3. Rewrite guards to use Scope covers TargetSlice + explicit Γ_time; remove “latest”.
    4. Publish any required Bridges with CL for Cross‑context usage.
    5. Document ΔG changes separately from evidence freshness (R).

    Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)