JoinWorld completes from the Actor Join completion callback · same-zone Move updates the Zone Spot copy
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.
Self-actions folded into the following message (archify sequence rejects from==to)
• mermaid A->>A: Defer() zone join, end handler — the Actor registers the join with Defer() and ends the current handler normally before EnterZoneReq; the join result arrives in a completion callback.
• mermaid A->>A: validate and update coordinates — the Actor validates the move and updates coordinates before sending UpdatePositionMsg to the Zone Spot.
Normative meaning
• A zone join is a Framework Actor Join, so it does not complete synchronously inside a handler.
• A successful JoinWorldRes means target zone admission has completed — an implementation that produces the JoinWorldRes terminal from pre-admission state (such as a cache) is non-conforming.
• Starting state: Gateway, the two ZoneNodes, and Ops have completed readiness, and the browser has connected a STREAM to Gateway. JoinWorld starts at (25,25) in zone-nw.