Context map — the integration view
Same model, zoomed out to the seams between teams. Contexts collapse to flat-bottomed clouds.One board, six readings. The map is generated from the regions and the arrows that cross them — never drawn by hand, so it cannot drift from the timeline. Every map carries a state: the board exists to model a change, so as-is and to-be are two maps over one model, not two documents.
SHARED KERNEL PARTNERSHIP CUSTOMER / SUPPLIER INFLUENCER OHS / PL VETO RIGHT U DCONFORMIST U DOHS / PL U DACL MONOPOLIST U D
One board, six readings. The map is generated from the regions and the arrows that cross them — never drawn by hand, so it cannot drift from the timeline. Every map carries a state: the board exists to model a change, so as-is and to-be are two maps over one model, not two documents.
switch AS-IS / TO-BE above — the to-be regions and relationships stay dashed until a step exists for them
Notation
- U / D upstream and downstream ends of a relationship.
- ACL anticorruption layer: the downstream translates rather than adopts.
- OHS / PL open host service with a published language.
- Conformist the downstream simply accepts the upstream model.
- Shared kernel · Partnership · Customer/Supplier symmetric relationships; no ACL implied.
- Stroke weight 2.6px is a core context, 1.8px supporting or generic, 1.2px dashed grey is outside our boundary.
- Governance right a dotted chip beside the pattern: INFLUENCER, OPINION LEADER, VETO RIGHT, DECISION MAKER, MONOPOLIST. The pattern says how the two models meet; the right says who can stop a change. Solid chip is the pattern, dotted is the right.
- Map state AS-IS or TO-BE. Both read from the same stickies; the to-be map may carry regions and relationships the timeline does not have yet, and those stay dashed until a step exists.
documentation chrome, not a component: the legend explains marks the view already draws, so `context-map/` correctly did not build it
Clouds, not boxes: off the grid the flat-bottomed cloud is the context, so a region on the timeline and a node here read as the same object. Relationship lines meet the flat baseline or the straight sides. Every line must name a pattern — an unnamed relationship goes to the review queue.