Route mesh channel — one connection, channels are names on top
node B reaches nodes on both the orders and billing channels over one MeshNode socket
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
Semantic radar needs more MAP space.
One MeshNode socket, channel names on top
• node B shares its orders Client and billing Client over one MeshNode socket — all four connections (A1·A2·C1·C2) sit on that single socket, and each is bidirectional (request · reply).
• The boxes are groups tied by name, not sockets. Calling orders has select-one pick one of A1/A2, and registering more channels doesn't add any sockets on node B.