Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-19 01:50:20 UTC

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

Anti-patternSymptomRepair
Pretty route as ontologyA card or graph is treated as the structure.Keep it as an explanation; qualify the structure independently.
Condition label as resultA label or claim reference is treated as proof that a continuation is enabled.Apply the test or recover the obtaining relation and facts. Mark the continuation unknown when the missing basis prevents deciding it.
One enabled branch as one-branch structureThe present result erases other potential continuations.Keep potential topology and the case result separate.
Formal package or field count firstA 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 WorkA teaching slice becomes a project procedure or authorization.Use the applicable Method, work-plan, or Work pattern for work order, A.21 for a gate decision, and the permission or authority rule for authorization, only when that claim is made.
Consumer architecture copied inwardCGUS repeats transformation-flow locators, naming procedures, or catalogs of neighboring claims.Keep the local structural rule and exit to the pattern that defines or tests the other claim.