a Ready owner crash ends in Unavailable — it is not automatic failover
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-message fallback (see report for rationale)
• mermaid has a self-message 'Workflow->>Workflow: Run only the next valid step' between the Events reply and ContinueOrderWorkflowRes. archify sequence messages route between two distinct participant columns; a from==to self-message was dropped as a separate arrow and its meaning folded into the ContinueOrderWorkflowRes label above.
Ready owner crash is not automatic failover
• mermaid Note over Caller,Workflow (positioned at the end): 'Ready owner crash is not automatic failover.' A Ready owner process failure ends the current operation in Unavailable; only a new attempt follows a separate policy — no new object is created on a different node automatically.