SOTA-PORTFOLIO — Compare approaches that could answer your question
Preface node
heading:sota-portfolio-compare-approaches-that-could-answer-your-question:856
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: Your team needs to know what competing approaches can establish and where each applies.
- Question: What can the sources already answer, and what work remains?
- First useful result or blocker: A comparison linking each claim to its source, edition, evidence and limits. State where the claims can be compared, what remains disputed and which part of your question is open.
- Mantra: Fix the inquiry and freshness needed. Compare claims, methods and grounds. Keep consequential disagreements. Use the comparison if it suffices. For a remaining need, consider reuse, a contribution, another product or maintained guidance. If a DPF or LPF is warranted, develop and test its patterns and revisit them as evidence or use changes.
- Start with:
G.2for source comparison. UseC.18,C.19orG.5for options. For framework authoring, develop the practitioner’s explanations underE.4.DPF. UseE.4.PFADfor a product choice andE.9for its decision record when needed. - Stop or return: Stop at the comparison when it answers the commission. For a usable practice or framework, carry the grounds into its construction and check what the practitioner can do. Recover a source construction lost in translation through
FPF.Reference:16.5.
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)