manual peer connection · client STREAMs directly to Play
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.
Connection flow
• With no separate Session server, each Play owns the stream session · actor · Entry Spot · room Spot together
• client creates a room over HTTP via Api → Api creates a room User Spot on Play
• client connects directly to each Play by STREAM using the Play endpoints it got from Api (emphasis)
• the dashed path to Api B / Play B is the alternate route · the second player's share
peer · location
• Play A ↔ Play B is a manual peer connection (bidirectional) — publishes the win-count milestone by Logical Multicast
• room·actor location is resolved by Location Store lookup (dashed) — only the connection between nodes is manual, object location is resolved by the store