FPF Reference

    SOTA-PORTFOLIO — Move from a plural field to the cheapest useful result

    Preface node heading:sota-portfolio-move-from-a-plural-field-to-the-cheapest-useful-result:622

    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

    • Situation: A project needs the modern field of approaches rather than one popular answer and may later need maintained domain guidance.
    • Question: What plural view is adequate now, and does the remaining problem call for reuse, a contribution, another product, a DPF or LPF, or no maintained result?
    • First useful result or honest blocker: One source-linked SoTA view, live option set, reuse route, framework decision, or exact missing scope or maintenance basis.
    • Mantra: Name the practical question, scope, freshness need, and rival traditions. Build a source-linked plural view; preserve disagreement and source-use limits; compare useful approaches; try cheaper reuse or contribution first; open a framework decision only for a recurring unmet problem; author and test the needed patterns; refresh when the field or use changes.
    • Start with: G.2; add C.18, C.19, or G.5 for the set and the E.4/E.9 authoring route only if a framework is selected.
    • Stop or return: Stop at the first adequate maintained or one-off result. A source pack or proposal is not a framework by appearance.

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