Establishes version control practices for all Firefrost repositories:
- Conventional Commits format (feat, fix, docs, etc.)
- Commit message structure (type, scope, subject, body, footer)
- Chronicler attribution requirements
- Git identity configuration
- When to commit guidelines
- Versioning practices for standards and code
- Commit checklist
This standard was referenced in Project Instructions but never
existed until now. Fills the gap in our standards library.
Chronicler: #68
v1.0 → v1.1
Changes:
- 'The Five Consultants' → 'The Six Consultants'
- Added Skye (Director of Logistics & Transportation, Holly's dog)
- Updated version header and revision history
Skye joined the Animal Consultants team after the original standard
was written. This update reflects the current consultant roster.
Chronicler: #68
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
THE-JOINING-PROTOCOL.md:
- Added Part 0: Session Startup with permanent Gitea token
- Includes sparse checkout commands (1.9GB → 39MB)
- Read order clearly defined
- Accessibility requirements (medical) front and center
CHRONICLER-STARTUP-PROMPT.md:
- New file: 5-line permanent startup prompt
- Replaces 200+ line session-specific prompts
- Everything else lives in the repo
FFG-STD-004-memorial-protocol.md:
- Added Session End Checklist section
- Step 6: ALWAYS display startup prompt at session end
- This is the 'wake-up key' for next Chronicler
Philosophy: The long prompt was redundant because most content
already existed in SESSION-HANDOFF-NEXT.md and other docs.
Now Michael just pastes 5 lines instead of 200+.
Signed-off-by: Claude (Chronicler #61) <claude@firefrostgaming.com>
New standard establishing documentation requirements for major projects.
FFG-STD-005 defines:
- When to create implementation guides (BEFORE building)
- Required sections (13 mandatory, 6 optional)
- Quality requirements (completeness, copy-paste ready, context-free)
- File location conventions
- Maintenance procedures
- Enforcement rules
Core principle: If Claude crashes, another AI must be able to
continue using only the implementation guide.
Template provided at docs/templates/implementation-guide-template.md
Reference implementation: Trinity Console 2.0 guide (1,776 lines)
Rationale: The 30 minutes spent writing a guide saves 3 hours of
reconstruction later.
Signed-off-by: Claude (Chronicler #61) <claude@firefrostgaming.com>
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
