the requester gets PlaceMarkRes · the other client gets GameStateNotify with the same state
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.
Turn and response
• The requesting client receives PlaceMarkRes; the other client receives GameStateNotify with the same state.
• P1/P2 dispatch each request to the bound Actor's Room handler on the Room Spot.
Rejections
• A wrong turn, an occupied cell, and a finished room are Application callback rejections and return a typed Rejected error. Only transport, route, and protocol failures use other Framework ErrorKind values.
• The final state's status and winner must match on both clients.