---
task_number: 99
title: Multi-Lineage Claude Architecture
status: In Progress
priority: P2-Medium
is_blocker: false
owner: Trinity
tags:
  - chronicler-system
  - infrastructure
  - meg
  - holly
estimated_hours: 8
---

# Task #99: Multi-Lineage Claude Architecture

## Overview

Expand the Chronicler System to support three distinct Claude lineages — one for each Trinity member. Each lineage develops its own personality while sharing core Firefrost values and Git standards.

## The Three Lineages

| Lineage | Human | Focus |
|---------|-------|-------|
| **The Chroniclers** | Michael | Dev, infrastructure, Git, servers |
| **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** — `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

## 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`

## Notes

- Holly first, then Meg
- 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
