A.15.7:8 - Common Anti-Patterns and How to Avoid Them

Anti-pattern	Repair
“The dashboard chose the next action.”	Name the deciding System; state which current dashboard claim it used and why that claim remained applicable.
“We improvised.”	State the relevant domain-Method limits, current fact, chosen action, performer, and stop.
“Every cue needs a decision dossier.”	Keep a reversible live cue in ordinary language unless another use relies on a durable claim.
“The steering Method is obviously part of the domain Method.”	Either state two separately grounded enactments or admit the exact submethod relation; infer neither from consultation.
“The recommendation was recent enough.”	State the action-changing qualification window or refresh, safe fallback, or stop.
“The plan already contains the action, so Work occurred.”	Keep plan revision, next-action answer, and performed Work separate.
“Several options might exist, so use C.11 first.”	Recover the current Work, relevant Method limits, facts, and available actions first; use `C.11` only when several live options remain.