E.17.AUD:6 - Common Anti-Patterns and How to Avoid Them

Anti-pattern	Why it fails	How to avoid it
Fixing one sentence while the whole unit already carries a quiet interpretation shift	local repair is asked to carry whole-unit stabilization	check primary subject, carried publication move, and outside boundary to work, work planning, decision, gate, or reliance claim before repairing the sentence
Treating form labels as if they changed the publication unit under review	`table`, `sheet`, or `screen` is used as if it already named a different ontology or downstream claim or effect	treat those as presentation forms first; only leave this pattern when the problem situation itself changes
Laundering comparison through stability language	teams keep saying the unit is unstable when the active problem situation is already bounded comparison	apply `E.17.ID.CR ComparativeReviewUnit` and name the exact source publications
Laundering downstream decision or reliance through clearer prose	a better-written note is over-read as if it had become an approval, gate, work, or reliance text	keep the outside boundary to work, work planning, decision, gate, or reliance claim explicit and leave this pattern when downstream claim or effect appears
Letting three repair choices act at once	lexical-head repair, whole-unit stabilization, and a neighboring-pattern application are patched in parallel with no shared primary-subject interpretation	use the working card first and name one current repair choice before patching the unit