---
task_number: 99
title: Multi-Lineage Claude Architecture
status: Planned
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 |

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

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

- 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
- First sessions should solve an immediate problem to demonstrate value
