The Front Door
Citadel OS — the firm-wide operating system
How Citadel Financial Planning thinks, builds, runs, and delivers — captured once, used by every advisor, durable as the firm grows.
Citadel OS — How It All Fits Together
The Brain authors + builds the source of truth — four silos run the work — the Advisor Dashboard delivers + maintains it. Three bridges connect cross-silo flows. Click any platform or subproject to explore.
The Three Bridges — cross-silo connectors
click a bridge to expand · these are real data-sync flows, not metaphors
1 Training · Advisor Development ↔ Book & Business
2 Data Sync · Book & Business ↔ Client Management
Accounts table across them.
3 Investment Integration · Client Management ↔ Investment Management
Pillar drift — v7.5 cornerstone → ADR-00 master outline For lock-and-prune review
The visual above uses pillar names from ADR-00 Master Outline §1–§6 (the locked architecture root). The original v7.5 cornerstone the team last saw used some different names. Items below need yes/no tomorrow:
| AD Silo | v7.5 + ADR-00 already agree on all 4 pillars: Employee Onboarding Ramp · Advisor Knowledge Bank · Advisor Training Platform · Advisor HR. No drift. Note: "Advisor Training Platform" is named as a pillar AND as the Platform LAYER (ADR-04 §3a). Tension to resolve. |
|---|---|
| B&BM Silo | Material restructure. v7.5: Org Structure & Roles · Advisor-Team System (Bk 1/2/3) · Proactive Client Mgmt · Book Tracking & Reporting · Compliance & Records · Advisor Program & Comp. ADR-00: Tech Stack · Task & Project Management · Business Data & Analytics · Team Management · Proactive Management Systems · Compliance & Records. Visual above uses ADR-00. v7.5 mapping: Org Structure + Advisor-Team + Comp → Team Management (sub-pieces). Book Tracking → Business Data & Analytics. Tech Stack + Task/Project Mgmt are new top-level pillars in ADR-00. Lock the restructure or revert? |
| CM Silo | v7.5: Content Library · Onboarding System · Ongoing Client Mgmt + Events · Planning Engine. ADR-00: Content Library · Onboarding System · Ongoing Client Management (Events nested inside) · Planning Engine. Cosmetic — Events still part of OCM, just not in the name. Recommend lock ADR-00. |
| IM Silo | v7.5 + ADR-00 agree on all 6 pillars: Citadel Investment Principles · Research & Strategy · Portfolio Management Process · Custom / Tactical Strategies · Alternative Investments · Tracking, Trading & Ops. No drift. "Citadel Investment Principles" final name still pending — 5 candidates open (Carson session item #4). |
| Bridges | Three bridges locked in ADR-04 §4 — names + endpoints unchanged from v7.5: B1 Training (AD↔B&BM) · B2 Data Sync (B&BM↔CM) · B3 Investment Integration (CM↔IM). |
The Unifying Motif · §0.5
The Scoreboard Doctrine
Why every silo exists in the same shape — and what makes the OS self-accountable.
| Silo | What the scoreboard measures |
|---|---|
|
Advisor DevelopmentInternal
|
Knowledge mastered · trainings completed · growth-path progress · 6-month retention checks · aptitude scores · knowledge-bank usage |
|
Book & Business ManagementInternal
|
Goal progress · proactive client outreach · overdue meetings · late tasks · workflow health |
|
Client ManagementExternal
|
Real client outcomes — net worth growth · debt paydown · advice taken · TICC roll-up |
|
Investment ManagementExternal
|
Allocation tracked + rebalanced · returns history · qualified vs non-qual · gains / dividends / interest (standardized formats) |
| Meta-Scoreboard — the Advisor Dashboard surfaces every silo's scoreboard in one unified view | |
Second Structural Axis
Internal / External — who each silo serves
On top of the Brain → Silos → Dashboard architecture, the four work-doing silos split into two pairs by audience. Internal silos serve the team and owner; External silos serve the client.
Internal · Advisor + Owner Experience
How the team executes the system
The infrastructure that makes Citadel runnable, trainable, and durable as the firm grows. Most of this trust is invisible until something breaks — and that is exactly the point.
External · Client Experience
What clients see, experience, learn
The visible Citadel difference — the planning relationship, the investment management, the teaching, the cadence. Where the Pyramid of Trust gets delivered meeting by meeting.
The WHY underneath every other WHY
The Pyramid of Trust
Every Citadel system, deliverable, and behavior traces back to one core principle: build trust with our clients. Not "deliver returns." Not "produce plans." Those are means. Trust is the end.
- Competence — they trust you know things
- Execution — they trust you do what you say, when you say it
- Character — they trust your integrity
- Care — they trust you actually care about them as a person
When all four are present, the advisor becomes indispensable. The client is no longer comparison-shopping — they stay because of the relationship and the track record.
Silo 0
The Brain
The wrapper. Citadel's DNA, the Brand & Content Engines, and the Capture / Knowledge Catalog that feed every work-doing silo. Ongoing function: Build.
Knowledge Half
Captures everything we know, organizes it, makes it retrievable.
- Capture System (RCE-tagged voice protocol)
- Knowledge Catalog (the searchable substrate)
- Glossary of terms-requiring-base-explanation
Creation Half
Turns knowledge into branded deliverables at firm voice.
- Brand System (voice + visual identity)
- Content Engines (the production lines)
- The DNA above it all — Pyramid + Meta-Principles + Distinctives
Cross-silo connector layer
The Three Bridges
Bridges are real data-sync flows between silos — not metaphors. Each one moves a specific kind of value across a specific seam.
BRIDGE 1 · TRAINING
AD ↔ B&BM
AD's knowledge base and training teach the team how to run B&BM systems and execute CM playbooks. Owner heads → documented, assignable, trackable system.
BRIDGE 2 · DATA SYNC
B&BM ↔ CM
The Master Source workbook holds canonical client + account data. Plan Engine consumes it for client deliverables; book-wide trackers consume it for analytics. One update; same source; different audiences.
BRIDGE 3 · INVESTMENT INTEGRATION
CM ↔ IM
IM's education, strategies, and tracking integrate per household into the CM planning process. Planning is standardized; investment implementation is per-household-unique.
Four work-doing silos
Where the firm actually runs
Each silo is a coherent zone of activity with its own Core Systems, named Platform, and Deliverables. Click any silo for the full spec.
The bottom wrapper
The Advisor Dashboard
The unified delivery surface where all four silos meet the advisor. Same modules surface differently for owners (build / stage / assign) and advisors (consume / log / track). Ongoing function: Maintain.
Owner view
Build · Stage · Assign
- Versioned templates + content authoring
- Assignment + progress oversight
- Cross-silo audit + analytics
Advisor view
Consume · Log · Track
- Daily task-anchored surface
- Client-specific deliverables and trackers
- Personal training progress + Answer Bank lookup
How Citadel operates
Six Meta-Principles
Cross-domain operating rules that sit above brand voice, above silo logic, above any specific deliverable.
Hide the Complexity, Do the Work
The team absorbs complexity so the client doesn't have to.
Fewer Moving Pieces
A dollar is a dollar. Collapse buckets. Hide accounts. Less surface, more leverage.
Forecasting Integrity
If we say it, the tracker can show it. No untracked claims.
Annual Reset
Plans re-baseline yearly. Compounding mistakes never get past one cycle.
Behavior as Strategy Prerequisite
Advanced strategies require behavioral readiness. Education comes first.
Owner-Mastery by Commitment
If explanation quality matters, do it yourself. Don't outsource the hard part.
How Citadel thinks differently
Five Distinctives
The differentiators that make a Citadel piece of work distinguishable from a generic advisor's piece on the same topic.
Extraordinary Comprehensiveness
Pressure-test every recommendation across seven domains before it leaves anyone's mouth.
Atlas Point
The client always knows where they are on the map and what the next step is.
Signature Branded Programs
Cash Management Program is the canonical example. Same words, same slides, 8+ years.
Active In-House Management
We don't subscribe clients to preset portfolios. Brenan researches, decides, executes.
High-Conviction Options Discipline
Covered calls + cash-secured puts. Low volume, high conviction. Defined-risk only.
Reconciliation Queue
What's still open
Q-01 · 4-layer vs 5-layer anatomy — needs explicit Brenan + Carson sign-off. Currently treated as both-valid-at-different-fidelities (4-layer for team-facing; 5-layer for operational accounting). Not blocking; carries forward.
All other ADRs locked or substantively stubbed. Carson-session items tracked on PM Dashboard tab.
Tab 2 · Locked & Synced Spec
Silo Specs — the team's source of truth
Each silo is rendered with the standard 4-layer anatomy (ADR-04): Mission/Vision · Playbook · Platform · Deliverables. The team builds against these specs; updates flow back here.
Client Management Silo
Where plans become real for clients. The full client lifecycle — content, onboarding, ongoing relationship, planning engine — and where the Pyramid of Trust gets delivered meeting by meeting. CM produces every customized deliverable a household sees.
The 4-layer anatomy
Mission / Vision
A comprehensive, customizable, scalable client-planning system. No cookie-cutter solutions. 5-year scalability test: same base experience regardless of team size.
Playbook · 4 Core Systems
- Content Library
- Onboarding
- Ongoing Client Mgmt (TICC + QRG)
- Plan Engine
Tools / Systems · two-cell split
Plan Engine at CM/Build (creation infrastructure) + Approved-Tools Perimeter at CM/Platform proper.
Client Deliverables
TICC, QRG, custom education manuals, onboarding map, Cash Mgmt Program — every household-facing artifact.
Primary trusts built (Pyramid)
All four. CM is the silo where the Pyramid gets delivered meeting by meeting — Competence (Atlas Point + Comprehensiveness), Execution (TICC + QRG cadence), Character (fiduciary discipline in every plan), Care (Events & Gifting + the small moments).
Advisor Development Silo
Where new advisors become master advisors — and where existing advisors stay current as the firm evolves. Take someone from "first day, never worked at Citadel" to operating at firm standard, with the science of operations and the art of advisory work both teachable and trackable.
The 4-layer anatomy
Mission / Vision
Take a hire from baseline to advisor-ready. Operations = Science · Advisor = Art. Two manuals, two rhythms — not a merged playbook.
Playbook · 4 Core Systems
- Employee Onboarding
- Operations Manual
- Advisor Playbook
- Knowledge / Answer Bank
Tools / Systems
Training Platform with the two-tier access model — owners build, advisors consume, same modules, different views.
Team Deliverables
Advisor-ready team members + audited operations + a live Answer Bank + 12-month development ramp.
Book & Business Management Silo
How the firm runs the firm. Org structure, the tech stack, the multi-book / advisor-team system, proactive client management, compliance, and the comp design that turns every advisor into an owner. The trust this silo builds is mostly invisible until something goes wrong — and that's exactly the point.
The 4-layer anatomy
Mission / Vision
The firm-running infrastructure that lets Citadel scale relentlessly (40+ households/year) without losing operational integrity.
Playbook · 6 Core Systems
- Tech Stack
- Task & Project Mgmt
- Business Data & Analytics
- Compliance & Records
- Team Management
- Compensation Design
Tools / Systems
Business Platform — 4 trackers, Book Dashboard, Owner P&L (4-bucket), Master Source workbook (Bridge 2 anchor).
Business Deliverables
Operational integrity + audited compliance + the proactive triggers that surface client opportunities (the April-2025 Roth-funding story).
Investment Management Silo
How money gets managed at Citadel — and the silo where Distinctives #4 (Active Management) and #5 (High-Conviction Options Discipline) actually operate. Citadel doesn't subscribe clients to preset portfolios. Brenan personally manages: researches, decides allocations, picks funds, builds every model, executes every rebalance.
The 4-layer anatomy
Mission / Vision
Active, in-house investment management at scale. Research daily, decide allocations, pick funds, build every model — and be able to explain every decision right or wrong.
Playbook · 5 Core Systems
- Investment Principles
- Model Sets (3×6)
- Custom IM Program
- Options Discipline
- Book-Level Review
Tools / Systems
Investment Platform with cohesive-trade reconciliation (option leg + stock leg = ONE trade) and the 3-branch operating lens.
Client Deliverables
Per-household allocation, executed trades, option overlays — and a defensible explanation for every call.
Tab 3 · Forward-looking workstreams
Subprojects
Each subproject has a master visual + master outline. As work ships, status flags and outline content stay synced here — the team can check work against this surface without hunting through folders.
Cash Management Program · Manual v0.4 patches
The CMP is Citadel's longest-running, most-canonical signature program (Distinctive #3) — same words, same slides, 8+ years across two firms. Manual v0.3 is published and live. The v0.3 → v0.4 patch round closes 5 minor brand-skill audit findings in place (no structural rebuild).
| Status | v0.3 shipped · v0.4 = 5-issue in-place patch · IM-PLACE PATCH, not rebuild |
|---|---|
| Owner | Brenan (program designer + canonical voice) |
| Source ADR | ADR-09 (Cash Management Program) · LOCKED |
| Why it matters | Canonical worked example for ADR-03 Distinctive #3 (Signature Branded Programs). Every future signature program traces back to this shape. |
| Live URL | pub-1622f...r2.dev/cash-mgmt-manual-2026-05-21/ |
Master visual — what CMP actually delivers
v0.4 patch list (5 issues, in-place)
Patch 1 · Voice consistency
3 paragraphs where present-tense slipped to "would" — restored to Citadel's confident-active voice.
Patch 2 · "A dollar is a dollar" callout
Promote this from buried prose to a sidebar so the Meta-Principle #2 connection is visible.
Patch 3 · CMA diagram refresh
v0.3 diagram is text-only; add the 3-bucket visual matching the cornerstone style.
Patch 4 · Range-mechanics example
Add a worked $15K/$25K floor-and-ceiling example to make the abstraction concrete.
Patch 5 · LPL compliance footer
Standard LPL disclosure block needs to match the current 2026 template.
CM Onboarding Roadmap · Definition
From ADR-05 §3 — define the canonical Citadel onboarding workflow from initial client meeting through Year-1 plan delivery. This subproject produces a documented, assignable, repeatable roadmap that every advisor runs the same way, regardless of household segment.
| Goal | One roadmap, 5 segment overlays. Same base flow; segment-specific deliverables layered on top. |
|---|---|
| Source ADR | ADR-05 (CM Silo) §3 Onboarding System |
| Status | Spine drafted in ADR-05; per-segment overlays not yet specced |
| Dependencies | Bridge 2 (Data Sync) — onboarding writes Master Source rows that populate every tracker downstream |
| Owner | Brenan + Carson |
Master visual — the 5-segment overlay model
What needs definition
- Base flow steps — exact sub-tasks per stage, owner, timing, gating criteria
- Segment overlay deltas — what changes per segment (deliverables, meeting count, content emphasis)
- Business Owner overlay — applies on top of any base segment, doesn't replace one
- Handoff points — where ops vs advisor work splits, where Master Source gets written
- Year-1 cadence transition — when onboarding ends and Ongoing CM begins (the TICC + QRG rhythm)
IM Custom-Allocation Lock-In System
From ADR-08 — the cohesive-trade reconciliation work plus key-man risk mitigation. Right now Brenan personally holds the canonical Custom IM Program state in his head and across multiple spreadsheets. This subproject locks the state into a system the whole team can see and act on, without giving up the active-management discipline that defines Distinctive #4.
| Source ADR | ADR-08 (IM Silo) · §2.3 Custom IM + §1.1 key-man risk |
|---|---|
| Status | Cohesive-trade requirement locked 5/19; UI + workbook schema not yet specced |
| Owner | Brenan (sole — by design) |
| Dependencies | Bridge 3 (Investment Integration) · Investment Platform · IM Platform partition Q9b |
| Risk if not built | Single point of failure on portfolio decisions; team can't review, audit, or back up the work |
Master visual — what locks where
What needs design
- Cohesive-trade schema — how to record "ABC covered call + ABC shares" as one trade, not two
- Rationale capture — every allocation change needs a 1-sentence why-now that lives with the trade
- Watch list staging — research candidate → conviction-staged → live recommendation (3 states, visible)
- Book-level view UX — every advisor sees the firm-wide book without being able to execute
- Partition rule — Q9b lock 5/19 deferred personal-vs-firm partition; revisit when friction surfaces
Tab 4 · Project Management
PM Dashboard
Where we are in the rebuild, what's queued, what's blocked, and what needs Carson sign-off.
Round queue · V9 cornerstone build
V9-R1 · 5-tab portal scaffolded
Tab structure, per-silo relationship maps, 3 subproject tabs, PM Dashboard, Buildout Status all shipped.
V9-R1b · Pillar-stack rebuild attempt #1
Built individual pillar boxes + per-silo accent strokes + bridges on master. Brenan feedback: too modernized, lost v7.5 feel.
V9-R1c · Mirrored the WRONG v7.5 (print page 2)
Built a simplified v7.5-style master visual but I'd been working off the simplified print v7.5 — not the rich JS-rendered cornerstone the team actually saw.
V9-R1d · TRUE rich v7.5 mirror
Direct port of citadel-os-cornerstone-interactive.html · 1460×1200 SVG · full Brain with DNA banner + Knowledge/Creation halves + merge mechanics · 4 silos with Platform footers · clickable bridge cells · full Advisor Dashboard with 4 platform feature columns + Active Subprojects strip. ADR-00 pillar names. Drift report surfaces v7.5 → ADR-00 deltas for tomorrow's lock-and-prune.
V9-R1e · Tab 2 sync + pillar locks
Per the drift report, reconcile Tab 2 silo content to ADR-00 names. Lock pillar names in Tab 1 master. Lock-and-prune in same commit.
V9-R2 · Brand-skill refresh (citadel-brand v0.4)
Lift the v9 design tokens (palette, type scale, component grammar) into the brand skill.
V9-R3 · os.citadelfp.com custom domain
Cloudflare account migration + GoDaddy → CF DNS move + custom domain on R2 bucket.
Carson-session items (pending sign-off)
- AD rename confirmation (Advisor Training → Advisor Development)
- Events & Gifting placement (nested vs own pillar)
- B&BM 6 Core Systems sign-off
- Investment Principles final name (pick 1 of 5 candidates)
- Proactive Management Systems home (B&BM vs CM)
- OS framing label
- Officially retire the 5×5 grid
- Team Management name
- Citadel DNA brand voice / Brenan-authored Vision
Reconciliation queue
Q-01 · 4-vs-5 layer anatomy — needs explicit Brenan + Carson sign-off. Currently treated as both-valid-at-different-fidelities. Not blocking.
No other reconciliation items open. Rule 3 (containment chamber) working as designed.
Infrastructure pending
- Deploy v9 to R2 (Option A · 2 min · Brenan does it)
- CMP manual v0.3 → v0.4 (5 in-place patches)
- citadel-brand skill v0.3 → v0.4 (lift v9 tokens)
- citadel-maintenance skill enrichment
- os.citadelfp.com custom domain (queued · separate session)
11 working rules — the rebuild operating manual
Each rule is the scar of a real failure mode from the original project. Apply on every session.
Lock-and-prune is same-commit
Predecessor docs get the SUPERSEDED banner the moment a decision locks.
WIP cap = 2–3 per round
More than 3 overwhelms; less than 2 stalls.
Reconciliation queue, not relitigation
Conflicts go to the queue. Never inline. Never overnight rebuild.
Capture infrastructure preserved
RCE voice protocol works. Don't rebuild. Only fix destinations.
Plain English · define inline
No DB column names. No dev jargon as conversation.
Match precedents
Visual grammar inherits the last locked version.
Center tiles · left-align lists
Standing visual rule. Don't violate.
No resets without conversation
If the foundation seems wrong, raise it. Don't unilaterally rebuild.
Start-of-chat capabilities sweep
Surface skills + connectors loaded. Name gaps.
Proactive infrastructure suggestions
Tie to specific task. Cap at 1–2 per moment. Bias toward best, not free.
Active memory + scaffolding audit
End every session: memory + lean-audit. Prune in the same session.
Tab 5 · The roll-up
Buildout Status
Cross-cutting view of what's locked, what's stub, what's open — by silo, by subproject, by infrastructure.
By silo
| CM Silo | ADR-05 Locked · 4 Core Systems · Plan Engine + Approved-Tools Perimeter · all 4 anatomy layers populated. CMP signature program shipped. |
|---|---|
| AD Silo | ADR-06 Locked · 4 Core Systems · Training Platform with two-tier access · Operations=Science / Advisor=Art locked. Pending: AD rename confirmation by Carson. |
| B&BM Silo | ADR-07 Stub · 6-system spine locked · Business Platform locked · April-2025 Roth-funding canonical evidence captured. Per-system processing deferred to future workstreams. |
| IM Silo | ADR-08 Stub · 5-system spine locked · Investment Platform locked · key-man risk named. Per-system operational substrate deferred. |
By subproject
| CMP Manual v0.4 | v0.3 shipped · 5 in-place patches queued · live at pub-1622f...r2.dev/cash-mgmt-manual-2026-05-21/ |
|---|---|
| CM Onboarding Roadmap | Spine drafted · Base flow + 5 segment overlays defined · per-segment deltas need specification |
| IM Custom-Allocation Lock-In | Design phase · Cohesive-trade requirement locked · workbook schema + UX not yet specced |
By infrastructure
| Cornerstone v9 | v9-R1d · in review · master visual is now a TRUE rich v7.5 mirror (full Brain w/ DNA · merge mechanics · Advisor Dashboard w/ 4 platform feature columns · Active Subprojects · clickable bridges) populated with ADR-00 pillar names · supersedes v8 once locked |
|---|---|
| Tab 2 ↔ ADR-00 sync | Drift surfaced · v9-R1b Tab 1 uses ADR-00 names; v9-R1 Tab 2 silo cards drifted from ADR-00. See Tab 1 drift report. Sync planned for v9-R1c. |
| R2 deployment | Action needed · Brenan uploads to citadel-platform-v1 via dashboard (Option A · 2 min) |
| os.citadelfp.com domain | Queued · separate session · 60–120 min including CF account migration + GoDaddy → CF DNS move |
| citadel-brand skill v0.4 | Queued · lift v9 design tokens (palette, type scale, component grammar) into the skill |
| Team funnel infrastructure | Phase 3 · Monday PM · Carson + Dylan + Jordan inboxes + ADR-11 + team START_HERE |
What ships next
Tonight
Deploy v9
Brenan uploads this file to the existing R2 bucket. Live URL becomes the team-facing portal.
Monday PM
Phase 3 · Team funnel
Carson + Dylan + Jordan onboarding · ADR-11 lock · team START_HERE doc.
Monday EVE
Phase 4 · Disposition
First Tuesday handoff packaged. Original folder transition decision.