Appearance
State Model
The canonical state machine that spans the whole Originator-to-Designee lifecycle. Engineering and operations should align around this model — every per-role journey moves through these states.
State progression
| State | Trigger | Owner | Allowed next state | Block condition |
|---|---|---|---|---|
| Draft | Originator starts transaction | Originator / Facilitator | Awaiting Origin Evidence | Missing designee phone number |
| Awaiting Origin Evidence | Cargo prepared | Originator / Operator | Origin Validated | Phone number not visible |
| Origin Validated | Origin scan PASS | System | Awaiting Pickup | OCR / phone mismatch |
| Awaiting Pickup | Operator assigned | First-Mile Operator | First-Mile Custody Active | Operator / device not verified |
| First-Mile Custody Active | Pickup scan PASS | First-Mile Operator | Awaiting Hub / Mid-Mile Handoff | Count mismatch |
| Awaiting Handoff | Operator reaches hub | First-Mile + Receiver | Mid-Mile Custody Active | Missing dual scan |
| Mid-Mile Custody Active | Mid-mile receiving scan PASS | Mid-Mile Operator | Awaiting Relay or Last-Mile Assignment | Geo / time anomaly |
| Relay / Disaggregation Pending | System recommends split | Relay Actor / Supervisor | Relay Complete or HOLD | Unauthorised relabel |
| Awaiting Last-Mile Assignment | Cargo at destination hub | Hub / System | Last-Mile Custody Active | No eligible operator |
| Last-Mile Custody Active | Last-mile receiving scan PASS | Last-Mile Operator | Delivery Pending | Cargo mismatch |
| Delivery Pending | Operator reaches designee | Last-Mile Operator / Designee | Delivery Validation Pending | Designee unavailable |
| Delivery Validation Pending | Final evidence uploaded | System | Delivered / HOLD / FAIL | Offline unsynced evidence |
| Delivered | Integrity PASS | System | Settlement Eligible | Dispute raised |
| Settlement Eligible | Validated delivery event | Settlement Rail | Payout Released | Finance / legal hold |
| HOLD | Anomaly detected | Reviewer | Resolved / FAIL / Recapture | Evidence insufficient |
| FAIL | Integrity failure | Reviewer / System | Dispute / Liability Assignment | None |
| Closed | Delivery and settlement complete | System | Archive / report | Post-delivery dispute window |
How to use this model
- Engineering: implement as the authoritative state machine in the order/container service.
- Operations: every dashboard, alert and exception tool should reference these states by name.
- Per-role journeys: each role's actions should map onto state transitions in this table.
Source
Kaya Sync — User Journeys: Originator to Designee, §5.