Atlas — Personas & Flows

Atlas is multi-persona: each user role logs in to a different default surface tuned for their job. This index lists every persona’s flow with a one-click link to the interactive prototype and the persona’s design notes.

Active flows

Persona	What they do	Interactive prototype	Design notes
Onboarding Agent	Process new rider / agent / partner applications, KYC, approvals	Open	design.md
Technical Specialist · KaaG	Commission hardware, inspect raw telemetry, diagnose faults, manage firmware, and send audited technical controls	Open	design.md
Product Manager · KaaG	Monitor the live fleet, investigate sessions, respond to alerts, and control inverters	Open	design.md
VP Product · KaaG	Read-only executive view of adoption, energy, fleet health, inspection, and rollout	Open	design.md
Inventory Manager	Stock levels, labelling/UOM stewardship, receiving with scan verification, returns, low-stock triggers to Procurement	Open	design.md
Procurement Manager	Requisition approval, orders with amendment history, vendors + lead time, BOM Procurement Orders, Atlas·Polaris sync	Open	design.md
Production Manager	Request materials for work orders with end-to-end lifecycle visibility, log consumption at point of use	Open	design.md
Retrofit Station Manager	Request materials for retrofit work, shared-demand reasoning, Rider Management scoped to the station’s retrofit pipeline	Open	design.md
VP of Facilities	Read-only executive view of the whole estate — portfolio Facility Health, regions roll-up with per-region details, every site, an Issues & SLAs queue with breach state, the Expansion pipeline and standing reports (monitor only; the PM decides and advances)	Open	design.md
Facilities Product Manager	Own the physical estate — site health, issues, requests, equipment, contractors, and the expansion decisions: read the Location Acquisition Manager’s case reports, accept or send back submitted locations, and advance projects to handover (Super Admin)	Open	design.md · PRD.md
Regional Facility Manager	Region admin (South-West) — clusters + facilities oversight, region issue queue with review-and-forward-to-PM, requests, equipment, contractors; standards read-only, in a site’s record	Open	design.md
Facility Manager	Cluster admin (Ogun) — cluster health, issues, requests, equipment, contractors; standards read-only and acknowledged from a site’s record; requests forwarded to the PM	Open	design.md
Station Manager	Single station (Ijoko) — station dashboard: health-check, open issues, equipment condition, personnel; files issues, acknowledges SOPs	Open	Core · full build to follow
Location Acquisition Manager	Expansion (South-West) — interactive locations map, PM requirement SOPs, SOP-tied case reports with photo/video, and Projects tracking accepted locations Leased → Design → Construction → Handover with the lease/landlord record and renewal reminders; reports to the PM and VP	Open	design.md · PRD.md
PM, Battery	Battery PM command-and-control for the Tricycle Hardware unit — fleet-wide KPI strip, fleet composition by status + battery-to-tricycle ratio per station, severity-ordered fault queue with Acknowledge, searchable fleet table opening to a full battery detail page (BMS-estimate vs quarterly audit-grade SoH kept separate)	Open	PRD.md

Planned

These personas exist in Atlas’s product space but don’t have a canonical interactive flow yet. Drop one into a new flows/<persona>/ folder when ready and add a row above.

Persona	Default surface concept
Operations Dispatcher	Live fleet view, station ops, dispatch queue
Customer Support Agent	Case management, conversation thread, SLA timers
Fleet Manager	KaaG telemetry dashboard, asset health, deployment heat-map
Finance / Billing	Wallet flows, settlement, ledger reconciliation
Admin	User and role management, RBAC, audit log

Sub-categories

Atlas flows are grouped in the /flows sidebar under these sub-categories. Every new Atlas flow must be assigned to exactly one — set category on its entry in site/src/data/products.ts:

`category`	For
`onboarding`	Rider/agent acquisition, conversion, post-retrofit onboarding
`swap`	Swap operations, PM/VP/CPO dashboards, swap support
`inventory`	Inventory, bundles, battery identity/lifecycle
`support`	Field support, CFSM, and anything that isn’t the above
`telemetry`	RADR telemetry administration and KaaG executive dashboards
`facilities`	Facilities estate management — sites, issues, requests, equipment, contractors, SOPs
`tricycle-hardware`	Tricycle Hardware unit — battery PM, maintenance/reliability, production

If it isn’t obvious which sub-category a new flow belongs to, ask before placing it.

Adding a new flow

mkdir -p products/atlas/flows/<persona-slug>
# 1. Drop the interactive HTML at products/atlas/flows/<persona-slug>/index.html
# 2. Author products/atlas/flows/<persona-slug>/design.md following
#    the template in products/atlas/flows/onboarding-agent/design.md
# 3. Add a row to the table above.
# 4. Run `cd site && npm run sync` (or restart `npm run dev`).
# 5. In site/src/data/products.ts, set the flow's `category` to one of
#    onboarding | revenue-assurance | swap | inventory | support | telemetry | facilities.

The sync script symlinks flows/ into site/public/products/atlas/flows/ automatically, so the prototype is reachable at https://design.rechaj.com/products/atlas/flows/<persona-slug>/ as soon as the file exists.