Ops fans WorldAnnounceEvent and NodeMaintenanceChangedEvent out to every ZoneNode, which applies only its own NodeId
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 preceding message (archify sequence rejects from==to, no following message on that lane)
• mermaid Z1->>Z1: apply only matching NodeId — appended to the NodeMaintenanceChangedEvent fanout message to Z1.
• mermaid Z2->>Z2: apply only matching NodeId — appended to the NodeMaintenanceChangedEvent fanout message to Z2.
Registered vs. Connected, and maintenance semantics
• WatchNodesRes's Registered and Connected are different observations: Connected comes from the peer state of the runtime status observation, and Registered comes from ZoneNode's explicit report — the Framework topology status doesn't expose a registration signal.
• If the target zone owner has maintenance=true, the target Zone Spot's OnActorJoin admission rejects with ZoneMaintenance. Only movement within the same zone is allowed.
• This maintenance is application admission desired state and does not invoke Host relocation flow's Relocate(PlannedMaintenance) — it is not crash failover.
• Ops records desired state to the maintenance store, so the maintenance state for the same NodeId is restored after a ZoneNode restart.