| Module diagram as architecture view | One module-interface diagram is treated as the whole architecture or as a U.View by appearance. | Use structure-kind triage; keep module-interface as one structure kind and apply exact E.17.0 conformance only when view membership matters. |
| Viewpoint as structure kind | VP.Functional, VP.ModuleInterface, or another viewpoint is used as if it were the selected structure kind. | Recover ArchitectureStructureKindRef; keep its binding to an exact viewpoint episteme separate. |
| Structure kind as viewpoint | FunctionalStructure or ControlStructure is treated as if it were already an admitted viewpoint P. | Keep structure-kind classification separate; when viewpoint reuse is needed, resolve one exact U.ViewpointRef from a materialized local catalogue declaration to exact P and test E.17.0 conformance. |
| Publication-face collapse | A diagram, model, table, dashboard, generated relation graph, ADR, or C4 view is treated as the view episteme. | Recover description episteme, representation, and E.24.PUB occurrence, form, and carrier separately; use ArchitectureStructuralView only if exact conformance obtains and the view changes action. |
| Single-view decision | A decision uses one architecture view as if it covered all affected structures. | Name affected structures and view refs, or narrow the decision to the single view’s admissible use. |
| Lost-structure silence | Extracted, generated, coarsened, or compressed views hide distinctions but still justify action. | Add hidden structure and lost structure and source-return condition, or narrow admissible use. |
| Proof overread | The structural view is used as evidence sufficiency, safety proof, causal proof, gate decision, or work record. | Use the applicable evidence, assurance, causal, gate, or work pattern and keep ASV only to view adequacy. |
| Risk color as security architecture | A red, yellow, or green risk cell, risk matrix, maturity score, or compliance color stands in for SecurityTrustBoundaryStructure or resource-allocation priority. | Recover protected asset or effect, trust boundary, untrusted input, privilege or authority relation, data flow or control flow, abuse or misuse path, and the evidence named by value, assurance, measurement, causal, gate, selection, or allocation claim kind if that claim is being made; do not treat ordinal risk color as security architecture adequacy, resource-allocation priority, or gate passage. |
| Taxonomy without action | The text classifies a view but does not say what changes in practice. | Add admissibleArchitectureMove or stop at Plain recognition wording. |