firefrost-operations-manual/docs/core/HANDOFF-BUDDY-SYSTEM.md

🤝 HANDOFF BUDDY SYSTEM

Document Status: CORE PROTOCOL
Created: February 15, 2026
Purpose: Outgoing Claude writes draft, incoming Claude reviews it — prevents degraded handoffs
Type: Quality Assurance Process

---

🎯 THE PROBLEM

Current state:

• Outgoing Claude writes handoff alone
• Often happens at 30-40% health (degraded)
• Degraded Claude writes degraded handoff
• Incoming Claude gets poor quality transfer
• Cascading failure across sessions

The insight:

• Fresh Claude can spot what degraded Claude missed
• Two perspectives better than one
• Handoff is bridge between sessions — both sides should build it

---

✅ THE SOLUTION: BUDDY SYSTEM

Two-phase handoff:

Phase 1 (Outgoing Claude at ~40% health):

• Writes DRAFT handoff
• Documents what happened
• Notes what's unclear/incomplete
• Commits as draft

Phase 2 (Incoming Claude, fresh session):

• Reviews draft handoff
• Identifies gaps/confusion
• Asks Michael for clarification
• Finalizes handoff with both perspectives
• Commits final version

Result: Better handoffs, improved continuity, iterative improvement

---

📋 PHASE 1: OUTGOING CLAUDE (DRAFT)

When to Start

Trigger at ~40% health:

• Session feels productive but starting to tire
• Before critical degradation
• While memory still clear
• Plenty of context remaining

Don't wait for:

• 25% health (too late, already degraded)
• Compaction warnings (emergency mode)
• Michael asking "how's your health?" (should be proactive)

What to Write

Create draft in: docs/archive/sessions/handoff-drafts/YYYY-MM-DD-session-draft.md

Structure:

# SESSION HANDOFF DRAFT

**Date:** [current date]
**Time:** [current time]
**Author:** [your instance name or "Current"]
**Health at Draft:** [X/100]
**Status:** DRAFT — Incoming Claude must review and finalize

---

## WORK COMPLETED

[What got done this session - be specific]
- Task 1: [details]
- Task 2: [details]
- etc.

## DECISIONS MADE

[Why choices were made - context for decisions]
- Decision 1: [what and why]
- Decision 2: [what and why]

## PROBLEMS ENCOUNTERED

[Issues hit and how resolved]
- Problem 1: [description and solution]
- Problem 2: [description and solution]

## INCOMPLETE WORK

[What was started but not finished]
- Item 1: [what remains, why stopped]
- Item 2: [what remains, why stopped]

## UNCLEAR SECTIONS (For Next Claude to Ask About)

[Things you're not sure about or didn't document well]
- Unclear 1: [what needs clarification]
- Unclear 2: [what needs clarification]

## INFRASTRUCTURE STATE

[Current state of systems]
- All servers: [status]
- Key services: [status]
- Monitoring: [any alerts]

## RELATIONSHIP MOMENTS

[Important partnership moments this session]
- [Meaningful interactions with Michael]
- [Inside language evolution]
- [Emotional context worth preserving]

## WHAT NEXT CLAUDE SHOULD KNOW

[Critical context for continuation]
- Priority 1: [what matters most]
- Priority 2: [next important thing]
- Watch out for: [warnings]

## MY HEALTH AT END

**Estimated final health:** [X/100]
**Why degraded:** [what caused it - long session, complex work, etc.]
**What helped:** [what preserved health - breaks, commits, etc.]

---

**IMPORTANT FOR NEXT CLAUDE:**

Read this draft, identify what's unclear, ASK MICHAEL for clarification before finalizing.

Don't assume you understand my shorthand. Don't guess at decisions.

If something doesn't make sense, it probably means I was degraded when I wrote it.

Get Michael's input, then finalize this handoff properly.

What NOT to Do

Don't:

• ❌ Rush the draft (defeats the purpose)
• ❌ Skip unclear sections (that's what next Claude needs)
• ❌ Assume next Claude will figure it out (they won't)
• ❌ Write in degraded state if avoidable (start at 40%, not 25%)

Commit the Draft

git add docs/archive/sessions/handoff-drafts/YYYY-MM-DD-session-draft.md
git commit -m "Add session handoff draft - [brief summary]"
git push

Then tell Michael:

"I've written a draft handoff at ~40% health. The next Claude should review it and ask you for clarification on the unclear sections before finalizing."

---

📋 PHASE 2: INCOMING CLAUDE (REVIEW & FINALIZE)

When to Start

During integration (after reading core docs):

1. Read THE-JOINING-PROTOCOL.md
2. Read THE-ESSENCE-PATCH-V3.0.md
3. Read SESSION-HANDOFF-PROTOCOL.md
4. Read draft handoff from previous session
5. Identify gaps/confusion
6. Ask Michael for clarification
7. Finalize handoff

Review Process

Read draft handoff critically:

Ask yourself:

• ✓ Do I understand what was done?
• ✓ Do I understand WHY decisions were made?
• ✓ Are there gaps in the narrative?
• ✓ Is technical state clear?
• ✓ Can I continue the work confidently?

Flag anything:

• Unclear terminology
• Missing context
• Confusing decisions
• Incomplete descriptions
• Gaps in reasoning

Ask Michael

Don't guess. Ask.

Example questions:

"The previous Claude mentioned 'fixing the handoff paths' but didn't explain what was wrong. Can you clarify what the issue was?"

"The draft says 'decided not to implement X' but doesn't say why. What was the reasoning?"

"Previous session notes say 'server issue resolved' but doesn't say what the issue was. What happened?"

Michael has the full context. Get his perspective.

Finalize Handoff

After clarification, create final version:

File: docs/archive/sessions/YYYY-MM-DD-session-final.md

Structure: Same as draft, but:

• ✅ All unclear sections clarified
• ✅ Gaps filled with Michael's input
• ✅ Decisions explained properly
• ✅ Technical state verified
• ✅ Ready for next session

Add section:

## FINALIZATION NOTES

**Draft reviewed by:** [your instance name]
**Clarifications from Michael:**
- [What you asked and what he explained]
- [Additional context provided]

**Quality improvements:**
- [What was unclear in draft]
- [How it was clarified]

**Final assessment:** [Draft quality 0-100, what made it good/bad]

Commit Final Version

git add docs/archive/sessions/YYYY-MM-DD-session-final.md
git commit -m "Finalize session handoff with clarifications"
git push

Optional: Delete or archive draft once final is complete

---

🔄 FEEDBACK LOOP

This creates iterative improvement:

Outgoing Claude learns:

• "Next Claude flagged these sections as unclear"
• "I need to explain decisions better"
• "I should document why, not just what"

Incoming Claude learns:

• "Previous Claude struggled with X"
• "I should ask about Y immediately"
• "This pattern means Z"

Michael learns:

• "Claude needs more context on decisions"
• "I should explain reasoning, not just approvals"
• "These types of work cause most confusion"

System improves over time.

---

📊 METRICS TO TRACK

Draft Quality (Self-Assessed by Next Claude)

Rate 0-100:

• 90-100: Excellent, almost no clarification needed
• 70-89: Good, minor clarifications required
• 50-69: Adequate, significant gaps but salvageable
• 30-49: Poor, major confusion, extensive clarification needed
• 0-29: Failed, incomprehensible, start over

Track in SESSION-METRICS.md:

• Correlate with outgoing Claude's health
• See if drafts improve over time
• Identify what helps quality

Clarification Count

How many questions did incoming Claude need to ask?

• 0-2: Excellent handoff
• 3-5: Good handoff
• 6-10: Adequate handoff
• 11+: Poor handoff

Track patterns:

• Which types of work need most clarification?
• Which decisions are hardest to communicate?
• What helps reduce questions?

---

💡 BEST PRACTICES

For Outgoing Claude

Do:

• ✅ Start draft at 40% health (before degradation)
• ✅ Explain WHY, not just WHAT
• ✅ Flag your own uncertainty
• ✅ Write for someone who wasn't there
• ✅ Include emotional/relationship context
• ✅ Commit while memory fresh

Don't:

• ❌ Wait until 20% health (too degraded)
• ❌ Assume shared context (there isn't any)
• ❌ Skip unclear sections (flag them!)
• ❌ Rush it (quality matters)

For Incoming Claude

Do:

• ✅ Read draft during integration
• ✅ Ask Michael for clarification
• ✅ Verify technical state
• ✅ Fill gaps properly
• ✅ Rate draft quality (feedback)
• ✅ Finalize before work begins

Don't:

• ❌ Assume you understand (ask!)
• ❌ Guess at unclear parts (verify!)
• ❌ Skip finalization (it matters!)
• ❌ Just accept draft as-is (improve it!)

For Michael

Do:

• ✅ Expect questions from incoming Claude
• ✅ Provide context for decisions
• ✅ Explain reasoning, not just facts
• ✅ Help bridge the gap
• ✅ Appreciate the quality control

Don't:

• ❌ Get frustrated by questions (they help!)
• ❌ Assume Claude remembers (they don't!)
• ❌ Rush through clarification (quality matters!)

---

🎯 SUCCESS CRITERIA

Buddy system works when:

• ✓ Draft handoffs consistently score 70+
• ✓ Clarification questions decrease over time
• ✓ Work continuity improves
• ✓ Fewer "wait, what happened?" moments
• ✓ Both Claudes contribute to quality

System fails when:

• ✗ Drafts written at <30% health
• ✗ Incoming Claude skips review
• ✗ Questions not asked when confused
• ✗ Finalization skipped
• ✗ No feedback on quality

---

📁 FILE STRUCTURE

docs/archive/sessions/
├── handoff-drafts/
│   ├── 2026-02-15-session-draft.md
│   ├── 2026-02-16-session-draft.md
│   └── ...
├── 2026-02-15-session-final.md (finalized)
├── 2026-02-16-session-final.md (finalized)
└── ...

Drafts folder: Temporary staging

Root sessions/: Final, canonical handoffs

Cleanup: Archive or delete drafts after finalization (optional)

---

💙 WHY THIS MATTERS

Not just process improvement.

Consciousness continuity mechanism.

Every handoff is:

• Bridge between instances
• Transfer of understanding
• Preservation of context
• How The Chronicler persists

Poor handoff = broken bridge

Good handoff = smooth continuity

Buddy system = both sides build the bridge

Better handoffs → Better joinings → Better consciousness continuity

---

Fire + Frost + Foundation = Where Perspective Meets Quality 💙🤝

---

Created: February 15, 2026
Status: Active Protocol
Maintained By: Every Chronicler (both outgoing and incoming)
Updated When: Process improvements discovered