ROUTE_SELF_LOOP_OCCUPANCY
ROUTE_SELF_LOOP_OCCUPANCY is a geometric warning: a self-loop cannot reserve a clear side, boundary span, route corridor, or label area without colliding with another loop or route.
What triggers it. Several self-loops competing for the same node side, or a later route/label pass entering space already certified for a loop. The warning names the conflict kind and, when applicable, the other edge.
How to fix it. Move one relationship to a different endpoint or remove a redundant loop. If unchanged source fires nondeterministically, report it as a route-allocation defect.
Run am verify diagram.mmd --json, inspect this code, and apply the smallest source or typed mutation that clears it. If it persists after two mechanical attempts, return the warning and ask for human review.
In the cloned repo, am is bun run bin/am.ts.
Machine-readable: this page as Markdown.
Back to all warning codes, or open a blank editor to try a fix.