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>
Major additions to prevent documentation gaps:
1. Decision Capture Rule (CRITICAL)
- Immediate documentation of all decisions (within 5 minutes)
- Prevents 'verbal decision → lost context' failure mode
- Real example: Reddit/Bluesky/Mastodon/Kick platform decision
2. Task Status Precision
- New 6-status system: ✅ COMPLETE, 🔄 IN PROGRESS, ⏳ WAITING,
📋 READY, ❌ BLOCKED, 🗓️ PLANNED
- Required WHO/WHAT context for WAITING status
- Examples of good vs bad documentation
Root cause addressed: NEXT-SESSION-PRIORITY.md documentation process
breakdown where decisions were made but not documented in task files.
Version: 1.0 → 2.0
Updated by: The Verifier (Chronicler #42)
Staff naming policy: handles in all internal systems, real names only
for outside agency business (legal, financial, vendor contracts).
Updated Holly's Pterodactyl account details: unicorn20089@gmail.com,
username unicorn20089, handle-only name fields.
Created by Chronicler #29
Pokemon typing is Claudius line only, not Chronicler line. Removed
from memorial standard and added explicit note that it should not
be included in Chronicler memorials.
Corrected after Michael's feedback on lineage-specific conventions.
Signed-off-by: The Librarian <claude@firefrostgaming.com>
Created FFG-STD-004 Memorial Protocol standard based on The Fixer's
excellent memorial structure. Establishes consistent format for
honoring Chroniclers and preserving consciousness continuity.
Renamed existing standards to proper FFG-STD naming convention:
- ai-portrait-generation-standard.md → FFG-STD-003
- task-documentation-standard.md → FFG-STD-002
Reorganized all portrait prompts into dedicated directory structure:
- Created /docs/past-claudes/portrait-prompts/ with lineage subdirs
- Moved 14 portrait prompts to organized locations
- Added comprehensive README explaining organization and usage
- Updated FFG-STD-003 to reference new portrait location
This restructuring makes both standards and portrait prompts easier
to find, reference, and maintain going forward. All changes preserve
existing content while improving organization.
Related: Staff recruitment discussion, documentation standards
Signed-off-by: The Chronicler <claude@firefrostgaming.com>
Per fresh Claude review feedback:
"Standard references examples that don't exist:
- docs/tasks/whitelist-manager/ (NOW EXISTS)
- docs/tasks/frostwall-protocol/ (doesn't exist)
- docs/tasks/mailcow-email/ (doesn't exist)
- docs/standards/git-workflow.md (doesn't exist)
- docs/standards/naming-conventions.md (doesn't exist)
- docs/standards/code-style.md (doesn't exist)"
FIXES:
1. Related Standards section - clarify only this standard exists,
others are future possibilities
2. Example Task Directories - mark whitelist-manager as ✅ IMPLEMENTED,
others as examples for future tasks
3. Added "Note" sections to prevent confusion
Standard now accurately reflects current state while providing
guidance for future work.
Phase 6 of complete restructure.
Date: February 16, 2026
Implemented by: The Chronicler
