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.
Judging join completion
• scheduled=true means the join was scheduled, not that membership commit is complete. Agent join should only be judged complete once both clients confirm the Active ParticipantJoinedNotify.
• The ConversationId of JoinConversationReq is a required stream-metadata value and isn't put into the payload as a route. participantId, role, and displayName are values needed for the actor join.
Starting state and waiting
• The starting state is that Session, Api, and Support readiness is complete, and the Agent roster is either empty or has capacity.
• When no Agent is assignable, the Customer's OpenConversationReq isn't an error — it waits at WaitingForAgent.
• OpenConversationApiReq and ConversationCreateReq are server-to-server request/reply. The Framework-issued SpotId is used as the ConversationId, and the owner location and ActorRef aren't put into the response. The ActorId in ParticipantJoinedNotify and ConversationAssignedNotify is the agent's identity actor id.