A.22.CGUS:8 - Common Anti-Patterns And Repairs

Anti-pattern	Symptom	Repair
Pretty route as ontology	A card or graph is treated as the structure.	Keep it as an explanation; qualify the structure independently.
Condition label as result	A label or claim reference is treated as proof that a continuation is enabled.	Apply the test or recover the obtaining relation and facts; otherwise return `unknown`.
One enabled branch as one-branch structure	The present result erases other potential continuations.	Keep potential topology and the case result separate.
Formal package or field count first	A simple correction requires replay fields, or authors add references merely to raise schema completion.	Use the ordinary branch and stop when it answers the question. In formal use, retain only fields consumed by qualification or replay and test whether readers recover the right alternatives and smallest repair.
Displayed order as Work	A teaching slice becomes a project procedure or authorization.	Use the applicable Method, work-plan, or Work pattern for work order, A.21 for an actual gate decision, and the direct permission or authority rule for authorization, only when that claim is actually made.
Consumer architecture copied inward	CGUS repeats transformation-flow locators, naming procedures, or catalogs of neighboring claims.	Keep the local structural rule and exit directly to the pattern that defines or tests the other claim.