B.3.4:6 - Common Anti-Patterns and How to Avoid Them

Anti-pattern	Failure in use	Repair
Old therefore invalid	An unchanged qualified library result is discarded because its report crossed a generic date.	Check the condition that matters; retain applicable support without automatic renewal.
Unchanged file therefore safe	A newly relevant dependency vulnerability is ignored because the library bytes are unchanged.	Reopen the affected security claim and communicate its unsupported reach.
Green therefore assured	Fresh reports or zero overdue reviews hide an unresolved performance failure.	Assess relevance and adverse results for the target claim; report dashboard meaning honestly.
Status as risk acceptance	Lowering a badge or obtaining a senior signature is treated as permission to expose others to harm.	Establish the actual rule, authority and permitted response; restrict unsupported use where needed.
Maintenance by forced experiment	A repeat test consumes the only opportunity for a protective inspection without changing any relevant conclusion.	Compare marginal contribution and displaced cost; retain binding conditions while seeking any justified amendment.