Handoff · 3 of 4 · journeys

Journeys, screens and automation events

The three end-to-end journeys exactly as they run in the prototype (Scenarios → Start journey). Each step lists the screen ID from the export package, so you can open the matching PNG. All three journeys pass as automated end-to-end tests at 1440 px. The export runs then repeat each journey at 768, 390 and 360 px and capture every state. Page journey IDs point to the same screen as captured in another journey.

Client actsWeblerr actsSystem (simulated)

{{l.title}}

{{l.sub}}
{{s.actor}}{{s.t}}{{s.id}}

Exception states (Scenarios → Open state)

{{e.id}}
{{e.t}}
{{e.d}}

Automation and notification events (simulated)

EventWhat happensChannelRetry / duplicate handling
{{e.name}}{{e.what}}{{e.ch}}{{e.idem}}
Simulated only. No payment provider, email service, staging host or WordPress integration is connected. The prototype’s Events panel logs each event and marks duplicates it ignored. The channel split (important actions: in-app + email; routine: in-app only) is an assumption to confirm.