Home
# Command Center section for the Nexus CRM: handover plan
Owner of the design: Work HQ thread. Build thread: the one with the CRM repo (jg-financial-workspace). Matteo merges. Nothing is pushed or deployed without Julian's yes.
## What it is
A section in the CRM where users plan, build and complete projects and daily tasks. Layout C (Julian's pick): left sidebar, then Today with a countdown strip, then three columns. Look: Faction Glass (pale glass tiles that glow, ink text, one signal red). Cards always include a Learn more option.
## Reference build (working, tested)
Work HQ review copy: https://claude.ai/artifact/84sjXVFZVW5jo4c6dcgjvR (Today, Overview, Work, Ask, Chats). Source file: the Work HQ thread's `hq/index.html`, single React page, about 1,100 lines. Reuse the structure and the data shapes, not the code, in the CRM's own stack.
## Screens
1. Today: countdown and what's due, then three columns. Needs me (Brief, Questions for you, decisions, builds waiting on a yes, my tasks). In progress (Next up queue, Building, Ready for review, team and bot tasks). Projects (status dot, priority, next step).
2. Overview: totals (questions, decisions, waiting on yes, open tasks, builds running, projects red), work chats, bots, projects, builds, task counts by owner, latest jobs.
3. Work: Projects, Tasks (archive, never delete), Build queue. Click any item for a side panel: Visuals, Plan, Edit and work.
4. Brief me: a report plus a card walk. One card at a time, answer in one tap, Saved line with Undo, half second tap lock.
5. Ask: send a job to a named bot or builder. Draft only, Julian sends.
## Data (collections)
- projects, tasks (owner, stage, done, archived), builds (stage, spec, next, plan, shots), decisions (options with a recommended one, status Open or Decided, note), questions (text, why, options, rec, status), queue (ordered Next up), threads (work chats: title, state, needs, at), bots, inbox (jobs and replies), digest (the Brief text).
## Seed projects, in Julian's order
1. DialRush AI and the correct lead routing playlists
2. Training group preselection at onboarding, with confirmation
3. New agent and agency onboarding (licensed and unlicensed tracks)
4. NAP AI onboarding
5. The 10 AM presentation
## Hard rules to carry over
Counts, not names, for people and money. No agent name next to money. Practice data only. Draft only, Julian sends. Never delete, archive instead. No force push, no push to main. DialRush, Railway, live CRM, bank, DNS and money need Julian's own yes. Income figures carry "Illustration, not a promise of income. Results vary." No em dashes. "The Roundtable" is one word. Text 14 px or more, taps 44 px or more, soft ground (never black), one main button per screen.
## Open items for Julian (one card at a time)
- Who can see and edit it: Julian and Matteo only, or every user with their own list?
- Does each agent get a personal Today, or one shared board?
- Which existing CRM page does the sidebar entry replace or sit beside?
- Faction Glass tokens: the design system thread holds the spec. Work HQ uses a description-based version until it is shared.
## Review path
Builder on Sonnet, Fable reviewer, one fix round, Julian's yes, Matteo merges.