B.1.2:7 - Common Anti-Patterns and How to Avoid Them

Anti-pattern	Symptom	Repair
Box as boundary	A diagram rectangle determines system membership.	Recover system identity and every obtaining part and crossing relation; stop if those facts answer the question. If a distinct use-relative boundary choice remains, name the applicable C.11 `ChoiceResult`, C.32.PAD `ArchitectureDecisionRelation@Project`, or another explicitly admitted direct result; otherwise stop with the missing-governor blocker. Add a C.2.1 episteme only when that claim must persist; use an A.22 selected structure only when its four discriminators are independently grounded.
Supplier as component	External supplier or grid is treated as part of the system.	Recover the exact supply, commitment, evidence, source-use, or other crossing relation under its subject pattern; infer no parthood.
Function block as module	A functional block is treated as a physical component.	Recover the exact functional element, proposed bearer, allocation or correspondence, and any obtaining part relation separately.
Digital twin as part	A model or dashboard appears inside the system aggregate.	Use description, representation, publication, evidence, source-use, and naming patterns; add parthood only if its direct predicate independently obtains.
Redundancy as arithmetic	Redundancy is averaged into a better system score.	Check characteristic scale and existing-whole explanation; use B.2 when the whole must be reidentified.