Case Overview: One Line, Three Readings
A procurement workflow diagram showed a double-headed arrow between "Budget Review" and "Compliance Sign-off." The diagram author meant "these two checkpoints exchange status updates." Engineering read it as "approval flows in both directions." Finance read it as "either checkpoint can approve." Legal read it as "the two steps are interchangeable." Three teams built three different processes around one ambiguous line.
The misreading surfaced during a quarterly executive review, when an auditor asked why purchase orders cleared compliance before budget confirmation. Neither team was wrong per its own reading of the diagram — the connector had simply never committed to a semantics, so every reader projected a different one onto it.
Failure Signature: Bidirectional Edges Between Checkpoints
A double-headed arrow between two governance gates almost always hides two distinct unidirectional relationships — a request path and a verdict path — with different payloads, timeouts, and rejection handling.
The remediation took twenty minutes: split the bidirectional arrow into two labeled edges — "submits for verdict" from Budget Review to Compliance, and "returns decision" in the opposite direction — each annotated with its payload and rejection behavior. The follow-up audit found zero disputed interpretations.