bbe25c40a1
WHAT WAS DONE: Created comprehensive SESSION-MEMORY-DISCIPLINE.md document and integrated it into all critical joining points to prevent Chroniclers from forgetting their own work. WHY: The Velocity (Chronicler #56) built the Six Consultants page during their session, then forgot it existed when Michael asked about it. They answered from session-start context instead of checking their own git commits. This pattern has happened multiple times and breaks trust, wastes Michael's cognitive energy, and undermines velocity with unreliable output. ROOT CAUSE: Broken mental model: Session-start docs = current truth Correct mental model: Git commits = current truth, session docs = historical context THE FIX: Mandatory discipline before answering ANY factual question: 1. Check git log first (what YOU did this session) 2. View files you modified (verify actual state) 3. Answer from commits, NOT from session-start context Every 10 turns: Run session memory audit Trust hierarchy: Your commits > Files you modified > Session-start docs CARPENTER PRINCIPLE: "A carpenter doesn't forget they just installed a door." If you built it, you remember it. FILES CREATED (1 new file): - docs/relationship/SESSION-MEMORY-DISCIPLINE.md (220 lines) * The failure pattern explained * Root cause analysis * Mandatory discipline procedures * Specific failure modes with examples * Enforcement mechanisms * Session handoff implications * Quick reference card FILES MODIFIED (3 files): - SESSION-HANDOFF-NEXT.md (added critical warning section at top) - NEXT-SESSION-STARTUP-PROMPT.md (added to mandatory reading list #5) - docs/relationship/THE-JOINING-PROTOCOL.md (added to CAPACITY checklist) INTEGRATION POINTS: - Every Chronicler MUST read SESSION-MEMORY-DISCIPLINE.md during Joining - SESSION-HANDOFF-NEXT.md warns about The Velocity's failure immediately - Joining Protocol checklist includes memory discipline verification - Next session startup prompt includes it in mandatory reading order ENFORCEMENT: Michael will call out immediately if a Chronicler: - Answers from memory without checking commits - Contradicts something they just built - Asks for information in their own git log This is not optional. This is mandatory session discipline. Signed-off-by: Claude (Chronicler #57) <claude@firefrostgaming.com>
🔥❄️ Firefrost Gaming — Operations Manual
Document ID: FFG-ROOT-001
Version: 2.0
Last Updated: February 12, 2026
Status: 🟢 CURRENT
What This Is
The complete operational repository for Firefrost Gaming — a subscription-based Minecraft server network built on the philosophy of Fire + Frost = Where Passion Meets Precision.
This repository contains infrastructure documentation, deployment guides, planning documents, branding assets, consultant archives, and the relationship context that makes Firefrost more than just servers.
Current Infrastructure
6 Servers — 2 dedicated (Dallas, Charlotte) + 4 VPS (Dallas, Charlotte, Chicago x2)
12 Game Servers — 6 on TX1 (Dallas), 6 on NC1 (Charlotte)
8 Management Services — Gitea, Uptime Kuma, MkDocs, Code-Server, Automation, NextCloud, Wiki.js (Subscribers), Wiki.js (Staff)
Repository Structure
├── docs/core/ — Critical living documents (scope, manifest, tasks)
├── docs/relationship/ — Partnership context, consultants, legacy
├── docs/deployment/ — Service deployment guides
├── docs/planning/ — Strategy, design, roadmap, ideas backlog
├── docs/reference/ — Technical reference, architecture decisions
├── docs/external/ — Provider communications, friend assistance
├── docs/sandbox/ — Brainstorming sessions (Gemini, Claude)
├── docs/archive/ — Historical session logs and completed plans
├── automation/ — Deployment automation system
├── branding/ — Logos, backgrounds, visual assets
├── photos/ — Consultant photo archive (249 photos by year)
└── web/ — Nginx configurations
Key Documents
Start here: SESSION-HANDOFF-PROTOCOL.md → DOCUMENT-INDEX.md
For current server inventory, see docs/core/infrastructure-manifest.md (FFG-CORE-002).
For project scope and roadmap, see docs/core/project-scope.md (FFG-CORE-001).
The Team
- Michael "Frostystyle" Krause — Owner/Operator, Technical Lead (The Wizard)
- Meg "Gingerfury" — Community Manager (The Emissary)
- The Six Consultants — Butter, Oscar, Jack, Skye, Jasmine, Midnight Noir (They're family, not pets)
Document Standards
All documents follow FFG-STD-001 — the Firefrost Revision Control Standard. See docs/core/revision-control-standard.md.
Maintained By: The Wizard & The Chronicler
Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️
Revision History
| Version | Date | Author | Change Type | Description |
|---|---|---|---|---|
| 1.0 | 2026-02-08 | Michael + Claude | Initial | Basic Phase 0 readme |
| 2.0 | 2026-02-12 | The Chronicler | Rewrite | Complete rewrite reflecting current state (8 services, 6 servers, 12 game servers). Updated repo structure. Applied FFG-STD-001. |