Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:40:20 UTC

C.30:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Architecture-as-documentA document, diagram, table, generated relation graph, or dashboard is treated as the architecture or as what makes ArchitectureRelation obtain.Recover the representation and publication objects, claim episteme, selected structure, and actual direct relation separately; a carrier creates none of their subject-side facts.
Publication-unit architecture driftOne publication unit mixes architecture description, evidence claim, gate decision state, decision note, and work authorization under one architecture heading.Name the ArchitectureRelation or modal ArchitectureClaim content, keep description, view, and publication objects separate, and use the applicable patterns for evidence, gate, decision, and work claims.
Module-diagram takeoverArchitecture is reduced to module structure or interface relation.Recover the structure kind, use C.30.ASV, and use the module-and-interface repair pattern when the full module claim is current.
Tool-model lock-inA notation or tool model becomes the source of architecture truth.Recover FPF architecture claim, structures, views, correspondence, and source-return condition.
Evidence launderingA published architecture description is used as evidence sufficiency.Use A.10 for source recovery and bounded reliance, and G.6 for a citable evidence-provenance path; identify each represented relation through its defining pattern. C.30 keeps only the architecture claim, selected-structure, and conditional architecture-description-use boundary.
Assurance or safety overreadArchitecture description or LCA diagram is used as assurance or safety case.Use B.3, A.10, G.6, C.30.LCA, or the safety or gate pattern according to the claim being made.
Risk color as architecture decisionA risk color, matrix or maturity score decides the architecture move or resource priority by itself.Recover the decision, affected structure and the rule connecting the color or score to that decision. Establish the hazard or loss, comparison basis and evidence; add assurance or a gate result only when the receiving decision requires it.
Causal sloganArchitecture property is said to cause a quality without a bounded claim or independently admitted relation grounding.Start with ArchitectureStructuralCharacteristicQBundleClaimLine; apply C.28 or the applicable evidence, causal-use, or assurance pattern, or use ArchitectureCharacteristicQBundleClaim when a durable bounded claim is needed. Name a direct relation only after its defining pattern identifies the participants and its predicate is satisfied.
Architecture-operation overreadReplacing a block, module, layer, protocol, cache, memory path or flow relation is treated as improvement by label alone.Recover unclear source labels through C.30.STRAT, then establish the changed structure or relation and the characteristic comparison claimed. Retain preservation, loss, source or decision grounds when the use consumes them.
Sterile compliance rewriteThe text becomes well typed but no longer helps the practitioner act.Restore a next architecture move, an ArchitectureQuestionCard@Project when needed, or the pattern for the separate claim.