Architecture vs diagram/module/model
Route
route:architecture-vs-diagram-module-model
What this page is
This is an FPF route: a curated working path through pattern IDs. It is not a website route or application navigation route.
Methodology
Use the ordered steps as the first path through the framework. Treat optional steps, landing points, route surfaces, and reroutes as controls for scope, ownership, and common wrong turns. Open exact pattern pages only when the work depends on their wording.
- First Honest Burden: "We have an architecture, module diagram, ports, functional architecture, TGA graph, LCA control description, modularity score, reusable structure, or bespoke residue, but we are not sure what object the description is about."
C.30.ASV when a structural view is live; C.30.TGA-FLOW-REL and E.18 when flow graph relation is live; C.30.LCA when control structure is live; A.6.F when function wording is live; C.30.ILC when cross-scope residual is live
Route surfaces
- C.30.P Architecture and Structure Precision Restoration
- C.30 Architecture Description Adequacy (ADA)
- A.6.M
A.6.M - C.31
C.31 - C.31.RSA
C.31.RSA
Citations
J.4
Last Updated: 2026-05-31 — upstream FPF commit 16cd3138 (github.com/ailev/FPF)