Member Onboarding Journey
A member creates their profile and starts their first triage session.
Sequence Diagram
API Reference
| Step | Service | Method | Path | Auth | Response |
|---|---|---|---|---|---|
| Get token | Keycloak | POST | /realms/olly/protocol/openid-connect/token | None | access_token |
| Create party | policy-admin | POST | /parties | Admin JWT | 201 {Locator} |
| Get party | policy-admin | GET | /parties/{locator} | Admin JWT | 200 {Locator, Type, FirstName} |
| Start session | triage | POST | /sessions | None (local dev) | 201 {session.locator, next_question} |
| Respond | triage | POST | /sessions/{locator}/respond | None | 200 {next_question} or {recommendation} |
/parties/{locator} | — | Not implemented — party left in place after test |
Notes
- Triage sessions do not require auth in the local dev configuration (JWT middleware disabled for triage in test env). See
triage_test.gofor precedent. next_questionmay benullif no LLM is configured — the test accepts this gracefully.- The member app stores the health profile (age, activity level, sleep) client-side only; no backend API call is made for this data in Phase 1.