The deadline expires, A's attempt=1 is marked expired and Reassigned is pushed → re-offered to B → Delivered
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.
Deadline expiry and stale decision (source Note and following paragraph)
• Source `Note over D`: deadline expires and attempt 1 is marked expired — the Dispatch sweeper marks the current record Expired and selects B as the next candidate. (archify sequence doesn't render notes, so this is preserved in the third message label and this card.)
• A decision from A that arrives after attempt 2 starts is recorded as a stale decision and has no status effect. If no candidate remains, Dispatch records Failed and sends the terminal status.
Reassignment path
• Tracking sends the status push to the CustomerActor, which pushes to the bound CustomerGateway session (same as §7.1 and the actual sample code sendToActor — the source mermaid omitted CustomerActor; corrected against the code).
• Reassignment order check: confirm the order Assigned, Reassigned, Accepted, Delivered and that the courier is B after Accepted.