Back to Dashboard
User Flow dashboard/src/participant
This is the participant-facing path from first visit to completed session. It is written as an operational flow: what the user sees, what AGS records, and what happens when the happy path breaks.
Primary participant path
1. Open AGS participant app
The participant starts at
/ags. AGS checks for a valid participant token. Returning participants can continue without re-entering details; new participants enter onboarding.2. Choose language and read orientation
The participant selects Kiswahili, Kiluhya, or English. The app explains that AGS gives support during a task and records interaction signals, not direct credentials.
3. Enter participant details
The participant provides phone number, age group, digital literacy, prior web-use status, font preference, and self-efficacy. The phone becomes an HMAC token; the raw phone is not stored.
4. Consent gate
Consent must be explicitly accepted before any telemetry can be written. If consent is missing, the events API rejects interaction telemetry.
5. Study ID and session token
AGS reveals the assigned
AGS### study ID and stores a participant JWT locally. This supports return visits without passwords or email recovery.6. Select service or assigned task
The participant chooses the task/service template. AGS resolves the template, target site, schema version, preferred capture mode, language content, and whether extension support is recommended.
7. Start session and calibrate
The server creates the session, resolves condition server-side, initializes Redis context, and records three baseline interactions. Governance cannot intervene until calibration clears.
8. Work through task steps
Each click, pause, help request, completion, typing/touch signal, or navigation event is sent to the pipeline. The user sees only normal task guidance and any AGS support that governance allows.
9. AGS adapts or stays quiet
For each event, AGS normalises signals, computes readiness, runs governance, and either withholds, delays, reassesses, or delivers a tooltip, guided prompt, reassurance, walkthrough, or rest prompt.
10. Complete, abandon, or recover later
Completion records session outcome and routes to the post-session survey. Abandonment records reason when available. Offline events queue locally and replay with idempotent event IDs when the connection returns.
Decision points
| Moment | Question AGS answers | Possible path |
|---|---|---|
| Returning participant | Is there a valid token or phone reauth? | Resume directly, reauth by phone, or start enrollment. |
| Consent | Has consent been recorded? | Proceed to session only after consent; reject telemetry before consent. |
| Capture mode | Can this task run through proxy/iframe? | Use proxy, Service Worker proxy, extension handoff, limited capture, or fallback notice. |
| Calibration | Are three baseline interactions complete? | Keep collecting baseline; governance withholds until calibration clears. |
| Runtime support | Is the participant coping, struggling, asking for help, or fatigued? | Withhold, delay, reassess, or intervene at L1-L3/rest. |
| After support | Did the intervention help? | Log improved/no-change/worsened, update cooldowns, and record adaptation failures when needed. |
What the participant should not see
- The study condition: control, governed adaptive, and always adaptive must look identical.
- Raw readiness scores, governance rule names, confidence gates, or experiment internals.
- Researcher dashboard views, exports, audit logs, or participant lists.
- Technical failure details beyond plain recovery guidance.
Evidence written during the flow
Participant/session setup
users, sessions, consent status, language, device type, condition, template, and Redis session context.Interaction loop
event_signals, normalised sub-scores, enrichment flags, readiness profiles, and governance decisions.Support delivery
adaptation_action, content source, intervention level/subtype, language, cooldown, and outcome window.End state
Completion, abandonment, post-session survey, adaptation failures, and export-ready session summaries.