Session validates the token via API, gets/creates the Player Actor, and binds the STREAM 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.
Binding step and route
• Between ActorRef and AuthenticateRes, Session binds the current STREAM session to the returned ActorRef (mermaid Session self-message).
• mermaid Note over Session,Play: later packets use the stored binding route — game packets after AuthenticateRes is returned are relayed to the Actor via the stored binding route.
Ownership boundary
• Session asks API to validate the token; on success Session gets or creates the Player Actor by global ActorId and stable actor type.
• Session doesn't store the physical Play endpoint or NodeRid. If the Actor moves via a planned relocation, the Framework updates the binding route.