the Room marks and leaves the Actor · the Framework returns it to the Entry Spot, which destroys it
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.
Relocation and destroy (mermaid Notes and Entry Spot self-message)
• mermaid Note over PlayerActor,EntrySpot: after the Room leave, the Framework relocates the Actor to the Entry Spot and calls its join callback (Entry Spot self-message 'Invoke join callback').
• mermaid Note over EntrySpot,PlayerActor: Destroy does not invoke the leave callback — Destroy cleans up the Actor registry, native ref, and binding, but doesn't call onLeaveActor again.
Order and boundaries
• The Room records state so cleanup only starts once, marks each player Actor to destroy after returning to the Entry Spot, and leaves the room.
• The Room leave callback waits on API's result recording via Yield; the external effect is idempotent so the same result converges on re-run. The Entry Spot checks the mark and then calls the public destroy operation, expressed as an async completion with no result value.
• On a STREAM disconnect the Framework submits disconnect to each exact identity in the binding snapshot: it cleans up the bound session but doesn't iterate Actors, remove a binding directly, destroy the Actor, or change room membership.