Case Overview: The Lineage Arrow That Looked Like a Pipeline
A platform team published a system map where solid arrows ran from "Data Platform Team" to each of five services — intended to show which group owned which component. A partner engineering team read the same arrows as data flows and designed an integration assuming the platform team brokered every request through a central service that did not exist.
The error only surfaced in design review, weeks in, when someone asked which API version the "owner service" exposed. There was no owner service — only an org chart accidentally drawn in flow notation. The diagram had fused two different semantic layers: responsibility and runtime traffic.
Failure Signature: Organizational Edges in Runtime Clothing
If an arrow's endpoints are a team and a service — not two runtime components — it is an ownership relationship. Rendering it with the same stroke, weight, and arrowhead as data flow guarantees misreading.
Responsibility matrices and domain boundaries solve this without borrowing flow notation at all: containment regions, color-coded ownership bands, or a labeled "owned by" badge on each node express accountability while leaving the arrow vocabulary free for actual traffic.