The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | / | Opens Rhythm at its starting address while already signed in. | CAP-PFM-CSH-004 | Only the loading view appears while access is being resolved. | test react-console:e2e/dev/initialisation.dev.spec.ts#asks the Platform exactly one thing first, and shows nothing until it is answered |
| 2 | getMySecurityContext | Waits for Platform to establish the session’s working access. | CAP-PFM-CSH-001 | The ready frame presents the person, workspace and available navigation. | observed react-console:components/console/console-shell.tsx:ConsoleShell |
| 3 | /console/{tenantId} | Arrives at the remembered workspace home. | CAP-PFM-CSH-004 | A greeting, attention items and the dashboard area appear. | observed |
| 4 | /console/{tenantId}/crm/contacts | Selects Contacts in the CRM menu. | CAP-PFM-CSH-006 | The contacts list opens and its position is represented in the menu. | observed react-console:components/console/app-sidebar.tsx:NavSectionItem |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 2 | The remembered workspace is no longer in service. | The default workspace becomes the starting context. | A persistent context notice explains the fallback and can be dismissed. | test react-console:e2e/controlled/tenant-unavailable.controlled.spec.ts#falls back to the default tenant, with a word of explanation, rather than refusing access |
| alternate | 1 | Rhythm staff begin at the starting address without explicitly entering a workspace. | The starting destination is Rhythm HQ. | The staff navigation appears; the remembered workspace remains available for later use. | test react-console:e2e/mock/staff-landing.mock.spec.ts#a staff member with a remembered tenant and a standing grant lands on /hq in HQ context |
| failure | 2 | The access request fails. | A separate failure view offers retry and sign-out. | A successful retry can establish the console. | observed |
| failure | 2 | The person has no effective access. | The refusal view identifies the signed-in address and offers sign-out. | The working frame remains absent. | observed react-console:components/console/console-boot-screens.tsx:consoleBootScreens |
| Id | Statement | Provenance |
|---|---|---|
01 | Access resolution precedes the working console view. | test react-console:e2e/dev/initialisation.dev.spec.ts#asks the Platform exactly one thing first, and shows nothing until it is answered |
02 | For a customer user, the starting address opens the remembered workspace home. | test react-console:e2e/mock/url-architecture.mock.spec.ts#the bare root opens the remembered tenant's home |
03 | A staff session started without an explicit workspace opens Rhythm HQ. | test react-console:e2e/mock/staff-landing.mock.spec.ts#a staff member with a remembered tenant and a standing grant lands on /hq in HQ context |
End-to-end policy: required: Browser coverage is needed for the access-loading boundary and the transition into a correctly identified workspace. Existing tests cover individual portions of this experience.