FPF Reference

    What FPF Is Not

    Preface node heading:what-fpf-is-not:625

    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

    FPF is not:

    • a shrink-wrapped project methodology;
    • a checklist bureaucracy;
    • a quick-answer cheat sheet;
    • a replacement for domain expertise;
    • a demand to study the whole specification before useful work begins;
    • a promise that every project needs every pattern.

    FPF is most useful when the cost of semantic drift, premature convergence, hidden evidence gaps, weak architecture, vague quality, or unreviewable work is higher than the cost of using a disciplined pattern language.

    Last Updated: 2026-06-17 — upstream FPF commit 646b0b9b (github.com/ailev/FPF)