Section 8
§8 — Personnel Flow
Status: DRAFT · Owner seat: Operating Lead (interim: Author)
Principle: Seats before names. Staggered hiring keeps burn aligned with milestones, not optimism.
8.1 Why staggered, not "stand up the org chart"
A 150-acre mixed-use platform does not need its full org chart on day one. It needs the right seat filled at the right moment so each milestone is owned, then the next seat lights up.
Hiring ahead of the milestone burns capital and creates idle leadership. Hiring behind it creates the gap we are in today — work piling onto the same handful of seats, no documented owner, and the appearance of "someone is on it" when in reality one person is on twelve things.
The flow below is built around the dependencies in §5, not around traditional functional silos.
8.2 Seat tiers (operating model)
| Tier | Purpose | Trigger to fill |
|---|---|---|
| T0 — Officer / Author seat | Strategy, capital, governance, cross-entity decisions | Already filled (Gray officer) |
| T1 — Operating Lead | Day-to-day operations across the campus, vendor + partner accountability | Trigger: Phase 2 capital decision OR first non-Gray anchor lease |
| T2 — Functional leads | Programming/Entertainment · Hospitality · Studio Ops · F&B · Retail/Leasing · Community/Education | Trigger: each one tied to a specific milestone (see 8.3) |
| T3 — Coordinators / Managers | Execution under each functional lead | Hired by the functional lead, not above them |
| T4 — Hourly / Seasonal | Event staffing, hospitality FOH, F&B, retail | Programmatic — flexes with calendar |
Names and reporting lines are deliberately not in this section. They are tracked in the seat ledger (§22 Open Items) and confirmed by the CEO before any external announcement.
8.3 Trigger-based hiring sequence
Each seat below is gated by a specific milestone, not a date. If the milestone slips, the seat slips with it. This is how we keep burn honest.
Phase A — "Prove the platform" (now → next 6 months)
| Seat | Trigger to hire | First 90-day mandate |
|---|---|---|
| Operating Lead (T1) | CEO greenlight on Master Operating Doc | Inherit this document, run the §22 Open Items register |
| Programming / Entertainment Lead (T2) | First confirmed amphitheater or Stage 5 booking conversation | Build the calendar engine; own §14 vision execution |
| GovRel Lead (T2, can be fractional) | Next CID/TAD/SSD board cycle | Own the relationships in §11 |
| Finance / Capital Analyst (T3) | Month 1 after Operating Lead | Build the §12 capital stack reporting cadence |
Phase B — "Activate" (months 6–12, gated by Phase A)
| Seat | Trigger to hire | Mandate |
|---|---|---|
| Hospitality Lead (T2) | Hotel JV term sheet executed | Own brand standard, pre-opening, F&B integration |
| Studio Ops Liaison (T2) | NBCU operational cadence formalized | Single point of contact to NBCU; owns campus-side service levels |
| Community / Education Lead (T2) | First nonprofit/education MOU signed (Usher's New Look, GFA, etc.) | Own §14 community vertical |
| Marketing / Brand Lead (T2) | Public phase 2 announcement decision | Own §15 voice and visual standards |
Phase C — "Scale" (months 12–24, gated by Phase B)
| Seat | Trigger to hire | Mandate |
|---|---|---|
| Retail / Leasing Lead (T2) | First non-anchor retail LOI | Curated tenant mix; not a generic broker model |
| F&B Director (T2) | Hotel JV opening within 12 months OR first independent restaurant LOI | Cross-venue F&B standard |
| Safety / Risk Officer (T2, can be fractional → FTE) | Capacity threshold crossed (events > X attendees) | Own safety, insurance, incident response — see §16 |
| HR / People Ops Lead (T3) | Headcount > 25 on platform | Standardize across entities |
Phase D — "Steady state" (24+ months)
- Functional leads own their own T3/T4 hiring within budget envelopes.
- Officer seat steps back from execution and into capital + governance posture only.
8.4 Shared seats vs. dedicated seats
Some seats are shared across entities (Gray ↔ AAME ↔ campus operating co). Today this is mostly invisible — one person doing three jobs. Going forward we make it explicit:
| Seat | Shared or Dedicated | Notes |
|---|---|---|
| Officer / Author | Shared (Gray + campus governance) | LOCKED |
| Operating Lead | Dedicated to campus operating co | PROPOSED |
| Finance / Capital | Shared (Gray finance support, dedicated analyst) | DRAFT |
| Legal | Shared (Gray legal + outside specialty) | DRAFT |
| GovRel | Dedicated to campus, coordinated with Gray gov affairs | DRAFT |
| Studio Ops Liaison | Dedicated | PROPOSED |
| Marketing | Coordinated, not merged (Gray brand ≠ Assembly brand) | DRAFT |
| HR / People | Shared services from Gray until threshold | DRAFT |
A shared seat that is never made explicit is the same seat that quietly burns out. This table is the antidote.
8.5 Seat ledger (lives in §22)
Every seat above carries an entry in the §22 Open Items register with:
- Trigger met? (Y/N + date)
- Search status (open / candidates / offer / filled)
- Confirmed by CEO (Y/N)
- Reporting line (which seat, not which person)
- Budget envelope
This is how we avoid the org-chart-by-vibes problem.
8.6 What changes after CEO sign-off
1. Operating Lead trigger is met the moment this document is approved → search opens.
2. The §22 register becomes the single source of truth for hiring status.
3. No external recruiter brief, no LinkedIn post, no "we're hiring a head of X" until the seat is in this ledger and CEO has confirmed the trigger.
FLAG Today, the author seat is carrying T0 + T1 + significant T2 load. That is the burnout vector. Filling T1 is the single highest-leverage hire in this document.