f4e4cc7729
WHAT WAS DONE: - Created BLOCKERS.md at repo root (4 soft launch critical tasks) - Created BACKLOG.md at repo root (organized future work parking lot) - Archived old tasks.md to docs/archive/tasks-historical-march-30-2026.md - Archived 50 Gitea issues to docs/archive/gitea-issues-archive-2026-04-01.md - Replaced tasks.md with migration notice and redirects - Closed all 50 Gitea issues with migration message WHY: Old system problems: - 97 task entries with 8 duplicates (tasks 52, 65, 69, 71, 83, 85, 87, 88) - Heavyweight maintenance burden - Gitea Issues + Kanban unused and abandoned - Not accessible to non-technical team members (Meg, Holly) - Desynchronized duplicates (Tier S section vs sequential list) New system benefits: - Clear focus: 4 blockers vs 89 backlog items - Simple markdown (easy to update) - Preserved all historical context in archives - Planning Trinity Console v2 Task Module for non-technical interface SOFT LAUNCH REALITY CHECK: Based on Michael's input, soft launch is blocked by: 1. Ghost homepage (2-3h) - content ready 2. Legal pages (1-2h) - Terms/Privacy 3. Unsubscribe flow (2-3h) - cancellation UI 4. End-to-end test (2-3h) - workflow verification Total: 8-11 hours of focused work Target: April 15, 2026 (14 days) Social campaign starts: April 2, 2026 (TOMORROW) GITEA CLEANUP: - Closed 50 open issues (all had been abandoned) - Each issue received migration notice comment - All preserved in gitea-issues-archive-2026-04-01.md - Issues feature will be disabled (Kanban decommissioned) NEXT STEPS: - Update DOCUMENT-INDEX.md to reference new files - Plan Trinity Console v2 Task Module (Gemini consultation) - Start on actual soft launch blockers FILES ADDED: - BLOCKERS.md (74 lines) - BACKLOG.md (227 lines) - docs/archive/gitea-issues-archive-2026-04-01.md (50 issues archived) - docs/archive/tasks-historical-march-30-2026.md (3151 lines preserved) FILES MODIFIED: - docs/core/tasks.md (replaced with redirect notice) IMPACT: - Clean foundation for tracking work - Historical context fully preserved - Ready for non-technical task interface (Trinity Console v2) - Clear path to April 15 soft launch Signed-off-by: Claude (Chronicler #54) <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 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. |