FPF Reference

    The Culinary Architecture Of Collective Thought

    Preface node heading:the-culinary-architecture-of-collective-thought:999

    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

    Many FPF ideas sound familiar. Evolution, exploration and exploitation, evidence, roles, boundaries, architecture, comparison, naming, and improvement are not new ingredients. A thoughtful reader may ask why FPF formalizes so many "obvious" ideas.

    The answer is that FPF is not trying to invent the ingredients. It is trying to build the kitchen.

    A domain methodology is like a cookbook. It gives excellent recipes for a class of dishes: software delivery, scientific experiment, safety case, product discovery, architecture review, or policy design. A skilled practitioner can often cook one dish beautifully from experience alone.

    FPF is closer to the architecture of a professional kitchen. It gives places, instruments, roles, interfaces, checks, and repeatable forms so many dishes can be prepared, compared, improved, and served without chaos. The value is not that flour or heat are new. The value is that ingredients, techniques, stations, timing, quality checks, and presentation can work together at scale.

    In FPF terms:

    • roles separate who can act, review, evidence, decide, or publish;
    • methods and method descriptions separate how action can be performed from the document describing it;
    • work patterns keep actual change distinct from plans;
    • evidence and assurance keep proof and reliance inspectable;
    • characteristic spaces define what quality means for the object at hand;
    • architecture patterns keep structure distinct from diagrams;
    • naming and term sheets let people talk across contexts without semantic collapse;
    • state-of-the-art and option portfolios keep search open before selection;
    • improvement loops let the whole arrangement get better over time.

    For a small well-known problem solved by one expert, FPF may feel heavier than intuition. Its advantage appears when reasoning must be collective, long-lived, high-stakes, cross-domain, AI-assisted, or open-ended. That is where tacit expertise alone becomes hard to audit, transfer, or refresh.

    FPF does not replace expert judgment. It gives expert judgment a shared architecture so it can compound rather than evaporate.

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