The Trading Floor — Overview & Desk Pipeline

~7 min – the hedge-fund-style desk that unifies live Team Pulse, the execution blotter, and the full team workspace — theses, set-ups, executions, guardrails, allocations, and attribution — under one sidebar section

You've mastered solo journaling, AI Council, CharterElite, What-If, and Monte Carlo. Now open The Trading Floor — the collaborative layer for discretionary teams who lose edge in hand-offs.

This is not three separate products. Sidebar → The Trading Floor is one collapsible section with nine sibling routes sharing selectedTeamId (Zustand team store). Team Pulse is the default operational view; the rest is the workspace pipeline plus risk, capital, and admin.

It answers: "How does our desk move from idea → structured plan → live position → risk enforcement → capital attribution — without dropping context?"

Where to Find It

• Sidebar → The Trading Floor (collapsible section)
• Onboarding home: `/team/overview` — create/select teams, dashboard snapshot (not in the nine tabs but required first)
• Default ops entry: `/team` or `/team/pulse` — Team Pulse
• Sibling routes: `/team/theses`, `/team/setups`, `/team/executions`, `/team/guardrails`, `/team/allocations`, `/team/portfolios`, `/team/performance`, `/team/team`
• Audit trail: `/team/audit-log` (linked from guardrails/settings context)

Desk Pipeline (End-to-End)

1. Team Overview (`/team/overview`) — create first team or switch teams; dashboard shows theses/set-ups/executions counts, Best Ideas / Best Execution attribution, quick links
2. Team (`/team/team`) — invite members, assign roles (owner, admin, lead, trader, analyst, viewer)
3. Portfolios (`/team/portfolios`) — create team trading accounts (exchange, live/paper/demo, risk method)
4. Guardrails (`/team/guardrails`) — team-wide limits, alerts, pause trading
5. Theses (`/team/theses`) — research ideas: regime, sizing, workflow (draft → pending → active)
6. Set-ups (`/team/setups`) — structured plans under active theses; 3-step execute dialog
7. Team Pulse (`/team`) — live P&L, blotter, watchers, leaderboard, allocation preview, stress test, correlation
8. Executions (`/team/executions`) — full book with Live / Closed / Breached filters
9. Allocations (`/team/allocations`) — per-trader R caps, rebalance history, dynamic rules
10. Performance (`/team/performance`) — desk scorecard by period

Shared Context Everywhere

• Team selector chips when multiple teams exist
• TradingPausedBanner + GuardrailViolationBanner on Set-ups, Executions, Allocations, Guardrails
• BuyingPowerCard on Set-ups, Executions, Team Pulse
• Permissions via `usePermissions` — create thesis/setup (analyst+), execute (trader+), guardrails/invite (admin+)

Role Cheat Sheet

| Role | Create thesis/setup | Execute trades | Guardrails / invite | |------|---------------------|----------------|-------------------| | owner | Yes | Yes | Yes | | admin | Yes | Yes | Guardrails, invite | | lead | Yes | Yes | Settings update | | trader | No | Yes | Watcher, comments | | analyst | Yes | No | Comments, vote | | viewer | No | No | View + comment |

Quick Workflow — First Desk Setup

1. Open `/team/overview` → Create Your First Team
2. Team tab → invite traders and analysts with correct roles
3. Portfolios → create at least one team portfolio (paper or live)
4. Guardrails → set daily loss, exposure, per-trade risk %, alert channels
5. Theses → create and activate a thesis
6. Set-ups → create set-up → execute → position appears on Team Pulse blotter
7. Weekly: Performance + Allocations for attribution and capital review

Quick Reality Checks

• No team? → Everything empty — start at Team Overview
• Can't execute? → Thesis not active, guardrails breached, or trading paused
• Blotter empty after execute? → Refresh Team Pulse; check correct team selected
• Capital request snackbar only? → Capital request UI exists; full API workflow may still be expanding

Next: Team Pulse Guide — live desk command center.

Or open Team Pulse right now. If you have an open book, you should see live P&L and the blotter. If not, run the pipeline above once. Your desk only works when the chain is connected end-to-end.