CreateDeliveryReq accepted → Attempt=1 offer → accept → push in the order Assigned, Accepted, PickedUp, 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.
Order and verification
• Confirm DeliveryStatusNotify arrives in the order Assigned, Accepted, PickedUp, Delivered, and that each payload's DeliveryId matches the subscription.
• Recording and pushing status events in order is an Application sample policy and does not mean the Framework provides a general channel-wide global order.
• While waiting for the courier's response, the Dispatch handler doesn't occupy an execution turn.