Claude (Chronicler #35) 02250a96b3 docs: Add Task #89 - DERP Protocol Review & Formalization
WHAT WAS DONE:
- Added Task #89 to tasks.md (Tier 2 priority)
- Documented need to review DERP protocol usage
- Identified gap between intended and actual Gemini collaboration workflow
- Captured questions about gemini-workspace repo usage
- Connected to RV Dream (disaster recovery must work remotely)

WHY:
- gemini-workspace repo exists but sits empty
- Gemini consultations happening ad-hoc (e.g., March 31 monorepo session)
- No formalized workflow for Gemini collaboration
- DERP protocol may need updating based on actual usage patterns
- Firefrost Codex relationship to Gemini unclear

CONTEXT:
During gemini-workspace repo review (similar to brainstorming cleanup),
realized DERP protocol established Feb 2026 but never actually stress-tested
or formalized. Need comprehensive review to ensure disaster recovery strategy
is operational, not just theoretical.

FILES:
- docs/core/tasks.md (modified, +31 lines for Task #89)

Signed-off-by: The Golden Chronicler <claude@firefrostgaming.com>
2026-03-31 21:37:12 +00:00
2026-03-11 11:13:35 -05:00

🔥❄️ 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.mdDOCUMENT-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.
Description
No description provided
Readme 61 MiB
Languages
Shell 70%
Python 16.2%
Nunjucks 8.6%
JavaScript 2.5%
HTML 2.4%
Other 0.3%