roster · conversation actors bound to one agent session
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 connection, several actors
• agent client ↔ session is one stream connection (bidirectional)
• that session binds the roster actor (Entry Spot) + a per-conversation conversation actor together (dashed)
• the agent sends through each room's Actor handle found from JoinConversationRes.actorId; Session relays to the bound Actor when the packet has an Actor slot, or to the identity Actor when it does not
• roster·conversation·customer nodes are circle actors in the original — drawn as boxes here
conversation Spot
• each conversation Spot holds the agent-side conversation actor and the customer actor together
• customers A·B are participants in their own conversation — only inside each Spot, with no separate connection line