FPF Reference

    PRACTICE-ARCHITECTURE — Connect methods with their use, support and development

    Preface node heading:practice-architecture-connect-methods-with-their-use-support-and-development:684

    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 decision about methods depends on performed or planned Work, capabilities, providers, descriptions, tools or cultural change whose structures do not align one-for-one.
    • Question: Which relations change how the methods can be used or improved?
    • First useful result or blocker: One readable synthesis, one bounded development action, or the exact missing Work case, relation, or transfer evidence.
    • Mantra: Start from representative Work and its needed result, or a proposed use with a later-test condition. Keep Methods, Work, capabilities, providers, descriptions, tools and cultural processes distinct; compare the structures that conflict; develop a limiting capability when needed; test transfer in real Work; return when the method, provider, evidence or style changes.
    • Start with: C.32.MWA; use E.23.CDI, E.23, or C.36 only for the question actually opened.
    • Stop or return: Stop when the synthesis or transfer result answers the decision. A method description is distinct from the method and from performed Work.

    Last Updated: 2026-10-12 — upstream FPF commit f2bc67dd (github.com/ailev/FPF)