A.22:9 - Consequences

Benefit	Cost or trade-off
FPF gains a reusable selected-structure EntityOfConcern without minting architecture, module, interface, platform, or graph as root kinds.	A conforming use recovers the exact constituents, selected obtaining relation occurrences, applied constraints, named use frame, preserved and lost structure, and stop or return condition; one grounded non-admissible use is optional.
Structural views become usable without confusing the view, publication form, publication, source-use relation, grounding relation, and selected structure EntityOfConcern.	Existing loose prose that says “the structure is the diagram” needs repair.
Structure claims can rely on C.29 mathematical-lens results or E.18 transformation-flow structures through exact, separately established relations, without treating them as the general structure ontology.	FPF pattern applications are named when evidence, assurance, causal-use, gate, work, or decision claims are being made.
Architecture work can start from selected structure through C.30 instead of forcing architecture to be either a document or a module diagram.	Architecture-specific conformance stays outside A.22, so practitioners can require one extra C.30 application when the architecture claim or durable architecture-description use is being made.