the game room publishes the reward · the observer's local room forwards it as a bound push, then the observer stops
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.
Participants and publish path
• Observer = Observer Client; Observer Actor/Room = Play / Observer Actor/Room; Game Room = Play / Game Room.
• The game room first confirms the end result, submits the player push, then publishes BingoRewardAcquiredEvent to the bingo.room.reward topic. Each Play node's local observation BingoRoom subscribes to the same topic; only a room whose event RoomId matches its own ObservedRoomId sends a typed message to the observer Actor, which notifies via bound session.
Delivery semantics
• The observation room doesn't participate in player membership, cards, the timer, or winner determination, and no separate reward-only Spot type is created.
• Normal publish completion means the source runtime started the operation — it doesn't guarantee subscriber handler execution or per-target acceptance. The Client confirms the delivery result via the BingoRewardAnnouncedNotify payload, not the publish return value.