Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 03:50:10 UTC
C.30:9 - Consequences
Benefit
Cost or trade-off
Actual architecture relations and modal architecture claims become separable from diagrams, publications, generated relation graphs, ADRs, module lists, and decisions.
A conforming use recovers actual subject relations, selected A.22 structure, direct-relation disposition, exact claim EntityOfConcern and effective reference scheme, and the exact inspected-material use when relevant.
The pattern enables first-principles architecture reasoning without forcing full measurement, synthesis, assurance, or decision machinery.
Some familiar architecture phrases become triggers for quick recovery rather than accepted claims.
Functional, flow, control, module structure, interface relation, information structure, placement structure, scale structure, work structure, evidence relation, and declared logical structures can coexist without one structure kind swallowing the rest.
Use C.30.ASV to test structural-view adequacy when an explicit view application is needed.
C.29, E.18, LCA, module-and-interface repair, evidence, assurance, and gate patterns can define or test source and reliance claims used in architecture work without adding them to architecture ontology.
Name the applicable pattern and the source or reliance relation whenever the use goes beyond C.30 architecture-claim, selected-structure, or conditional description-use scope.