FPF Reference

    PRACTICE-ARCHITECTURE — Develop a practice without collapsing its structures

    Preface node heading:practice-architecture-develop-a-practice-without-collapsing-its-structures:541

    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: Methods, Work, capabilities, providers, descriptions, tools, and cultural change do not align one-for-one in a practice.
    • Question: Which relations must be reconciled for the practice to become usable or improve in representative Work?
    • First useful result or honest 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. Keep Methods, Work, capabilities, providers, descriptions, tools, and cultural processes distinct; compare the structures that conflict; develop the limiting capability; test transfer in real Work; return when practice, 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 practice description is not the practice or performed Work.

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