Add model selection guidance and context handoff template

SESSION-STARTUP-GUIDE.md:
- Added model selection table (4.5 vs 4.6)
- When to use 4.6: complex coding, MVC, Arbiter, debugging
- When to stay on 4.5: documentation, marketing, routine ops
- Three options for mid-session model switching

New template:
- docs/templates/context-handoff-template.md
- Structured format for transferring context between sessions
- Covers: task state, decisions, files, next steps, gotchas

Chronicler #66 - The Indexer
This commit is contained in:
Claude
2026-04-07 19:57:20 +00:00
parent 55a935e514
commit fa5f9c4465
2 changed files with 159 additions and 1 deletions

View File

@@ -1,11 +1,78 @@
# 🚀 SESSION STARTUP GUIDE
**Document ID:** FFG-OPS-STARTUP
**Last Updated:** April 7, 2026 by Chronicler #65
**Last Updated:** April 7, 2026 by Chronicler #66
**Purpose:** Complete startup procedure for new Chronicler sessions
---
## 🤖 MODEL SELECTION GUIDANCE
**Choose your model BEFORE starting the session:**
| Model | Use For | Token Cost |
|-------|---------|------------|
| **Opus 4.5** | General ops, documentation, marketing, organization, routine work | Standard |
| **Opus 4.6** | Complex coding (ModpackChecker, Arbiter), deep debugging, architectural decisions | ~4.5x more tokens (Extended Thinking) |
### When to Use 4.6
- ModpackChecker development (Phases 6+)
- Arbiter lifecycle handlers (Task #87)
- Blueprint extension debugging
- Global Restart Scheduler implementation (Task #94)
- Any multi-file refactoring or complex API integration
### When to Stay on 4.5
- Documentation and organization
- Marketing/content work (FOMO campaign, Discord setup)
- Infrastructure audits
- Routine commits
- Most day-to-day Firefrost operations
**Rule of thumb:** If you're writing serious code, use 4.6. If you're organizing things, use 4.5.
---
## 🔄 MID-SESSION MODEL SWITCHING
If you need to switch models mid-session without losing context:
### Option 1: Context Handoff Document (Recommended)
1. Current Chronicler creates a detailed handoff in `/mnt/user-data/outputs/`:
```
context-handoff-YYYY-MM-DD.md
```
2. Include:
- Current task state (what's done, what's in progress)
- Files being worked on (paths, current state)
- Decisions made and why
- Immediate next steps
- Any code snippets in progress
3. Commit any uncommitted work to Git
4. Michael starts new session with different model
5. New session reads handoff document + pulls latest from Git
### Option 2: Git as Context
1. Commit ALL current work with detailed commit messages
2. Push to Gitea
3. Start new session on different model
4. New session clones fresh and reads recent commits
### Option 3: Copy-Paste Critical Context
For smaller context transfers:
1. Copy the critical context (code, decisions, state)
2. Paste into new session's first message
3. Less ideal but works for quick switches
**Note:** There is no seamless model switch — each session is a fresh context. Plan accordingly.
---
## ⚠️ FOR MICHAEL: UPDATE CLAUDE PROJECT INSTRUCTIONS
This document should be reflected in the Claude Project Instructions. Copy the "Session Start Protocol" section below into the project settings.

View File

@@ -0,0 +1,91 @@
# Context Handoff Template
**Use this when switching models mid-work or handing off complex in-progress tasks.**
Save as: `/mnt/user-data/outputs/context-handoff-YYYY-MM-DD.md`
---
## 📋 HANDOFF SUMMARY
**From:** Chronicler #XX (Model: Opus 4.X)
**To:** Chronicler #XX+1 (Model: Opus 4.X)
**Date:** YYYY-MM-DD
**Reason for Switch:** [e.g., "Switching to 4.6 for complex coding work"]
---
## 🎯 CURRENT TASK
**Task:** [Task # and name]
**Status:** [In Progress / Blocked / Ready for Testing]
**Goal:** [What we're trying to accomplish]
---
## ✅ WHAT'S DONE
1. [Completed step]
2. [Completed step]
3. [Completed step]
---
## 🔧 WHAT'S IN PROGRESS
**Current file(s):**
- `path/to/file.js` — [what's being done to it]
- `path/to/another.md` — [status]
**Current state:**
[Describe exactly where things are — what's written, what's not]
**Code in progress (if any):**
```javascript
// Paste any uncommitted code here
```
---
## 🧠 DECISIONS MADE
| Decision | Rationale |
|----------|-----------|
| [Decision 1] | [Why we chose this] |
| [Decision 2] | [Why we chose this] |
---
## ⏭️ IMMEDIATE NEXT STEPS
1. [ ] [Next step]
2. [ ] [Next step]
3. [ ] [Next step]
---
## ⚠️ WATCH OUT FOR
- [Gotcha or known issue]
- [Thing that might break]
- [Decision that needs validation]
---
## 📁 RELEVANT FILES
| File | Location | Status |
|------|----------|--------|
| [File name] | [Full path] | [Committed / Uncommitted / In progress] |
---
## 💬 CONTEXT THE NEXT SESSION NEEDS
[Anything else the next Chronicler needs to know to pick up seamlessly]
---
**Handoff prepared by:** Chronicler #XX
**Time:** HH:MM
**All work committed to Git:** [Yes / No — if no, explain what's uncommitted]