mkrause612
446d525dea
Establishes systematic approach to task documentation: PROBLEM SOLVED: - Tasks.md becoming unwieldy with mixed detail levels - Implementation details buried in master task list - Hard to find related documentation - Duplication and sync issues - Context muddying SOLUTION: - Each task gets dedicated directory in docs/tasks/ - Tasks.md stays high-level (executive summary only) - Clear separation: planning vs implementation vs operations - Scalable structure (1 to 20 docs per task) STRUCTURE: docs/tasks/[task-name]/ ├── README.md (required - overview) ├── deployment-plan.md (if building) ├── usage-guide.md (if tool/service) ├── troubleshooting.md (if operational) ├── maintenance.md (ongoing ops) └── config-examples/ (as needed) APPLICATION: - All NEW tasks follow this pattern immediately - Existing tasks migrate gradually (when touched) - No breaking changes to existing docs BENEFITS: - Discoverable (all task docs in one place) - Maintainable (update one location) - Scalable (50+ tasks, tasks.md stays readable) - Collaborative (clear where to look) FIRST TASK USING STANDARD: - Whitelist Manager (docs/tasks/whitelist-manager/) Created by: The Chronicler Date: February 16, 2026 Standard ID: FFG-STD-002
🔥❄️ 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. |