Governing Assumptions

These five rules control every user journey in Kaya Sync. Any design that contradicts them is wrong.

Rule	Why it matters
No custody event, no payout	Every operator-facing journey must end in a verified event, not a verbal claim.
Designee phone number is the cargo anchor	The physical cargo identifier is the designee phone number. QR codes and printed labels are not assumed.
Low-literacy execution	Interfaces must use icons, voice prompts, guided capture, traffic-light states, numeric confirmation and minimal text.
Offline-first field reality	Capture may happen offline, but settlement only happens after server-side validation.
Event-driven governance	Each meaningful action must generate an event: order creation, scan, upload, integrity result, custody transfer, payout hold or release, dispute, override, relabel or risk flag.
Settlement is a consequence, not a button	The system releases or holds payout based on validated delivery and custody evidence, not operator request alone.

Source

Kaya Sync — User Journeys: Originator to Designee, §1.