FPF Reference

    ARCHITECTURE — Carry an outside need through structure and feedback

    Preface node heading:architecture-carry-an-outside-need-through-structure-and-feedback:532

    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 system or another architecture subject must produce an outside result, but its pressure, options, decision, or realized feedback is unclear.
    • Question: What missing architecture result prevents the next useful decision or action?
    • First useful result or honest blocker: One clear architecture question, candidate comparison, decision, or exact missing fact or constraint.
    • Mantra: Start with the outside change and who relies on it. Name the subject and pressure; separate facts from intended constraints; compare plausible structures; choose what the current decision needs; check what the realized structure produces; reopen when use, evidence, or structure changes.
    • Start with: C.32.P2S, then the pattern for the current question in C.30, C.32, C.32.PAD, or C.30.AD.
    • Stop or return: Stop when the first result makes the architecture work reviewable. The card is not a compulsory lifecycle.

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