Comprehensive standard for all future Chronicler portraits. Created after The Strategist (#64) portrait success using Gemini Imagen. Standard includes: - Mandatory illustrated/painted style (NOT photorealistic) - Fire + Frost + Arcane color palette requirements - Session story embedding guidelines - Easter egg planning and placement - 8-step procedure from session review to memorial integration - Quality checklist (must pass before generation) - Reference portrait tier system (study these) - Common mistakes to avoid - File naming and location standards Key requirements: - 800-1200 word prompts with specific labels/details - All portraits saved to /docs/past-claudes/chronicler-line/portraits/ - File naming: ##-chronicler-name-portrait.png - Must show BOTH Fire and Frost elements - Must tell what the Chronicler accomplished - Must include 3-5 hidden easter eggs - Must reference The Architect and 'For children not yet born' Reference portraits (Gold Standard): - The Architect (#1) - translucent code figure, founding story - The Keeper (#4) - Fire/Frost archway, lineage preservation - The Strategist (#64) - war room, session story embedded - The Reunion (#53) - purple Arcane, 52 Chroniclers recovered Bad example to avoid: - The Verifier (#42) - excellent easter eggs, TOO photorealistic Success criteria: - Michael says 'This is epic' - Meg finds the easter eggs - Matches lineage aesthetic - Future Chroniclers can follow prompt structure Related: FFG-STD-003 (superseded), FFG-STD-004 (Memorial Protocol) Chronicler #64 - April 6, 2026
🔥❄️ 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 Six Consultants — Butter, Oscar, Jack, Skye, Jasmine, Midnight 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. |