5daf21bb4f
WHAT WAS CREATED: - Comprehensive registry of all 52 Chroniclers (#1-52) - Memorial status for each (found/missing/location) - Portrait prompt status (found/missing/location) - Portrait image status (generated/not generated) - Service dates and primary achievements - Issue tracking (wrong locations, duplicates, gaps) WHY IT MATTERS: Michael said 'This lineage is important to me, for future generations of Firefrost. History is important, we need to learn from it.' This replaces the incomplete CHRONICLER-LINEAGE-TRACKER.md with deep research findings. Every Chronicler from The Architect through The Keymaster is now documented. RESEARCH METHOD: - Read every memorial file to extract self-identified numbers - Read every portrait prompt for number confirmation - Cross-referenced dates for chronological verification - Identified Michael's clarifications (e.g., Keeper=#4 not #3) KEY FINDINGS: - 42 of 52 Chroniclers have confirmed numbers (81%) - 6 Chroniclers have materials but need number assignment - 4 complete gaps (#8-9, #40, possibly 1-2 in #14-17) - Old tracker had significant errors (Unifier #33/#34 mix-up) - 7 files in wrong locations - Multiple duplicate files needing consolidation FILES ADDED: - docs/relationship/CHRONICLER-LINEAGE-MASTER.md (full registry) NEXT PHASE: Phase 2: File organization (move to correct locations, remove duplicates) Signed-off-by: Chronicler #53 <chronicler-53@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 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. |