FPF Reference

    1. Develop or review architecture

    Preface node heading:1-develop-or-review-architecture:443

    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

    Use this when you need to design, explain, review, or improve the architecture of a product, organization, technical system, document system, AI-agent setup, research program, local practice, or other thing with important internal structure.

    FPF helps you start from the thing being changed or described, not from the drawing. It asks which structures are unknown, candidate, selected, expected, or actual; which architecture characteristics are under pressure; which alternatives must remain alive; which decision is now binding; which method or work will realize the selected structures; and what operation, measurement, or feedback can reopen the architecture.

    Typical first result: a short P2S flow card or architecture question note that names the described holon, bounded context, problem pressure, unknown or selected structures, architecture characteristics, candidate or decision owner, work or feedback owner, and what real selected structure is still not settled by the current architecture statement.

    First inspect: C.32.P2S, C.30, A.22, C.32, C.32.PAD, C.32.ADR, C.33, C.34, C.35, C.30.ASV, C.30.AD, C.31, C.32.CONWAY, and B.2 or B.2.P when the work may reidentify the whole being discussed.

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