Journey Model

The Journey Model is the cross-cutting layer that frames every per-role user journey. It captures the rules, states, exceptions and acceptance bars that every role must obey.

Per-role journeys (Originator, Designee, Operator, etc.) live under User Journeys and instantiate the model defined here.

Pages

Page	What it defines
Governing Assumptions	The five rules every journey must obey
Master Journey	The end-to-end flow from Originator to Designee, stage by stage
State Model	The canonical state machine spanning the whole lifecycle
Exception Journeys	Cross-cutting patterns for unreadable phone, offline capture, mismatch, designee unavailable
Acceptance Criteria	The 15-point bar for what "done" means for a full Originator-to-Designee journey
Prompt Vocabulary	The low-literacy, action-based language used in operator-facing prompts

Source

This section translates Kaya Sync — User Journeys: Originator to Designee (Nenyi, May 2026) into the internal plan.