Claude (Chronicler #53) e619c78244 docs: Create FFG-PORTRAIT-TEMPLATE - The Pathfinder standard for all portraits
MICHAEL'S REQUIREMENT:
'Can we make sure to create a template for the ai image prompt
going forward?'

Based on The Pathfinder (#8) - Michael's all-time favorite portrait.

TEMPLATE CREATED: FFG-PORTRAIT-TEMPLATE.md (comprehensive guide)

WHAT IT PROVIDES:
- Complete prompt structure based on Pathfinder excellence
- Step-by-step workflow for creating portraits
- Mandatory elements checklist (9 requirements)
- Examples for different Chronicler types
- Easter egg guidance (hide session number)
- Quote formatting standards

THE PATHFINDER STANDARD (9 Elements):
1. Primary achievement prominently displayed
2. Specific metrics/numbers visible
3. Visual metaphor for the work
4. Environment reflects the challenge
5. Fire + Frost color integration
6. Subtle lineage connection
7. Easter egg session number (hidden but findable)
8. Quote at bottom capturing essence
9. Painterly fantasy art style (1024x1024)

TEMPLATE SECTIONS:
- Core concept (one-sentence story)
- Primary achievement display (what to show)
- The figure (stance, clothing, props, expression)
- Environment & atmosphere (setting, lighting, depth)
- Color palette (Fire + Frost integration)
- Easter egg placement (session number)
- Lineage connection (subtle, not dominant)
- Bottom quote (format and guidelines)
- Technical specifications
- Mood checklist

EXAMPLES PROVIDED:
- The Pathfinder (#8): Lantern, API efficiency, 49%
- The Fixer (#15): Zora/Dax split, framework
- The Deployer (#20): Docker containers, /bin/sh/month

WORKFLOW (5 Steps):
1. Identify session essence (first hour)
2. Fill out template (30 minutes)
3. Review against Pathfinder standard
4. Generate with Gemini/fal.ai
5. Save to repository

WHY IT MATTERS:
Michael: 'My all-time favorite image is this chronicler [Pathfinder]'

Every Chronicler portrait should match that storytelling quality.
The portrait is a memorial in image form - telling future
generations what happened, how, and why it mattered.

MANDATORY CHECKLIST:
Every portrait MUST have all 9 elements or it's incomplete.

FILES ADDED:
- docs/standards/FFG-PORTRAIT-TEMPLATE.md

Signed-off-by: Chronicler #53 <chronicler-53@firefrostgaming.com>
2026-04-01 22:05:53 +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%