C.30.ASV:9 - Consequences

Benefit	Cost or trade-off
Architecture views become exact description epistemes over selected structures, not diagrams by appearance.	A conforming use states C.2.1 identity, selected structure, structure kind, exact viewpoint, obtaining conformance relation, and admissible use.
Project-local TEVB reference reuse does not enlarge either template.	Architecture-specific structure-kind bindings add one explicit record when their coverage matters; every reused viewpoint reference retains its exact materialized catalogue and member provenance and grants no view membership.
Functional, flow, control, module-interface, placement, information, runtime, work, evidence, scale, material, and logical structures can be separated.	Some familiar names require triage before they can carry FPF claim kinds.
Failed checks produce repair actions rather than only classification objections.	The checklist is longer than a pure taxonomy, but it is more useful for action.