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

Anti-pattern	Symptom	Repair
Named aggregate as system	“The platform” or “the fleet” is treated as a system because it has a name.	Identify one exact candidate and apply the complete A.1 and direct `U.System` criteria; if either fails or cannot be determined, withhold system-result recognition and return that failure or `unknown` to B.2 without inferring that the old whole is sufficient.
Component certificate transfer	Individual part certificates are used as result-system assurance.	Re-base assurance through B.2.2:4.5 and evidence-use patterns.
Controller as containing whole	A controller or external system is treated as the new whole because it changes the parts.	Use A.12, A.3.4, B.2.5, and part-whole patterns separately.
Dashboard as system	A monitoring model is treated as the operating system.	Use episteme, publication, source-use, C.30.AD, or digital-twin description patterns.
Capability jump as system MHT	A metric improves and the result is called a new system.	Perform B.2’s ordinary existing-whole comparison; return to capability, characteristic, Method, Work, or architecture patterns if the existing whole remains sufficient.