Atlas MR v3 — Current State
What the Madison Reed Atlas instance has today.
Overview
The MR Atlas (v3) is the live, API-backed instance built from the MR department brain's markdown files. It's a reduced surface compared to the full Northrun reference (12 deliberately chosen routes vs. 33), focused on making the People team's operating structure visible.
What's populated
| Entity type | Count | Quality | Notes |
|---|---|---|---|
| Departments | 11 | Full | Executive, People & Culture, Technology, Data & Analytics, Finance/IT, Marketing, HCB Operations, Supply Chain, Amazon/Direct/Wholesale, Enterprise PMO, Franchise (future) |
| Teams | 18 | Full | 4 cross-functional, 5 Marketing sub-teams, 3 HCB, 2 Color Crew, 2 Finance, Supply Chain, Amazon/Direct/Wholesale |
| Roles | 54 | Full | 41 current + 13 proposed/future state. Heavy coverage of C-suite, Color Council seats, and future profiles (Product Engineer, Platform Engineer, VP Franchise) |
| Mandates | 175 | Extensive | 80 leadership/governance mandates + 95 LABS-CSV team-member mandates spanning operations, automation, and the 3-phase People AI roadmap |
| Decisions | 8+ | Full | 5 MVO "Ask" gates (Zapier org-wide, HR chatbot, Shlanda role redesign, HCM platform eval, MVO endorsement) + 3 ratified decisions from Elena meeting |
| Artifacts | 49 | Full | 5 canon artifacts (Charter, MVO, Proposal, Academy, 90-Day Plan) + 44 working artifacts (trackers, audits, planning docs) |
| Conflicts | 5 | Full | Documented contradictions (mostly resolved); e.g., Council sponsor identity, Shlanda's name variants |
| People | 0 | Empty | Intentionally empty; CMPRSSN partners are engagement counterparties, not org members |
What's empty or sparse
- People — no person records loaded (by design; the org chart tree won't render)
- Workflows, Agents, Skills, Tools — referenced in page definitions but data population status unclear. These are the surfaces most relevant to your embed.
Data sources
Most Atlas data is sourced from these documents:
| Source | What it feeds |
|---|---|
| GOV BOARD CHARTER | Governance structure, Color Council charter, role definitions |
| MVO Framework | Strategic AI roadmap for the People function, phase definitions |
| AI Transformation Proposal | C-Team strategic doc, department-level mandates |
| LABS-CSV | Ranked use-case master list (~95 rows), horizon classification (H1 quick wins, H2, H3) |
| CMO-TRACKER | Per-team AI Transformation Tracker for Marketing org |
| Elena discovery notes | Technology decisions, stack choices |
Each entity carries a confidence rating (HIGH, MEDIUM, LOW) and surfaces open questions for ambiguous fields.
Routes available
The MR v3 instance defines 36 routes in its PAGE_NAMES config. The key ones for your work:
Organizational structure:
departments, teams, roles, people, org
Work governance:
mandates, workflows, projects, programs
AI operations:
agents, skills, tools
Observability:
signals, activity, decisions, logs, conflicts
Planning:
objectives, kpis, milestones, okrs, goals
Economics (CMPRSSN diagnostic only):
financials, impact, tokens, outcomes, maturity
Governance:
permissions, policies, canon, vendors, accounts
What needs to happen
The most impactful additions for your embed:
- Populate workflows — map the People team's actual workflows (onboarding, job changes, leave, compliance) as Atlas workflow entities with steps, owners, and AI-touch levels
- Populate agents — register the live agents (pay reconciliation, minimum wage monitor, leave agent) with their mandate holdings, stage, and cost
- Add embed mandates — the scope document defines clear accountabilities for your August-October cycle. These should be Atlas mandate objects (see embed-mandates.md)
- Connect mandates to workflows — link each mandate to the workflows it touches, so the transfer from manual to automated is visible