Game/Ops browsers · Gateway/Ops · two ZoneNodes on zoneworld.mesh RouteMesh + broadcast fanout
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.
Full channel names (mermaid edge labels)
• "mesh RouteMesh" on the diagram is the full mermaid label "zoneworld.mesh RouteMesh" — carries the ChannelName, Spot/Actor direct messages, and Logical Multicast.
• "broadcast fanout" is the full mermaid label "zoneworld.broadcast fanout" — a classic fanout publisher/subscriber connection independent of the mesh.
• Only Gateway provides the player-facing game STREAM, and only Ops provides the control STREAM.
ZoneNode roles
• ZoneNode A/B run with the same executable capability, registering the Zone Spot factory (stable type zoneworld.zone, four Spot instances by ZoneId), the Player Actor factory (stable type zoneworld.player), the zone Channel, and the report channel.
• Zone Spot capacity and readiness follow §3 of the ZoneWorld sample contract.
• NodeId and the transport RID are separate domains.
• Only the Gateway and Ops endpoints are exposed to the Client; the ZoneNode endpoint isn't exposed.