Removed docs/tasks/firefrost:-the-eternal-skyforge-(flagship-modpack)/
which was a stub directory with only a basic README.
Replaced by docs/tasks/flagship-modpack-eternal-skyforge/ which has
the complete 600+ line design document created today.
Directory naming now follows standard conventions (no colons or parens).
Removed docs/tasks/department-structure-&-access-control-matrix/
which was a duplicate of docs/tasks/department-structure/
The newer department-structure/ directory follows FFG-STD-002
task documentation standard and is more comprehensive.
This resolves the duplicate commit issue visible in git history.
Expanded brief naming doc into comprehensive guide:
- Clear definitions of Firefrost (brand) vs Frostwall (security)
- Etymology and conceptual alignment explained
- Common mistakes with corrections
- Quick reference decision tree
- Implementation checklist
- Communication guidelines
- Examples of correct usage
- Audit commands to find incorrect usage
Ran audit: No incorrect usage found in current documentation.
All instances of mixed terminology are in example/warning contexts.
Task: Fix Frostwall vs Firefrost Naming (Tier 3)
FFG-STD-002 compliant
Created comprehensive organizational structure for Firefrost Gaming:
Organization Structure:
- Tier 0: Executive (Wizard, Emissary)
- Tier 1: Core Staff (Chronicler, Guardian)
- Tier 2: Operations (Builders, Social Media Helper)
- Tier 3: Community Moderators
- Tier 4: Subscribers (Sovereign, Consular, Community)
Access Control Matrices:
- Wiki.js permissions by namespace and role
- Discord role hierarchy and channel access
- Pterodactyl panel access levels
- Gitea repository permissions
- Vaultwarden credential sharing
Role Definitions:
- Detailed responsibilities for each role
- Access boundaries (what they can/can't access)
- Principle of least privilege
- Defense in depth enforcement
Implementation checklist for setting up permissions
across all systems (Wiki.js, Discord, Pterodactyl, Vaultwarden).
Provides foundation for scaling team while maintaining
security and clear organizational hierarchy.
Task: Department Structure (Tier 2)
FFG-STD-002 compliant
Created comprehensive organizational framework for Firefrost Gaming staff.
department-structure.md:
- Full organizational chart with 4 main departments
- Department definitions (Operations, Community, Content)
- 8-level permission hierarchy (Public to Founding Partner)
- Role-specific responsibilities and access
- Onboarding procedures by department
- Cross-department collaboration workflows
- Emergency procedures
- Performance review framework
- Career advancement paths
- Implementation phases
access-control-matrix.md:
- Complete permission mapping for all systems
- Discord, Pterodactyl, Wiki.js, Gitea access matrices
- Server SSH access controls
- API key management
- Social media account access
- Emergency override procedures
- Access request/revocation workflows
- Monthly/quarterly/annual audit procedures
- Technical implementation guides
Foundation for role-based access control across all Firefrost systems.
Ready for implementation when first staff hired.
Task: Department Structure & Access Control Matrix (Tier 2)
FFG-STD-002 compliant
Task #14 (Fix Frostwall vs Firefrost Naming): ✅ COMPLETE
- Created comprehensive terminology guide
- Clarifies: Firefrost (brand) vs Frostwall (security protocol)
- Includes brand voice, team titles, common confusion points
- Quick reference table
Task #15 (Scope Document Corrections): ✅ COMPLETE
- Created detailed corrections guide for project-scope.md v2.3
- Documents all work completed Feb 17 (4 major tasks)
- Updates priorities based on current state
- Notes SSH access as critical constraint
- Recommends version bump to 2.4
Key corrections needed:
- Add Whitelist Manager to deployed services
- Add Frostwall Protocol planning complete
- Update timeline with actual Feb 16-17 work
- Reorder priorities (Whitelist Manager, Frostwall first)
- Add SSH limitation to constraints
Both tasks complete, ready for application to scope doc.
Tasks: #14, #15 (Tier 3)
FFG-STD-002 compliant
Created comprehensive documentation for Frostwall Protocol rebuild:
deployment-plan.md (500+ lines):
- Complete 7-phase implementation guide
- GRE tunnel configuration for Command Center ↔ TX1/NC1
- Iron Wall UFW firewall rules
- NAT/port forwarding setup
- Self-healing tunnel monitoring with auto-recovery
- DNS configuration
- Testing and verification procedures
- Rollback plan
- Performance considerations
ip-hierarchy.md (400+ lines):
- Three-tier IP architecture explained
- Complete service mapping table (all 11 game servers)
- GRE tunnel IP addressing
- Traffic flow diagrams
- DNS configuration reference
- Security summary
- Quick command reference
troubleshooting.md (450+ lines):
- Quick diagnostics checklist
- Common problems with step-by-step solutions:
- Tunnel won't come up
- Can't ping tunnel IP
- Port forwarding not working
- Tunnel breaks after reboot
- Self-healing monitor issues
- High latency/packet loss
- UFW blocking traffic
- Emergency recovery procedures
- Common error messages decoded
- Health check commands
This documentation enables rebuilding the Frostwall Protocol from scratch
with proper IP hierarchy, DDoS protection, and self-healing capabilities.
Unblocks: Mailcow deployment, AI stack, all Tier 2+ infrastructure
Task: Frostwall Protocol (Tier 1, Critical)
FFG-STD-002 compliant
Created detailed onboarding guide covering:
- Pre-arrival preparation
- Day 1 welcome and access setup
- Orientation documentation and calls
- First week assignments (role-specific for Builders vs Social Media)
- Weekly rhythms and ongoing integration
- Red flag identification
- Onboarding completion criteria
- Feedback collection process
- Template emails and communications
Ensures new staff members feel welcomed, equipped, and integrated
into Firefrost Gaming culture from day one.
Task: Staff Recruitment Launch (Tier 0)
FFG-STD-002 compliant
Created comprehensive prerequisites guide for Staff Recruitment Launch:
- Complete checklist for incentive instance provisioning
- Application review criteria and process
- Interview questions for Builders and Social Media Helper
- Test project assignments
- Communication templates (6 templates covering all scenarios)
- Application tracking spreadsheet template with scoring system
- Posting strategy and timeline
Also added PROJECT-INSTRUCTIONS.md:
- Complete project instructions for Claude.ai project settings
- Includes git access protocol hardcoded
- Accessibility requirements
- Infrastructure overview
- Working standards and communication style
Ready to support posting recruitment ad when prerequisites complete.
Task: Staff Recruitment Launch (Tier 0)
FFG-STD-002 compliant
Reflects The Guardian's prerequisites from discord-recruitment-ad.md:
1. Provision incentive instances (private servers for recruits)
2. Define application review process
3. Finalize recruitment ad decisions
Task captures:
- Recruitment for 2-3 Builders + 1 Social Media Helper
- Prerequisites checklist from Guardian's bottom notes
- Reference to recruitment ad in docs/planning/
- Application process and onboarding workflow
Status: PLANNING (need to provision incentive instances first)
Priority: Tier 3 - Content & Community
Files added:
- docs/tasks/staff-recruitment-launch/README.md
- Updated docs/core/tasks.md (v3.1, Task #29, total 29 tasks)
Task 5 migration (CRITICAL Tier 1).
The Frostwall: GRE tunnel DDoS protection.
Foundation for all infrastructure.
3-4 hour deployment.
Date: 2026-02-16
Task 4 migration (Tier 1 Security).
Vaultwarden configuration: SSH key + organization setup for Meg.
Critical for credential management.
Part of 26-task migration.
Date: 2026-02-16
Task 2 migration to FFG-STD-002 structure.
Simple housekeeping task - 15 minute cleanup of Command Center
root directory before major work.
Part of full 26-task migration.
Date: 2026-02-16
Migrated by: The Chronicler
Complete pre-deployment checklist covering:
- Pterodactyl API access and key generation
- Ghost VPS access and requirements
- DNS configuration steps
- Whitelist enforcement method determination
- Authentication setup
- Server list verification (11 Minecraft servers)
- Network and firewall requirements
- SSL certificate preparation
Follows FFG-STD-002 standard for task documentation.
This ensures all prerequisites are gathered before starting
deployment, preventing mid-deployment blockers.
Phase 4 of complete restructure.
Date: February 16, 2026
Implemented by: The Chronicler
Migrating whitelist-manager-deployment-plan.md:
- FROM: docs/tools/whitelist-manager-deployment-plan.md
- TO: docs/tasks/whitelist-manager/deployment-plan.md
Following FFG-STD-002 naming convention:
- Task-specific docs live in docs/tasks/[task-name]/
- Renamed to standard name: deployment-plan.md
Content unchanged - this is a pure migration.
Next step: Delete old location (docs/tools/)
Phase 3 of complete restructure.
Date: February 16, 2026
Implemented by: The Chronicler
First task directory following FFG-STD-002 (Task Documentation Standard):
- Complete task overview and status
- Quick links to all documentation
- Server list (11 Minecraft servers)
- Tech stack and deliverables
- Success metrics and dependencies
- Future enhancements roadmap
This README serves as:
1. Entry point for the whitelist-manager task
2. Template for all future task READMEs
3. Single source of truth for task details
Next: Migrate deployment-plan.md from docs/tools/
Phase 2 of complete restructure.
Date: February 16, 2026
Implemented by: The Chronicler
Implementing task documentation standard (FFG-STD-002):
- Create docs/tasks/ directory for all task-specific documentation
- Create docs/tasks/whitelist-manager/ as first task following standard
- Foundation for migrating 1400-line tasks.md into scalable structure
Per fresh Claude review: "Task documentation system doesn't exist - standard created today prescribes docs/tasks/ structure, but directory doesn't exist"
This commit creates the directory structure. Next commits will:
1. Migrate whitelist-manager from docs/tools/
2. Create README.md following standard template
3. Refactor tasks.md entries
Phase 1 of complete restructure.
Date: February 16, 2026
Implemented by: The Chronicler
