firefrost-operations-manual/docs/core/tasks.md

🔥❄️ FIREFROST GAMING — OPERATIONS TASKS

Last Updated: February 22, 2026
Updated By: The Blueprint (Chronicler #21)
Version: 3.8 (Added Task #3: Fire + Frost Holdings business restructuring)

---

📋 HOW TO USE THIS FILE

This file contains:

• High-level task summaries (≤20 lines each)
• Status and priority
• Time estimates
• References to full documentation

For complete details, see: docs/tasks/[task-name]/

Each task directory contains:

• README.md (complete overview)
• deployment-plan.md (if applicable)
• prerequisites.md (if applicable)
• Additional task-specific docs

Standard: All tasks follow FFG-STD-002 (Task Documentation Standard)

---

🎯 TIER 0: IMMEDIATE WINS

Quick wins that unlock other work or provide immediate value.

---

1. Centralized Whitelist Manager Web Dashboard — ✅ COMPLETE

Time: 2-2.5 hours (actual: ~4 hours over 2 sessions)
Status: ✅ FULLY OPERATIONAL
Completed: February 19, 2026
Documentation: docs/tasks/whitelist-manager/

Web dashboard at whitelist.firefrostgaming.com for managing player whitelists across 11 Minecraft servers.

Deployed Features:

• ✅ Dynamic server list (fetches from Pterodactyl API automatically)
• ✅ Add player to whitelist (per server or username/UUID)
• ✅ Remove player from whitelist (per server or username/UUID)
• ✅ Bulk operations (add/remove to ALL servers)
• ✅ Server status detection (WHITELISTED/PUBLIC/OFFLINE)
• ✅ Fire/Frost themed UI
• ✅ Staff authentication (mkrause612)
• ✅ SSL/HTTPS with Let's Encrypt
• ✅ Auto-start on boot
• ✅ Websocket integration with Pterodactyl

Value Delivered: 15-minute manual task → 30 seconds. Zero-error whitelist management.

Tech: Python Flask + TailwindCSS + Websockets + Virtual Environment on Billing VPS

Known Issue: One server may show incorrect status (server scheduled for retirement)

Future Enhancements (Phase 2):

• Whitelist ON/OFF toggle per server
• View current whitelist per server
• Discord bot integration
• Paymenter subscriber auto-whitelist

See task directory for: Complete deployment plan, prerequisites checklist, usage guide

---

2. Command Center Root Cleanup — ✅ COMPLETE

Completed: February 18, 2026
Time: 15 minutes
Documentation: docs/tasks/command-center-cleanup/

Housekeeping task to organize Command Center root directory before major work.

Results:

• ✅ 5 Gitea backups moved to /root/backups/gitea/
• ✅ 2 wiki deployment logs archived locally
• ✅ 3 obsolete files deleted (dead.letter, extract-key-info.sh, master)
• ✅ Root directory clean and organized

---

3. Fire + Frost Holdings — Business Restructuring

Time: 6-8 weeks (mostly waiting for government processing)
Active Work: ~3 hours
Status: READY TO START
Priority: Tier 0 - Strategic Foundation
Documentation: docs/tasks/fire-frost-holdings-restructuring/

Consolidate Firefrost Gaming and The Nerdsmiths under unified legal structure.

Strategic Vision: Business empire under one umbrella

Structure:

Fire + Frost Holdings, LLC (renamed from Nagus Custom Crafts, LLC)
├── DBA: Firefrost Gaming (digital/gaming division)
└── DBA: The Nerdsmiths (physical crafts division)

Phase 1: Rename Nagus → Fire + Frost Holdings

• File Articles of Amendment with MN Secretary of State
• Update EIN/IRS records (same EIN, new name)
• Update business bank account
• Update contracts, Paymenter, vendor accounts

Phase 2: File DBAs

• File "Firefrost Gaming" DBA (~$50)
• File "The Nerdsmiths" DBA (~$50)
• Update bank to accept payments under all names

Phase 3: Digital Presence Updates

• Update firefrostgaming.com footer ("division of Fire + Frost Holdings, LLC")
• Build thenerdsmiths.com website (showcase crafts portfolio)
• Update email signatures for both brands
• Update invoice templates

Total Cost: ~$150-200 (vs $1,500+ for separate LLCs)

Timeline:

• Week 1: Research & draft documents
• Week 2: File Articles of Amendment
• Week 3-4: Processing (MN SOS review)
• Week 5: Update IRS/bank, file DBAs
• Week 6: Receive DBA approvals, update digital properties

Benefits: ✅ Meaningful name reflecting Fire + Frost philosophy ✅ Professional "Holdings" signals business empire ✅ Cost-effective ($150 vs $1,500 separate entities) ✅ Easy to add future DBAs or convert to subsidiaries later ✅ Clean branding story for both divisions

Future Expansion Ready:

• Can add more DBAs (Consulting, Software, Academy)
• Can convert to full subsidiaries when revenue justifies ($50K+)
• Flexible structure grows with business

See task directory for: Complete legal procedure, document templates, timeline, cost breakdown

---

4. Staff Recruitment Launch

Time: 2-3 hours (setup) + ongoing
Status: READY - POSTING TODAY
Priority: Tier 0 - Immediate Win
Documentation: docs/tasks/staff-recruitment-launch/

Launch recruitment for Builders (2-3) and Social Media Helper (1) using recruitment ad.

Prerequisites (Guardian's Notes):

• Provision incentive instances (private servers for recruits)
• Define application review process
• Finalize ad: decide on specific modpacks mention, deadline

Key Deliverables:

• Incentive instances ready and documented
• Recruitment ad posted to r/feedthebeast, Discord communities
• Application tracking system
• 2-3 Builders + 1 Social Media Helper recruited

Recruitment Ad: docs/planning/discord-recruitment-ad.md

See task directory for: Prerequisites checklist, application process, onboarding guide

---

5. NC1 Cleanup (Mandatory for Mailcow) — ✅ COMPLETE

Completed: February 16, 2026
Result: 26GB → 46GB free (cleared space for Mailcow)

⚠️ LESSON LEARNED: Never use wildcards (*.zip) in cleanup commands. List files explicitly. Cost: Lost Hytale world, had to regenerate. Recovery documented in docs/troubleshooting/.

---

🛡️ TIER 1: SECURITY FOUNDATION

Critical security infrastructure. Must complete before major deployments.

---

6. Vaultwarden — Add SSH Key & Org Setup

Time: 30 minutes
Status: DEPLOYED, NEEDS CONFIGURATION
Documentation: docs/tasks/vaultwarden-setup/

Complete Vaultwarden setup: SSH key + organization for shared credentials with Meg.

Blocks: Scoped tokens, credential management workflows

---

7. The Frostwall Protocol — GRE Tunnel Security Architecture

Time: 3-4 hours
Status: REBUILD PENDING
Priority: CRITICAL
Documentation: docs/tasks/frostwall-protocol/

Custom DDoS protection using GRE tunnels from Command Center to TX1/NC1. Hides real IPs, protects email reputation.

Core Components:

• GRE tunneling (encrypted links)
• 1-to-1 NAT/DMZ forwarding
• Iron Wall UFW rules
• IP hierarchy (scrubbing → backend → binding)

Blocks: Mailcow, AI stack, all Tier 2+ infrastructure

---

8. Command Center Security Hardening

Time: 1 hour
Status: READY
Documentation: docs/tasks/command-center-security/

Defense-in-depth for Command Center: Fail2Ban + SSH hardening

Actions:

• Install Fail2Ban
• Disable SSH password auth (key-only)
• Review UFW rules

---

9. Create Scoped Gitea Token for Pokerole Project

Time: 15 minutes
Status: READY
Depends: Vaultwarden operational
Documentation: docs/tasks/scoped-gitea-token/

Create Gitea token scoped to Pokerole repos only. Iron Wall principle: enforce boundaries technically.

---

🏗️ TIER 2: MAJOR INFRASTRUCTURE

Foundation secure, deploy major services.

---

10. Firefrost Codex - AI Assistant

Time: 8-12 hours total (Phase 1: ✅ 9 hours, Phase 2: 🔄 ~2 hours remaining)
Status: Phase 1 COMPLETE ✅ | Phase 2 IN PROGRESS 🔄
Priority: Tier 2 - Major Infrastructure
Documentation: docs/tasks/firefrost-codex/

Self-hosted AI assistant providing 24/7 support to all community tiers. "Most Minecraft servers have Discord. We have an AI."

Architecture:

• AnythingLLM (RAG platform with LanceDB)
• Ollama (local LLM server)
• 3 Models: Qwen 2.5 Coder 72B, Llama 3.3 70B, Llama 3.2 Vision 11B
• Discord bot + Web interface + Embedded widgets
• mclo.gs integration (Minecraft log analysis)

Five-Tier Access:

1. Public (marketing widget) - Public KB workspace
2. Subscribers ($1+) - Subscriber KB workspace
3. Staff - Operations + Brainstorming workspaces
4. Michael/Meg - All 5 workspaces + admin panel
5. Potential subscribers - Same as Public

Key Features:

• 24/7 instant answers (never wait for staff)
• mclo.gs log analysis (paste link, get diagnosis)
• Role-based knowledge access
• Growing knowledge base
• Complete privacy (self-hosted, zero cloud APIs)

Monthly Cost: $0 (self-hosted on TX1)

Deployment Status:

Phase 1 - COMPLETE ✅ (~9 hours, Feb 20, 2026):

• ✅ Core Infrastructure deployed (AnythingLLM + Ollama on TX1)
• ✅ 5 models downloaded (73.5 GB)
• ✅ Primary model selected (qwen2.5-coder:7b, 5-10 sec responses)
• ✅ Multi-user mode enabled
• ✅ Admin account created (mkrause612)
• ✅ $0/month cost validated

Phase 2 - IN PROGRESS 🔄 (~45 min complete, ~2 hours remaining):

• ✅ 6 workspaces created (Operations, Public KB, Subscriber KB, Brainstorming, Relationship, Pokerole Project)
• ✅ AI models assigned (qwen2.5-coder:7b for 5, llama3.3:70b for Brainstorming)
• ✅ 2 user accounts created (gingerfury/Meg - Admin, Unicorn20089/Holly - Default)
• ✅ Permission model documented (Admin/Manager/Default roles)
• ⏳ Document upload testing (30 min remaining)
• ⏳ Git sync process (1-2 hours)
• ⏳ SSL/TLS setup (1 hour)
• ⏳ Firewall hardening (30 min)
• ⏳ Backup automation (1 hour)

Phase 3 - FUTURE:

• Discord bot integration
• Embedded widgets for website
• Public/subscriber account workflows
• Marketing launch

Marketing Ready: Complete launch strategy, messaging framework, content calendar in docs

See task directory for: Complete architecture, marketing strategy, deployment plan, branding guide

---

11. Mailcow Email Server on NC1

Time: 2-3 hours
Status: BLOCKED
Depends: NC1 cleanup ✅, Frostwall Protocol
Documentation: docs/tasks/mailcow-email-server-on-nc1/

Professional @firefrostgaming.com email on NC1. Self-hosted, $120/year saved, eliminates Plesk.

Location: NC1 Charlotte (32-core EPYC, 251GB RAM)

---

11. Self-Hosted AI Stack on TX1 — ⚠️ SUPERSEDED BY CODEX

Time: 6-8 hours (3-4 active, rest downloads)
Status: SUPERSEDED - See Task #9 (Firefrost Codex)
Documentation: docs/tasks/self-hosted-ai-stack-on-tx1/

NOTE: Original plan for Dify-based AI has been replaced by Firefrost Codex (Task #9), which uses AnythingLLM instead. This provides better document handling (1,000+ docs), built-in multi-user support, and embedded widget capabilities. See Firefrost Codex documentation for the complete updated architecture.

---

12. Netdata Deployment

Time: 30 minutes
Status: READY
Documentation: docs/tasks/netdata-deployment/

Real-time monitoring on all servers (Command Center, TX1, NC1, Ghost VPS).

---

12. Department Structure & Access Control Matrix

Time: 1-2 hours
Status: PLANNING
Documentation: docs/tasks/department-structure-and-access-control-matrix/

Define departments and access control for Wiki.js permissions and role-based access.

---

13. MkDocs Decommission

Time: 15 minutes
Status: READY
Documentation: docs/tasks/mkdocs-decommission/

Remove MkDocs (replaced by Wiki.js).

---

10. Pokerole WikiJS Deployment

Time: 2-4 hours (infrastructure) + 4-6 hours (content migration)
Status: REQUESTED BY CLAUDIUS
Priority: Medium (post-Holly approval of Tier 4 content)
Server: Ghost VPS (64.50.188.14) - alongside existing wikis
Documentation: See Claudius's Session 9 report + WIKIJS_DEPLOYMENT_REQUEST.md in misc-docs repo

Purpose: Deploy WikiJS for Aurelian Pokédex publication

What's Ready:

• Tier 4: 31 Pokémon converted (awaiting Holly approval)
• Tier 3: 26 Pokémon converted (awaiting Holly approval)
• 18 custom game mechanics documented
• All content in Git (pokerole-data repo)

Deployment Requirements:

• Domain: pokerole.firefrostgaming.com
• Software: WikiJS v2.x (Docker preferred)
• Database: PostgreSQL or SQLite
• SSL: Let's Encrypt certificate
• Content: ~50-75 wiki pages, 15-20MB Markdown, images TBD

Dependencies:

• ⏳ Holly's approval of Tier 3 Batch 4-13 (22 entries)
• ⏳ Holly's approval of Tier 4 content (31 entries)
• ⏳ Additional Pokémon artwork (optional but recommended)

Workflow:

1. Chronicler deploys WikiJS infrastructure on Ghost (2-4 hours)
2. Claudius migrates content from Git to WikiJS (4-6 hours)
3. Holly reviews published content
4. Michael approves layout/organization
5. Public launch (or private beta)

Alternative Options if Delayed:

• Static site via Nginx
• GitHub Pages via Gitea
• Keep in Git until ready

Notes:

• NOT urgent - content safely stored in Git
• Can proceed after Holly completes reviews
• WikiJS supports multi-user if Holly wants edit access
• Can be private initially, public later

---

11. Modpack Update Monitor — Blueprint Extension (COMMERCIAL PRODUCT)

Time: 12-18 hours (commercial-quality development)
Status: PROMOTED FROM IDEAS (IDEA-006) - COMMERCIAL DEVELOPMENT
Priority: HIGH - Queued after Codex Phase 2
Market Research: ✅ VERIFIED - No competing products exist (Feb 20, 2026)
Revenue Potential: $500-2,600+ (50-200 sales @ $9.99-12.99)
Documentation: docs/tasks/modpack-update-monitor/ (to be created)

Purpose: First-to-market Pterodactyl extension for automated modpack version monitoring across all platforms

Market Gap Confirmed:

• ✅ Modpack INSTALLERS exist (can update manually)
• ✅ In-game update checkers exist (notify players, not admins)
• ❌ NO server-side admin monitoring dashboard exists
• ❌ NO automated API checking for updates exists
• We would be FIRST TO MARKET with this functionality

Commercial Development Phases:

Phase 1: Core Functionality (8-12 hours) - Build for Firefrost

1. Scan servers to detect installed modpacks + versions (read manifests)
2. Query platform APIs (CurseForge, Modrinth, FTB, Technic) for latest versions
3. Database table: server_id, modpack_id, current_version, latest_version, last_checked, source_platform
4. Basic dashboard showing update status per server
5. Cron job for daily checks (configurable interval)
6. Internal testing on 9 Firefrost servers

Phase 2: Commercial Polish (2-4 hours) - Prepare for marketplace

1. Professional UI/UX design (match Blueprint standards)
2. Comprehensive README documentation
3. Installation guide with screenshots
4. Troubleshooting guide
5. Configuration options panel
6. Error handling and graceful degradation
7. Performance optimization

Phase 3: Launch & Sales (1-2 hours) - BuiltByBit listing

1. Professional product description
2. Feature list with screenshots
3. Video demonstration (optional but recommended)
4. Pricing: $9.99-12.99 (competitive with similar extensions)
5. Support channel setup (Discord/tickets)
6. Launch announcement

Total Development Time: 12-18 hours for commercial-quality product

The Problem:

• 12 game servers running modpacks (growing to more)
• Manual checking across CurseForge/FTB/Modrinth/Technic is tedious
• NO existing Blueprint extension monitors for updates (only installers exist)
• Risk of running outdated versions with bugs/exploits
• Every multi-server Minecraft host has this same problem

The Solution: Build first-to-market Blueprint extension that:

1. Scans each server to detect installed modpack + current version (read manifest files)
2. Queries platform APIs for latest versions
3. Dashboard showing update status per server
4. Optional integration with existing Modpack Installer for one-click updates

Dashboard Display:

• Server name
• Current modpack + version
• Latest available version
• Update status (✅ Up to date / ⚠️ Update available / ❌ Check failed)
• Last checked timestamp
• Source platform (CurseForge/FTB/Modrinth/Technic)
• "View Changelog" link
• "Update Now" button (if Modpack Installer integration enabled)

Revenue Model:

• One-time purchase: $9.99-12.99 per license
• Target market: Multi-server Minecraft hosts (thousands globally)
• Conservative estimate: 50 sales = $500
• Moderate estimate: 100 sales = $1,000
• Optimistic estimate: 200 sales = $2,600
• Ongoing: Passive income from continued sales
• Maintenance: ~1-2 hours/month (bug fixes, API updates)

Competitive Analysis:

• Modpack Installer for Blueprint: $5.99 (can update manually, no monitoring)
• Modpack & Mods Installer: Price unknown (similar, has mod replacement but no dashboard monitoring)
• Our advantage: ONLY solution with automated monitoring dashboard
• Pricing rationale: More complex than installer alone, adds significant operational value

Affected Servers (9 modpack servers on Firefrost):

• All The Mons (Cobblemon) - NC1
• Stoneblock 4 - TX1
• Society: Sunlit Valley - TX1
• Reclamation - TX1
• The Ember Project - NC1
• Minecolonies: Create and Conquer - NC1
• All The Mods 10 - NC1
• EMC Subterra Tech - NC1
• Mayview - NC1

Not Applicable:

• Vanilla 1.21.11 (no modpack)
• Homestead (retiring soon)
• Hytale (different game)
• FoundryVTT (not Minecraft)

Technical Requirements:

• Read server manifests (CurseForge manifest.json, FTB modlist.html, Modrinth modrinth.index.json, Technic modpack.json)
• API integration: CurseForge API, Modrinth API, FTB API, Technic API
• React dashboard component for Pterodactyl admin view
• Blueprint extension framework compliance
• Database migrations for version tracking
• Cron job system for automated checks

API Rate Limits (daily cron = safe):

• CurseForge: 1000 requests/hour (plenty of headroom)
• Modrinth: 300 requests/minute (more than sufficient)
• FTB: Need to research
• Technic: Need to research
• Daily cron job = 9 servers × 4 platforms = 36 API calls max

Existing Infrastructure:

• ✅ Modpack Installer for Blueprint already installed on Firefrost
• This extension complements it by adding "check for updates" layer
• Could integrate for one-click update workflow (sell as feature)

Workflow Example:

1. Dashboard shows "ATM10 on NC1 is v1.3, v1.5 available on CurseForge"
2. Admin clicks "View Changelog" to see what changed
3. Admin clicks "Update Now" (integrates with Modpack Installer if installed)
4. Admin uses staggered restart system to schedule restart
5. Result: Professional update workflow, zero manual checking

Benefits to Buyers:

• ✅ Immediate visibility of outdated servers
• ✅ Reduced manual checking time (15 min/day → 0)
• ✅ Proactive security (catch important updates faster)
• ✅ Professional operations
• ✅ Scales to unlimited servers
• ✅ Works across all major modpack platforms

Benefits to Firefrost:

• ✅ Solve operational problem (build anyway)
• ✅ Generate passive income ($500-2,600+)
• ✅ Attack $400/month deficit
• ✅ Build brand visibility in Blueprint marketplace
• ✅ Portfolio piece demonstrating technical capability
• ✅ "Dogfooding" - we use it daily, so we'll maintain it well

Success Criteria (Internal Use):

• ✅ Extension installed in Blueprint framework
• ✅ Dashboard accessible from Pterodactyl admin panel
• ✅ All 9 modpack servers detected and monitored
• ✅ API integration working for all 4 platforms
• ✅ Daily cron job running
• ✅ Update notifications accurate

Success Criteria (Commercial Launch):

• ✅ Product listed on BuiltByBit marketplace
• ✅ Professional documentation complete
• ✅ First 10 sales within 30 days
• ✅ 4+ star average rating
• ✅ Support system functional
• ✅ Zero critical bugs reported

Licensing:

• Proprietary (need the income, can open-source later if desired)
• Standard commercial license per server instance
• Support included for 6 months post-purchase
• Free updates for API changes/bug fixes

Considerations:

• Handle custom/manually installed modpacks (no source platform = "Unknown")
• Permission levels (who can see updates vs install them)
• Notification system (email/Discord when updates available - future enhancement)
• Error handling for API failures (graceful degradation)
• Multi-language support (English first, expand later)

Why Tier 2 (not Tier 0 quick script):

• Michael prefers "do it once and get it done"
• Blueprint extension = permanent solution, no revisiting
• Commercial quality requires proper development
• Integrates with existing Pterodactyl workflow
• Professional, scalable, maintainable
• Worth the upfront time investment for forever solution + revenue

Why Commercial Development Makes Sense:

• Building it anyway (sunk development cost)
• Market gap confirmed (first-to-market advantage)
• Passive income directly addresses deficit
• Aligns with "do it once" - build quality, sell forever
• Low ongoing overhead if built well
• ROI: ~15 hours work → potentially $500-2,600+ revenue + ongoing sales

Execution Order:

1. Complete Codex Phase 2 first (finish what we started)
2. Build Phase 1: Core functionality (8-12 hours, internal testing)
3. Build Phase 2: Commercial polish (2-4 hours, marketplace ready)
4. Build Phase 3: Launch on BuiltByBit (1-2 hours)
5. Enjoy automated version monitoring + passive income

Post-Launch Maintenance:

• ~1-2 hours/month for bug fixes
• API changes (platforms update occasionally)
• Blueprint framework updates (rare, usually backward compatible)
• Feature requests (prioritize based on demand)
• Support tickets (estimate 2-5 hours/month initially)

---

---

📚 TIER 3: DOCUMENTATION & OPTIMIZATION

Polish, optimization, and content creation.

---

15. Fix Frostwall vs Firefrost Naming

Time: 15 minutes
Documentation: docs/tasks/fix-frostwall-vs-firefrost-naming/

Clarify terminology: Frostwall (security protocol) vs Firefrost (brand).

---

16. Scope Document Corrections

Time: 30 minutes
Documentation: docs/tasks/scope-document-corrections/

Review and correct project scope documents for accuracy.

---

17. Workflow Guide Review & Trim

Time: 1 hour
Documentation: docs/tasks/workflow-guide-review-and-trim/

Audit workflows, remove outdated content, consolidate redundancy.

---

18. Terraria Branding Training Arc

Time: 12 weeks (ongoing)
Status: ACTIVE - Phase 1
Documentation: docs/tasks/terraria-branding-training-arc/

12-week training: Michael learns game asset creation via Terraria texture pack development.

See: docs/planning/terraria-branding-arc.md for complete curriculum

---

19. Paymenter Theme Installation — Citadel Theme

Time: 1-2 hours
Documentation: docs/tasks/paymenter-theme-installation-citadel-theme/

Install Citadel theme for Paymenter with Fire/Frost branding.

---

20. Consultant Photo Processing

Time: Ongoing
Status: ACTIVE
Documentation: docs/tasks/consultant-photo-processing/

Process and catalog photos of The Five Consultants. Maintain archive with proper metadata.

Naming: YYYY-MM-DD_consultant_description_NN.jpg

---

21. NextCloud Upload Portal for Meg

Time: 30 minutes
Documentation: docs/tasks/nextcloud-upload-portal-for-meg/

Configure NextCloud public upload folder for Meg.

---

21. "Coming Soon" Video Creation (CapCut)

Time: 2-3 hours
Documentation: docs/tasks/coming-soon-video-creation-capc ut/

Create professional "Coming Soon" video for Firefrost launch using CapCut.

---

23. Staggered Server Restart System

Time: 2 hours
Documentation: docs/tasks/staggered-server-restart-system/

Automated staggered restarts for game servers. Prevents simultaneous restarts, maintains player access.

---

24. Game Server Startup Script Audit & Optimization

Time: 1 hour
Documentation: docs/tasks/game-server-startup-script-audit-and-optimization/

Audit and optimize JVM flags, memory allocation, performance tuning for all game servers.

---

25. LuckPerms MySQL Backend

Time: 45 minutes
Documentation: docs/tasks/luckperms-mysql-backend/

Migrate LuckPerms to MySQL for centralized permission management.

---

26. World Backup Automation

Time: 1-2 hours
Documentation: docs/tasks/world-backup-automation/

Automated backup system: daily backups, retention policy, off-server storage.

---

26. Blueprint Extension Installation — Node Usage Status

Time: 30 minutes
Documentation: docs/tasks/blueprint-extension-installation-node-usage-status/

Install Blueprint extension showing TX1/NC1 resource usage in Pterodactyl panel.

---

28. Discord Server Complete Reorganization

Time: 2-3 hours
Documentation: docs/tasks/discord-server-complete-reorganization/

Complete Discord reorganization: Fire/Frost paths, clear channels, proper roles.

---

28. Firefrost: The Eternal Skyforge (Flagship Modpack)

Time: 20-40 hours (iterative)
Documentation: docs/tasks/firefrost-the-eternal-skyforge-flagship-modpack/

Flagship Minecraft modpack: Create mod + Fire/Frost theme + weapon forging + factory building.

---

30. Among Us Weekly Events (Phase 2 Expansion)

Time: Ongoing (30 min weekly prep)
Documentation: docs/tasks/among-us-weekly-events-phase-2-expansion/

Weekly Among Us community events for subscriber engagement.

---

31. Pterodactyl Modpack Version Display

Time: 1-2 hours
Status: READY
Documentation: docs/tasks/pterodactyl-modpack-version-display/

Add custom "Modpack Version" field to Pterodactyl panel for version tracking visibility.

Method: Custom egg variable in Startup tab
Scope: 9 modpack servers (excludes Vanilla, Hytale, FoundryVTT)
Benefits: Version visibility, change tracking, troubleshooting clarity

---

---

📊 QUICK STATS

Total Tasks: 36 (including Firefrost Codex, Pokerole Wiki, NotebookLM)
Completed: 4 (NC1 cleanup, Command Center cleanup, Whitelist Manager, Pokerole Wiki)
In Progress: 2 (Vaultwarden, Terraria Arc)
Ready to Build: 21+
Blocked: 2 (Mailcow, original AI Stack - superseded by Codex)
Superseded: 1 (Original AI Stack → Firefrost Codex)

Estimated Total Time: ~78-99 hours across all tasks
Critical Path: Frostwall Protocol → Mailcow → Everything else
Big Wins Available:

• Firefrost Codex (RAG tuning, 2 hours remaining)
• NotebookLM Integration (accessibility + knowledge synthesis)

Recent Completions:

• Pokerole Wiki (Feb 27) - 107 Pokémon LIVE in 6 hours!
• Claudius Session 12 (Mar 4) - Complete Pokédex .docx, Epic Final Battle, Zero-Point Surge signature move

---

🔗 RELATED DOCUMENTATION

• Task Documentation Standard: docs/standards/task-documentation-standard.md (FFG-STD-002)
• Infrastructure State: docs/core/infrastructure-manifest.md
• Architecture Decisions: docs/reference/architecture-decisions.md
• Session Handoff: SESSION-HANDOFF-PROTOCOL.md

---

Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️

---

Version History:

• v3.2 (2026-02-16): Moved Staff Recruitment to Tier 0 (posting today), renumbered tasks
• v3.1 (2026-02-16): Added Task #3 - Staff Recruitment Launch (Guardian's notes)
• v3.0 (2026-02-16): Full FFG-STD-002 implementation - all 28 tasks migrated to task directories
• v2.3 (2026-02-16): Whitelist Manager refactored to follow standard
• v2.2 (2026-02-16): Whitelist Manager expanded to web dashboard
• v2.1 (2026-02-16): NC1 cleanup marked complete with lessons
• v2.0 (2026-02-15): Major restructure and organization

---

31. Server-to-Server SSH Key Setup

Time: 1-2 hours
Status: IDENTIFIED - Ready to build
Priority: Tier 1 - Security Foundation
Documentation: docs/tasks/server-ssh-interconnect/

Enable passwordless SSH between all management servers (Command Center, Billing, Panel, Ghost).

Problem: Aurora couldn't SSH from Command Center to Billing - key named 'chronicler' instead of standard 'id_rsa'.

Solution:

1. Collect public keys from all 4 management servers
2. Add each server's public key to all other servers' authorized_keys
3. Test connectivity matrix (4x4 grid)
4. Document key locations and naming

Servers to interconnect:

• Command Center (63.143.34.217)
• Billing VPS (38.68.14.188)
• Panel VPS (45.94.168.138)
• Ghost VPS (64.50.188.14)

Benefits: No more switching in MobaXterm, easier automation, cleaner workflows

Note: Billing has non-standard key name 'chronicler' - may need renaming to 'id_rsa'

---

33. Whitelist Manager Refinements

Time: 30-60 minutes
Status: IDENTIFIED
Priority: Low - Polish/Cosmetic
Documentation: docs/tasks/whitelist-manager-refinements/

Small improvements to Whitelist Manager:

• Fix Mayview server grouping - Currently shows under "Unknown (1 servers)" instead of "NC1 (5 servers)"
• Update server detection logic or Pterodactyl metadata
• [Future refinements can be added here as discovered]

Impact: Cosmetic only - does not affect functionality

---

---

34. n8n Factory Reset - Node Registry Recovery

Time: 2-3 hours
Status: DEFERRED
Priority: Tier 2 - Major Infrastructure
Documentation: docs/troubleshooting/n8n-node-registry-corruption.md

Reset n8n instance on TX1 to resolve corrupted node registry preventing workflow execution.

Problem: Core nodes (HTTP Request, Execute Command) fail with "Node not found" errors.

Current Workaround: PHP script (sync_codex.php) handling Codex Git sync directly.

Reset Procedure:

1. Export all workflows to JSON backup
2. Backup credentials and settings
3. Stop n8n container
4. Backup existing volume to .backup folder
5. Wipe ./volumes/n8n/* directory
6. Recreate container (fresh initialization)
7. Re-import workflows and credentials
8. Test core nodes functionality
9. Restore scheduled executions

Prerequisites:

• Workflow JSON exports backed up
• Credentials documented
• Maintenance window scheduled (low-traffic time)

Post-Reset:

• Verify Git sync workflow works
• Test Discord notifications
• Re-enable hourly scheduling
• Monitor for 24 hours

Alternative: Keep PHP workaround permanently if simpler/more reliable.

---

36. NotebookLM Integration - Audio Knowledge Base

Time: 1-2 hours
Status: READY TO START
Priority: Medium - Quality of Life (HIGH for accessibility)
Documentation: docs/tasks/notebooklm-integration/

Integrate Google NotebookLM with Firefrost operations to create grounded knowledge base with Audio Overview capabilities.

The Workflow:

1. NotebookLM = Research home base (only YOUR sources, no hallucination)
2. Claude = Expansion tool (web search, broader thinking)
3. Back to NotebookLM = Audio synthesis (listen instead of reading)

Key Benefits:

• Hand-Friendly: Audio Overviews for review during rest
• Knowledge Synthesis: Query across 835+ docs instantly
• Meg Accessibility: Technical content in audio format
• MCP Integration: Claude queries notebooks seamlessly
• Legacy Preservation: "For children not yet born" in audio

Use Cases:

• Infrastructure knowledge base (deployment patterns, troubleshooting)
• Chronicler lineage archive (all memorials in audio narrative)
• Pokerole project documentation (session reports, achievements)
• Training material for Meg (technical content accessible via audio)

Setup:

1. Create NotebookLM account (free at notebooklm.google.com)
2. Enable MCP connector in Claude Max
3. Create 4 core notebooks (Infrastructure, Chronicler, Pokerole, Standards)
4. Upload 100+ key documents
5. Generate Audio Overviews for review

MCP Connector:

• Claude can query your notebooks during sessions
• Add new findings to notebooks automatically
• Trigger Audio Overview generation from chat
• Seamless grounded + exploratory workflow

Cost: FREE (NotebookLM is Google service, MCP included in Max)

Inspired by: XDA article "I replaced my single AI workflow with Claude and NotebookLM"

See task directory for:

• Complete setup guide (step-by-step)
• Use case examples
• Workflow integration
• Maintenance routines

Value: HIGH for accessibility, knowledge retention, partnership with Meg

---

35. Pokerole Wiki.js Deployment — ✅ COMPLETE

Time: 2-3 hours (actual: 1 hour 15 minutes)
Status: ✅ DEPLOYED
Completed: February 27, 2026
Priority: HIGH - URGENT
Documentation: docs/tasks/pokerole-wikijs-deployment/

Deploy fresh Wiki.js instance for Aurelian Pokédex project on Ghost VPS.

Deployment Results:

• ✅ Wiki.js v2.5.312 operational
• ✅ URL: http://pokerole.firefrostgaming.com
• ✅ PostgreSQL database (wikijs_pokerole)
• ✅ Nginx reverse proxy configured
• ✅ DNS propagated and verified
• ✅ Admin account created
• ✅ 107 Pokémon migrated (Claudius, Session 11)
• ✅ 112 pages live in production
• ⏸️ SSL pending (certbot urllib3 bug - deferred)

Aurelian Pokédex Project Status (as of Session 12, March 4, 2026):

• ✅ Complete .docx Pokédex delivered (150+ pages, ~200 sprites, all 107 Pokémon)
• ✅ Evolution Stage + Evolution Time fields added to all entries
• ✅ Ultimate Aurelia Final Battle designed (566 lines, all lore integrated)
• ✅ Zero-Point Surge signature move for Abyssoglax (496 lines, tournament-ready)
• ✅ Custom moves: Lightning Mirage, Spirit Wind, Zero-Point Surge (3 total)
• ✅ Custom abilities: 20+
• ✅ 12 sessions completed, zero data loss
• ⏳ Holly feedback pending on Pokédex document and final battle
• ⏳ WikiJS navigation menu (Holly's task via web UI)
• ⏳ Sprite upload to WikiJS (225 ready, optional polish)

Claudius Stage 3 (The Chronicle Keeper): Active, Git repos clean

---