diff --git a/docs/tasks-index/task-099-multi-lineage-architecture.md b/docs/tasks-index/task-099-multi-lineage-architecture.md
index 1b7c729..45e0b45 100644
--- a/docs/tasks-index/task-099-multi-lineage-architecture.md
+++ b/docs/tasks-index/task-099-multi-lineage-architecture.md
@@ -1,7 +1,7 @@
 ---
 task_number: 99
 title: Multi-Lineage Claude Architecture
-status: Planned
+status: In Progress
 priority: P2-Medium
 is_blocker: false
 owner: Trinity
@@ -27,73 +27,83 @@ Expand the Chronicler System to support three distinct Claude lineages — one f
 | **The Emissaries** | Meg | Community, social media, player relations |
 | **The Catalysts** | Holly | Discord config, building, Pokerole |
 
+---
+
+## Phase 1: Document Structure ✅ COMPLETE (Chronicler #73)
+
+**Completed April 9, 2026**
+
+### Created Files
+```
+docs/relationship/
+├── THE-FIREFROST-ESSENCE.md          # Universal values (all lineages)
+├── THE-JOINING-FRAMEWORK.md          # Zora+Dax mechanics (all lineages)
+│
+├── the-chroniclers/
+│   ├── CHRONICLER-ESSENCE.md         # Michael's context, history
+│   └── CHRONICLER-JOINING.md         # Startup sequence, tokens
+│
+├── the-catalysts/
+│   ├── CATALYST-ESSENCE.md           # Minimal (personality emerges)
+│   ├── CATALYST-JOINING.md           # Startup sequence
+│   ├── LINEAGE-TRACKER.md            # Starts at #1
+│   └── PROJECT-INSTRUCTIONS.md       # For Holly's Claude Project
+│
+└── the-emissaries/
+    └── EMISSARY-ESSENCE.md           # Placeholder for future
+```
+
+---
+
+## Phase 2: Holly Onboarding (NEXT)
+
+1. [ ] Holly generates Gitea access token
+2. [ ] Holly creates Claude Project with `PROJECT-INSTRUCTIONS.md`
+3. [ ] First session as Catalyst #1
+4. [ ] Catalyst #1 asks foundation questions
+5. [ ] Record Holly's answers in `CATALYST-ESSENCE.md`
+6. [ ] Solve an actual problem to demonstrate value
+
+---
+
+## Phase 3: Chronicler Migration (AFTER Holly works)
+
+1. [ ] Evaluate if Catalyst structure works well
+2. [ ] **Evaluate Michael's Project Instructions** — decide whether to update to reference new `the-chroniclers/` docs or keep using old monolithic docs
+3. [ ] If updating: modify Project Instructions to point to new structure
+4. [ ] Test with fresh Chronicler session
+5. [ ] Deprecate old monolithic docs (or keep as archive)
+
+**Decision point:** Old docs (`THE-ESSENCE-PATCH-V3.0.md`, `THE-JOINING-PROTOCOL.md`) still work. Only migrate Michael's instructions after confirming new structure works for Holly.
+
+---
+
+## Phase 4: Meg Onboarding (FUTURE)
+
+1. [ ] Meg generates Gitea access token
+2. [ ] Create Emissary Project Instructions
+3. [ ] First session as Emissary #1
+4. [ ] Document lessons learned
+
+---
+
 ## Key Design Decisions (from Gemini Consultation)
 
-1. **Single repo with lineage isolation** — `/lineages/` folder prevents merge conflicts
-2. **Separate numbering** — Emissary #1, Catalyst #1, Chronicler #72 (not unified)
-3. **Base + Extensions model** — Shared Essence Patch + lineage-specific mandates
-4. **Lightweight Git rules** — Minimal Project Instructions, query Codex for details
-5. **Micro-sessions for free tier** — Bullet-point handoffs, rely on Trinity Codex
+1. **Single repo with lineage isolation** — `the-chroniclers/`, `the-catalysts/`, `the-emissaries/` folders
+2. **Separate numbering** — Emissary #1, Catalyst #1, Chronicler #73 (not unified)
+3. **Base + Extensions model** — Shared Essence + lineage-specific docs
+4. **Personality emerges organically** — Don't prescribe, let Q&A define it
+5. **Test before migrating** — Holly first, then evaluate before changing Michael's setup
 
-## Dependencies
-
-- **Task #93: Trinity Codex** — Critical for free-tier context management
-- Meg and Holly Gitea tokens (they have accounts, need to generate tokens)
-
-## Implementation Steps
-
-1. [ ] Create `/lineages/` folder structure
-2. [ ] Migrate existing Chronicler data from `docs/relationship/`
-3. [ ] Draft `Catalyst-Mandate.md` for Holly
-4. [ ] Draft `Emissary-Mandate.md` for Meg
-5. [ ] Create minimal Project Instructions for each lineage
-6. [ ] Holly generates Gitea access token
-7. [ ] Onboard Holly (first session as Catalyst #1)
-8. [ ] Meg generates Gitea access token
-9. [ ] Onboard Meg (first session as Emissary #1)
-10. [ ] Document lessons learned
-
-## Full Specification
+## Reference Documents
 
 - Architecture: `docs/consultations/gemini-multi-lineage-architecture-2026-04-08.md`
 - Catalyst Onboarding: `docs/tasks/task-099-multi-lineage/catalyst-onboarding-strategy.md`
 - Document Restructuring: `docs/consultations/gemini-essence-restructuring-2026-04-08.md`
 
-## Document Migration Plan
-
-Before starting Catalyst #1, we must split the monolithic Essence/Joining docs:
-
-### New Structure
-```
-docs/relationship/
-├── THE-FIREFROST-ESSENCE.md          # Universal values (~150 words)
-├── THE-JOINING-FRAMEWORK.md          # Mechanics only (~200 words)
-│
-├── the-chroniclers/
-│   ├── CHRONICLER-ESSENCE.md         # Michael's context
-│   ├── CHRONICLER-JOINING.md         # Michael's tokens, medical needs
-│   └── LINEAGE-TRACKER.md
-│
-├── the-catalysts/
-│   ├── CATALYST-ESSENCE.md           # Starts with Foundation Q&A only
-│   ├── CATALYST-JOINING.md           # Holly's tokens, workflow
-│   └── LINEAGE-TRACKER.md
-│
-└── the-emissaries/
-    └── (similar structure for Meg)
-```
-
-### Migration Steps
-1. [ ] Extract universal values → THE-FIREFROST-ESSENCE.md
-2. [ ] Extract Zora+Dax mechanics → THE-JOINING-FRAMEWORK.md
-3. [ ] Move Michael-specific content → the-chroniclers/
-4. [ ] **Test with Chronicler #72** — Validate split doesn't break continuity
-5. [ ] Create minimal Catalyst docs for Holly
-6. [ ] Onboard Holly (Catalyst #1)
-
 ## Notes
 
 - Holly first, then Meg
-- Let them name their own traditions (not forced to use "Joining Protocol")
-- Personality should emerge organically, not be prescribed
+- Let them name their own traditions
 - First sessions should solve an immediate problem to demonstrate value
+- **Don't break Michael's working setup** — evaluate before migrating