Site map + IA
The full site map: a tree of the 11 clusters (0 to 11) plus per-node cards, each with its number X.Y, type, what it includes, and transitions. This is the detailed body that expands the base Concept map. States and page copy live on the individual node pages; here we lay out the whole product surface, cluster by cluster. See also the Flows.
Cluster tree
The twelve clusters and how the primary journey threads through them: public acquisition into auth, auth into the one-time onboarding wizard, the wizard into the operator home, and from the Dashboard out to Programs, Team, the Owner path, and Settings. The owner surface and the employee check-in branch off Team and the Owner path. System nodes hang off the global shell.
flowchart TD
c0id["0 Global shell + home"]
c1id["1 Public marketing"]
c2id["2 Authentication"]
c3id["3 Onboarding"]
c4id["4 Dashboard + pulse"]
c5id["5 Programs"]
c6id["6 Team"]
c7id["7 Owner share + upgrade"]
c8id["8 Settings"]
c9id["9 Owner surface"]
c10id["10 Employee check-in"]
c11id["11 System + global"]
c0id -->|public| c1id
c0id -->|auth| c2id
c2id -->|"sign up"| c3id
c3id -->|finish| c4id
c4id -->|Programs| c5id
c4id -->|Team| c6id
c4id -->|Owner| c7id
c4id -->|Settings| c8id
c7id -->|"invite owner"| c9id
c6id -->|"invite link"| c10id
c0id -.->|system| c11id
0 - Global shell and home
Public and all roles. The per-page template exemplar plus the canonical global components (nav, footer, privacy disclosure, program card, dialog shell, canonical lists), each defined once and referenced everywhere.
1 - Public marketing and acquisition
Public pages. Nodes 1.1 to 1.6 were registered from the footer (0.2) at Step 3, per discover-as-you-go; they serve the existing Main and trust jobs, not new jobs.
2 - Authentication
Public to operator. Closes no job on its own but gates every operator job (Main, J1, J2, E1); never a dead-end.
3 - Onboarding, guided first-run wizard
Linear, time-budgeted under 5 minutes. Sequential flow depth, not navigational depth. Runs once, not reachable from global nav afterward.
4 - Dashboard and pulse, operator home
The operator home. The recurring aha, 1 tap from login: the pulse signal (score + interpretation + suggested next action).
5 - Programs
Browse, pick, manage, and set up the check-in. The core "what do I run" job (Main + J6 + item 2), entered repeatedly.
6 - Team
Invite and participation aggregate. Entered on every new hire; the invite / roster surface (Main + item 3 + item 10).
7 - Owner share and upgrade, operator-facing
The prove-it-works and paid-conversion path (J1 + J5 + S2 + item 8). Fires from a positive milestone (F3).
8 - Settings, operator utility
Noindex. One shell whose section list mirrors nav; a corner utility entry, not a job tab.
9 - Owner surface, aggregate-only, secondary
Under 2 minutes, one read. No nav tabs by design; a single aggregate dashboard for the secondary persona.
10 - Employee check-in, near-anonymous, third-party, mobile
Linear, under 30 seconds, no account for the first check-in. A near-anonymous flow for the third-party persona (J3 + J4).
11 - System and global nodes
Fleshed at Step 6, grounded in law. The system surfaces that apply across all roles.