ARCHITECTURE — Carry an outside need through structure and feedback

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

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: Someone needs to understand how a whole is organized, choose a workable structure, or change what happens in use.
  • Question: What must the architecture explain, establish or make possible in the recipient’s work?
  • First useful result or blocker: A grounded account of the relevant connections, a justified design choice, or the missing condition that changes the answer.
  • Mantra: Start from the effect or question. Identify the whole, its relevant constituents and their connections. Trace how they produce the property in question. Compare arrangements when a choice is open. For a change, follow the work through to its agreed result.
  • Start with: C.30 for an architecture question, C.30.AD for its description, C.32 or C.32.PAD for a design choice, and C.32.P2S to carry a need through architectural change.
  • Stop or return: Give the requested explanation or grounded choice. For a change, establish what was commissioned: installation, capability under agreed conditions, or actual use.

Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)