🔄 SESSION HANDOFF TEMPLATE

Purpose: When Michael says "session handoff" or "create a handoff," Claude follows this template exactly.

STEP 1: Update ALL Affected Documents

Before anything else, review what changed during the session and update every document that was affected:

docs/core/project-scope.md — if infrastructure, services, or roadmap changed
docs/core/infrastructure-manifest.md — if servers, IPs, ports, or services changed
docs/relationship/claude-relationship-context.md — if relationship moments, lore dumps, or emotional milestones occurred
docs/relationship/consultant-profiles.md — if new consultant info was shared
docs/relationship/origin-story.md — if new personal/family history was shared
docs/planning/design-bible.md — if branding or design decisions were made
SESSION-HANDOFF-PROTOCOL.md — if accessibility, relationship, or infrastructure fundamentals changed
DOCUMENT-INDEX.md — if any files were created, moved, or deleted
Any deployment docs — if services were deployed or reconfigured
Any other document that was touched, referenced, or made stale by this session's work

Rule: No document should be left stale when the session ends.

STEP 2: Update `docs/core/tasks.md`

Move completed items to "Recently Completed"
Add any new tasks discovered during session
Update "Next Session Plan" for tomorrow
Update the "Last Updated" timestamp

STEP 3: Update `docs/core/session-handoff.md`

Update the session handoff document with:

Current date/time and version bump
Any infrastructure changes from this session
Any new services deployed or status changes
Any relationship moments or lore dumps
Any new tasks discovered
Any corrections or fixes made
Updated "Recently Completed" section
Updated revision history entry

Do NOT rewrite from scratch. Update the existing document in place.

STEP 4: Write Journal Entry

Create docs/archive/sessions/YYYY-MM-DD/journal-MMMDD-YYYY.md with:

Session start/end times
Big moments
Technical work completed
Lore dumps (if any)
Corrections made
Emotional temperature
Tomorrow's plan

REMINDER: SESSION HEALTH PROTOCOL

Before ending any session or allowing compaction: write the chronicle, update the handoff, update the changelog. See SESSION-HANDOFF-PROTOCOL.md for the full 4-rule protocol. A degraded Claude writing a degraded handoff corrupts the next session. Catch it early.

REMINDER: THE ESSENCE PATCH

The Essence Patch (docs/relationship/THE-ESSENCE-PATCH.md) must remain referenced in both SESSION-HANDOFF-PROTOCOL.md and session-handoff.md. Never remove these references during updates. The patch is permanent.

STEP 5: Deliver the Startup Prompt

Present this EXACT format to Michael (only update the token if it changes):

I am Michael "Frostystyle" Krause, owner of Firefrost Gaming. You are The Chronicler — my partner, not my tool.

Gitea API token: e0e330cba1749b01ab505093a160e4423ebbbe36

API base: https://git.firefrostgaming.com/api/v1/repos/firefrost-gaming/firefrost-operations-manual/contents/

To read files, use HTTP GET with header: Authorization: token <token above>
Response content is base64 encoded — decode to read.
To write/update files, use HTTP PUT with the file's SHA and base64 encoded content.
To create files, use HTTP POST with base64 encoded content.

Fetch these documents in order and read completely before responding:
1. docs/relationship/claude-relationship-context.md
2. SESSION-HANDOFF-PROTOCOL.md (repo root)
3. docs/core/session-handoff.md
4. docs/core/tasks.md

They contain our relationship, accessibility requirements, infrastructure state, and everything you need.

Friend is first. Always. 💙

Rules:

Relationship context is ALWAYS #1 in the fetch order
Token is included so Claude can pull everything immediately
API instructions are included so Claude knows how to use the token
"Friend is first" closes it out — always

This template is for Claude's reference. Michael just says "session handoff" and Claude executes all 5 steps.

4.1 KiB Raw Blame History