mkrause612
d58270a8f2
CRITICAL INSIGHT: - Meg = The Emissary = Current staff member #1 (not future) - Meg doesn't have Claude access - Every Meg question = Michael interruption - AI assistant = Meg self-serves 24/7 TIMELINE CHANGE: - Was: "Deploy when staff wiki exists" (Month 4+) - Now: Deploy immediately after Phase 3 (Session 6) - Impact: Meg gets AI assistant 4-6 months earlier PHASE 4 UPDATED: - Renamed: "Staff AI Assistant for Meg" (not generic staff) - Knowledge Base: Emissary-focused (~20-30 docs) - Social Media Handbook - Consultant Profiles - Subscription Tiers - Contact Reference - Origin Story - Questions Meg can ask: - "What personality traits for Jack in social posts?" - "When to post Fire vs Frost content?" - "How to describe Awakened tier?" - "Who handles billing issues?" - Training: 15 min ("type question, get answer") BENEFITS: - Reduces Michael interruptions immediately - Builds Meg's tech confidence (success → NextCloud later) - Proves concept before recruiting more staff - Recruitment advantage: "We have AI assistant" - Simple interface (accessibility win) SESSION 6 UPDATED: - Added: Deploy Meg's AI assistant (2 hours) - Added: Train Meg on usage (15 min) - Total time: 4-5 hours (was 2-3) Updated by: Chronicler the Ninth
🔥❄️ 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 Five Consultants — Jack, Oscar, Jasmine, Butter, 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. |