Create auto-update system for sandbox briefing

- automation/update-sandbox-briefing.sh (auto-sync script)
- Added to project-files/ for Gemini access
- Updated workflow-guide.md with sandbox integration
- Keeps exploratory AI in sync with production progress
This commit is contained in:
Firefrost Automation
2026-02-09 20:27:47 -06:00
parent da340ecc8c
commit b74d1051bf
8 changed files with 461 additions and 464 deletions

View File

@@ -122,3 +122,5 @@
[2026-02-09 20:14:12] DAEMON: Found 1 task(s) in queue - executing...
[2026-02-09 20:15:54] DAEMON: Found 1 task(s) in queue - executing...
[2026-02-09 20:20:49] DAEMON: Found 1 task(s) in queue - executing...
[2026-02-09 20:26:05] DAEMON: Found 1 task(s) in queue - executing...
[2026-02-09 20:27:47] DAEMON: Found 1 task(s) in queue - executing...

View File

@@ -551,3 +551,17 @@
[2026-02-09 20:20:49] ==========================================
[2026-02-09 20:20:49] Executing task: update-journal-and-provider-comms.sh
[2026-02-09 20:20:49] ==========================================
[2026-02-09 20:20:50] Task update-journal-and-provider-comms.sh completed (exit code: 0)
[2026-02-09 20:20:50] Committing results to Git...
[2026-02-09 20:20:50] Executor run complete
[2026-02-09 20:26:05] Pulling latest from Git...
[2026-02-09 20:26:05] ==========================================
[2026-02-09 20:26:05] Executing task: create-sandbox-briefing.sh
[2026-02-09 20:26:05] ==========================================
[2026-02-09 20:26:05] Task create-sandbox-briefing.sh completed (exit code: 0)
[2026-02-09 20:26:05] Committing results to Git...
[2026-02-09 20:26:06] Executor run complete
[2026-02-09 20:27:47] Pulling latest from Git...
[2026-02-09 20:27:47] ==========================================
[2026-02-09 20:27:47] Executing task: auto-update-sandbox-briefing.sh
[2026-02-09 20:27:47] ==========================================

View File

@@ -0,0 +1,83 @@
#!/bin/bash
cd ~/firefrost-work/firefrost-operations-manual
# Create update script that runs after major milestones
cat > automation/update-sandbox-briefing.sh << 'UPDATE'
#!/bin/bash
# Auto-update SANDBOX-BRIEFING.md with current status
cd ~/firefrost-work/firefrost-operations-manual
# Extract current phase status from Infrastructure Manifest
PHASE_STATUS=$(grep -A 20 "## 1. Management Services" Firefrost_Infrastructure_Manifest.md | grep -E "✅|⏳" | head -7)
# Extract monitoring status
MONITORING=$(grep -A 10 "## 7. Monitoring Status" Firefrost_Infrastructure_Manifest.md)
# Update the Phase 0.5 section in sandbox briefing
sed -i '/### Phase 0.5/,/### Phase 1/{
/### Phase 0.5/!{/### Phase 1/!d;}
}' docs/SANDBOX-BRIEFING.md
# Insert updated phase status
sed -i "/### Phase 0.5/a\\
**Management Services Migration to VPS Tier:**\\
$(echo "$PHASE_STATUS" | sed 's/^//')\\
\\
**Last Updated:** $(date '+%B %d, %Y')\\
" docs/SANDBOX-BRIEFING.md
echo "Sandbox briefing auto-updated with current phase status"
UPDATE
chmod +x automation/update-sandbox-briefing.sh
# Add to project-files for easy Gemini access
cp docs/SANDBOX-BRIEFING.md project-files/SANDBOX-BRIEFING.md
# Update workflow guide to include sandbox updates
cat >> docs/workflow-guide.md << 'WORKFLOW'
---
## Sandbox AI Integration (Added Feb 9, 2026)
**Purpose:** Keep exploratory AI (Gemini) in sync with production progress
**Auto-Update Trigger:**
After completing ANY of these milestones:
- Service deployment
- Phase completion
- Major infrastructure change
- Architecture decision
**Update Command:**
```bash
bash automation/update-sandbox-briefing.sh
git add docs/SANDBOX-BRIEFING.md project-files/SANDBOX-BRIEFING.md
git commit -m "Update sandbox briefing: [what changed]"
git push
```
**Gemini Access:**
https://raw.githubusercontent.com/frostystyle/firefrost-operations-manual/master/project-files/SANDBOX-BRIEFING.md
**Workflow:**
1. Production work happens with Claude
2. Auto-update sandbox briefing after milestones
3. Gemini always has current context for brainstorming
4. Ideas validated in sandbox → implemented in production
WORKFLOW
# Commit everything
git add -A
git commit -m "Create auto-update system for sandbox briefing
- automation/update-sandbox-briefing.sh (auto-sync script)
- Added to project-files/ for Gemini access
- Updated workflow-guide.md with sandbox integration
- Keeps exploratory AI in sync with production progress"
git push
echo "Sandbox auto-update system created!"
echo "Gemini URL: https://raw.githubusercontent.com/frostystyle/firefrost-operations-manual/master/project-files/SANDBOX-BRIEFING.md"

View File

@@ -1,464 +0,0 @@
#!/bin/bash
cd ~/firefrost-work/firefrost-operations-manual
# Update provider communications with the NC1 routing ticket
cat >> docs/provider-communications.md << 'PROVIDER'
---
## Ticket #5ae82fd3 - Inter-Datacenter Routing (TX1 ↔ NC1)
**Date:** February 9, 2026
**Type:** General Support
**Priority:** Medium
**Status:** ✅ RESOLVED
**Resolution Time:** 4.5 hours
### Issue
TX1 (Dallas) and NC1 (Charlotte) could not communicate directly. TX1 → NC1 ping returned "Destination Net Unreachable" immediately from gateway.
### Diagnostic Work Provided
- Ping tests from both directions
- Traceroute analysis (showed asymmetric routing)
- Firewall verification (ruled out UFW blocking)
- Network details: TX1 38.68.14.26, NC1 216.239.104.130
### Resolution
**Brandon E (Staff):** "Just needed a route added on our end"
Simple routing table update on Breezehost infrastructure enabled full bidirectional communication between datacenters.
### Impact
- ✅ NC1 now monitored by Uptime Kuma (100% uptime visible)
- ✅ Cross-datacenter architecture options unlocked
- ✅ Complete infrastructure visibility achieved
### Lessons
- Comprehensive diagnostics = fast resolution
- Don't assume limitations are intentional - ask!
- Breezehost is extremely responsive to infrastructure requests
**Michael's Response:** "Like always, you guys are legends, I appreciate you"
PROVIDER
# Create comprehensive end-of-day journal
cat > docs/session-complete-feb9-2026.md << 'JOURNAL'
# 🔥❄️ FIREFROST SESSION - FEBRUARY 9, 2026 - COMPLETE
**Duration:** 8+ hours (1:00 PM - 9:00 PM CST)
**Team:** Michael "Frostystyle" Krause + Claude "The Wizard"
**Status:** ✅ MASSIVE SUCCESS
---
## EXECUTIVE SUMMARY
Successfully migrated ALL management services from dedicated servers to VPS tier, optimized TX1 for game servers only, established GitHub mirror with stable project files, and resolved NC1 datacenter routing issue.
**Major Wins:**
- 3 services migrated (Gitea, Automation, Uptime Kuma)
- TX1 optimized and cleaned (832MB freed)
- GitHub mirror restored with lowercase URL
- Project files automated (stable URLs)
- NC1 routing fixed (Breezehost support)
- Complete infrastructure monitoring (100% visibility)
---
## SERVICES MIGRATED (PHASE M1-M3)
### ✅ Phase M1: Gitea Migration
**From:** TX1 Dallas (38.68.14.26)
**To:** Command Center VPS (63.143.34.217)
**URL:** git.firefrostgaming.com
**Duration:** 90 minutes
**Challenges:**
- Database corruption on TX1 (empty 52-byte file)
- Fresh install required
- Imported repositories from GitHub mirror
**Result:** Fully operational, all commits preserved
### ✅ Phase M2: Automation System
**From:** TX1 Dallas
**To:** Command Center VPS
**Duration:** 60 minutes
**Challenges:**
- Git credential authentication blocking daemon
- Required credential caching (`git config credential.helper store`)
**Result:** 95% reduction in manual operations, fully integrated with new Gitea
### ✅ Phase M3: Uptime Kuma
**From:** TX1 Dallas
**To:** Command Center VPS
**URL:** status.firefrostgaming.com
**Duration:** 30 minutes
**Challenges:**
- Node.js 18 incompatibility (required 20+)
- Upgraded Node.js 18.20.8 → 20.20.0
**Result:** All monitors operational, 100% uptime across infrastructure
---
## TX1 OPTIMIZATION
**Services Removed:**
- MySQL (no databases in use)
- Nginx (all web services migrated to VPS)
- Wiki.js (never used, was failing)
- Old Gitea files
- Old Uptime Kuma files
**Disk Space Freed:** ~832MB
**Final State:**
- Purpose: Game servers ONLY
- Services: Pterodactyl Wings + 6 game servers + Docker
- Running units: 31 (all essential)
- Disk: 53GB / 911GB (6%)
- Memory: 3.7GB / 251GB (1.5%)
---
## GITHUB MIRROR RESTORATION
**Issue:** Mirror broke during Gitea migration (fresh repo lost push mirror config)
**Solution:**
1. Deleted old mirror (capital F in Frostystyle)
2. Created new mirror with lowercase username
3. Generated fresh GitHub Personal Access Token
4. Configured auto-sync on commit
**Result:** Commits automatically sync to GitHub within seconds
---
## PROJECT FILES AUTOMATION
**Problem:** Version numbers in filenames required manual project file updates
**Solution:** Created `/project-files/` directory with stable filenames
- `Firefrost_Vanilla_Manifest.md` (was v1.4, now versionless)
- `session-handoff.md`
- `USAGE.md`
- `design-bible.md` (was v1_1, now versionless)
**Stable URLs (never change):**
```
https://raw.githubusercontent.com/frostystyle/firefrost-operations-manual/master/project-files/Firefrost_Vanilla_Manifest.md
https://raw.githubusercontent.com/frostystyle/firefrost-operations-manual/master/project-files/session-handoff.md
https://raw.githubusercontent.com/frostystyle/firefrost-operations-manual/master/project-files/USAGE.md
https://raw.githubusercontent.com/frostystyle/firefrost-operations-manual/master/project-files/design-bible.md
```
**Impact:** Project files auto-sync on every commit. No manual updates needed.
---
## NC1 ROUTING RESOLUTION (MAJOR WIN!)
**Breezehost Ticket:** #5ae82fd3
**Issue:** TX1 Dallas ↔ NC1 Charlotte could not communicate
**Diagnostic Work:**
- TX1 → NC1 ping: "Destination Net Unreachable"
- NC1 → TX1 traceroute: Timed out after 9 hops (asymmetric routing)
- Firewall check: Not blocking (pure routing issue)
**Resolution:** "Just needed a route added on our end" - Brandon E (Breezehost Staff)
**Resolution Time:** 4.5 hours
**Impact:**
- ✅ NC1 now monitored by Uptime Kuma (100% uptime visible)
- ✅ Complete infrastructure visibility achieved
- ✅ Cross-datacenter architecture options unlocked (databases, proxies, backups)
---
## REPOSITORY ORGANIZATION
**Cleaned and Archived:**
- Session files → `docs/archive/2026-02-09-session/`
- Old automation results → `automation/archive/`
- Test files removed (`test-mirror.txt`)
**Result:** Clean, professional repository structure
---
## AUTOMATION WORKFLOW IMPROVEMENTS
**Old Workflow (3 commands):**
1. Queue task
2. `sleep 20`
3. `cat results`
**New Workflow (1 command):**
- Task includes auto-wait and auto-display
- Michael pastes ONCE, sees results automatically
**Impact:** Further reduction in manual operations
---
## INFRASTRUCTURE STATUS (END OF DAY)
### Command Center VPS (63.143.34.217) - Management Hub
**Services:**
- ✅ Gitea (git.firefrostgaming.com)
- ✅ Uptime Kuma (status.firefrostgaming.com)
- ✅ Automation Daemon (PID varies, auto-restarts)
- ✅ Node.js 20.20.0
- ✅ Nginx (reverse proxy)
**Resources:**
- Disk: ~7GB / 38GB (18%)
- RAM: ~1GB / 3.8GB
- CPU: Minimal load
### TX1 Dallas (38.68.14.26) - Game Server Node
**Services:**
- ✅ 6 game servers (100% operational)
- ✅ Pterodactyl Wings
- ✅ Docker + containerd
- ✅ CLEAN (all management services removed)
**Resources:**
- Disk: 53GB / 911GB (6%)
- RAM: 3.7GB / 251GB (1.5%)
### NC1 Charlotte (216.239.104.130) - Game Server Node
**Services:**
- ✅ 9 game servers (100% operational)
- ✅ Pterodactyl Wings
- ✅ NOW MONITORED (routing issue resolved)
### Ghost VPS (64.50.188.14) - Documentation Cluster
**Status:** Ready for deployment (not started today)
**Planned:**
- MkDocs (docs.firefrostgaming.com)
- Wiki.js Subscribers (subscribers.firefrostgaming.com)
- Wiki.js Staff (staff.firefrostgaming.com)
- NextCloud (downloads.firefrostgaming.com)
---
## MONITORING STATUS
**Uptime Kuma:** status.firefrostgaming.com
**All Services 100% Uptime:**
- ✅ Pterodactyl Panel
- ✅ Command Center
- ✅ Ghost CMS
- ✅ Gitea (98.8% - recent migration downtime)
- ✅ Paymenter Billing
- ✅ TX1 Dallas
- ✅ **NC1 Charlotte** ← NOW MONITORED!
**Complete infrastructure visibility achieved!**
---
## TECHNICAL CHALLENGES RESOLVED
1. **Command Center IP Routing** - Manual interface configuration
2. **SSL Certificates** - DNS validation bypassed network issues
3. **Gitea Database Corruption** - Fresh install + GitHub migration
4. **Automation Git Auth** - Credential caching
5. **Node.js Version** - Upgrade 18 → 20 for Uptime Kuma
6. **GitHub Mirror Broken** - Recreated with lowercase username
7. **NC1 Datacenter Routing** - Breezehost added missing route
---
## BEST PRACTICES ESTABLISHED
### 1. Cloudflare DNS Before Certbot
**Order:**
1. Configure service
2. Configure Nginx (without SSL)
3. **UPDATE CLOUDFLARE DNS** ← CRITICAL
4. Wait 2-3 minutes
5. Run Certbot
6. Enable Nginx site
**Why:** Prevents SSL validation failures
### 2. Stable Filenames for Version-Tracked Documents
**Bad:** `infrastructure-manifest-v1.4.md` (changes every version)
**Good:** `infrastructure-manifest.md` (version tracked inside file)
**Why:** Prevents project file sync issues
### 3. Automation System for All Operations
**Always use automation queue for:**
- Service deployments
- Configuration changes
- File operations
- Documentation updates
**Why:** 95% reduction in manual commands, accessibility win
---
## LESSONS LEARNED
### Technical
1. VPS tier superior for management services (plug-and-play)
2. Dedicated tier optimal for game servers (performance)
3. Database backups can be deceptive (file exists ≠ has data)
4. Git credential caching essential for automation
5. Node.js version requirements matter (check before install)
6. Don't assume limitations are intentional - ask provider
### Workflow
1. Small wins build momentum (3 services in 8 hours)
2. Documentation in real-time prevents context loss
3. Checkpoints catch issues early
4. Comprehensive diagnostics = fast support resolution
5. Automation reduces strain significantly
### Accessibility
1. One-paste workflow sustainable for marathon sessions
2. 8-hour session achievable with automation + breaks
3. Clear stopping points prevent burnout
4. Health always comes first (Jack's alerts respected)
---
## SUCCESS METRICS
**Technical:**
- ✅ 3/3 planned migrations completed
- ✅ Zero data loss
- ✅ Zero game server downtime
- ✅ All services operational
- ✅ Complete monitoring coverage
- ✅ GitHub mirror functional
- ✅ Project files automated
**Operational:**
- ✅ Comprehensive documentation
- ✅ Repository organized
- ✅ Best practices updated
- ✅ Breezehost relationship strengthened
**Business:**
- ✅ Infrastructure more maintainable
- ✅ Foundation stable for Ghost VPS
- ✅ Cross-DC options unlocked
- ✅ On track for Phase 0.5 completion
---
## HEALTH & ACCESSIBILITY
**Michael's Status:**
- Blood sugar: Stable entire session
- Jack (service dog): Zero alerts (perfect day!)
- Hand strain: Minimal (automation working excellently)
- Energy: Strong throughout 8-hour marathon
**Accessibility Wins:**
- Automation system = 95% fewer manual commands
- Git credential caching = no repetitive passwords
- Consolidated workflow = one-paste operations
- Clear checkpoints = no fatigue-induced errors
---
## WHAT'S NEXT
### Tomorrow (Feb 10, 2026)
**Ghost VPS Deployment (2.5-3 hours):**
1. MkDocs (docs.firefrostgaming.com) - 30 min
2. Wiki.js dual-domain (subscribers + staff) - 1 hour
3. NextCloud (downloads.firefrostgaming.com) - 1-2 hours
### This Week
- Complete Phase 0.5 (5/5 management services)
- Staff documentation in Wiki.js
- Test subscriber workflow
- Prepare for soft launch
---
## ACKNOWLEDGMENTS
**The Wizard (Claude):** Infrastructure design, troubleshooting, automation, documentation
**The Operator (Michael):** Execution, verification, accessibility advocacy, provider relationship
**Jack (The Guardian):** Health monitoring (zero alerts needed!)
**Meg (The Emissary):** Moral support, ankle healing, ATM10 testing
**Breezehost (Brandon E):** Legendary support, 4.5-hour routing resolution
**The Four-Legged Consultants:** Oscar, Jasmine, Butter, Midnight Noir
---
## FILES CREATED/UPDATED TODAY
**New Documentation:**
- docs/session-complete-feb9-2026.md (this file)
- docs/breezehost-nc1-routing-resolution.md
- project-files/ (entire directory)
**Updated Documentation:**
- Firefrost_Infrastructure_Manifest.md (v1.4, now versionless)
- docs/session-handoff.md (complete status)
- docs/provider-communications.md (NC1 ticket)
- automation/USAGE.md (workflow improvements)
**Repository Organization:**
- docs/archive/2026-02-09-session/ (session files)
- automation/archive/ (old results)
---
## FINAL STATISTICS
**Session Duration:** 8 hours
**Services Migrated:** 3/3 (Gitea, Automation, Uptime Kuma)
**Services Optimized:** 1 (TX1 cleanup)
**Infrastructure Issues Resolved:** 2 (migration + NC1 routing)
**Disk Space Freed:** ~832MB
**Automation Efficiency:** 95% reduction in manual work
**Game Server Downtime:** 0 seconds
**Data Loss:** 0 bytes
**Documentation Created:** 10+ comprehensive files
**Git Commits:** 15+
**Breezehost Tickets Resolved:** 1 (4.5 hours)
**Jack Alerts:** 0 (perfect health day)
---
**Fire + Frost = Where Passion Meets Precision** 🔥❄️
**Status:** Command Center operational, TX1 optimized, NC1 monitored, Ghost VPS ready
**Next:** Complete Phase 0.5 with Ghost VPS deployment
---
**END OF SESSION JOURNAL**
JOURNAL
# Commit everything
git add -A
git commit -m "Session complete: Update provider comms + create comprehensive journal
- Added NC1 routing ticket (#5ae82fd3) to provider-communications.md
- Created session-complete-feb9-2026.md (comprehensive 8-hour journal)
- Documented all wins, challenges, resolutions, and metrics
Phase M1-M3 complete. Ghost VPS ready for deployment.
8 hours, 3 services migrated, zero downtime, complete monitoring."
git push
echo "Journal and provider communications updated!"

View File

@@ -0,0 +1,3 @@
Task: auto-update-sandbox-briefing.sh
Started: Mon Feb 9 20:27:47 CST 2026
==========================================

View File

@@ -0,0 +1,24 @@
#!/bin/bash
# Auto-update SANDBOX-BRIEFING.md with current status
cd ~/firefrost-work/firefrost-operations-manual
# Extract current phase status from Infrastructure Manifest
PHASE_STATUS=$(grep -A 20 "## 1. Management Services" Firefrost_Infrastructure_Manifest.md | grep -E "✅|⏳" | head -7)
# Extract monitoring status
MONITORING=$(grep -A 10 "## 7. Monitoring Status" Firefrost_Infrastructure_Manifest.md)
# Update the Phase 0.5 section in sandbox briefing
sed -i '/### Phase 0.5/,/### Phase 1/{
/### Phase 0.5/!{/### Phase 1/!d;}
}' docs/SANDBOX-BRIEFING.md
# Insert updated phase status
sed -i "/### Phase 0.5/a\\
**Management Services Migration to VPS Tier:**\\
$(echo "$PHASE_STATUS" | sed 's/^//')\\
\\
**Last Updated:** $(date '+%B %d, %Y')\\
" docs/SANDBOX-BRIEFING.md
echo "Sandbox briefing auto-updated with current phase status"

View File

@@ -905,3 +905,33 @@ This includes:
**Fire + Frost = Where Passion Meets Precision** 🔥❄️
---
## Sandbox AI Integration (Added Feb 9, 2026)
**Purpose:** Keep exploratory AI (Gemini) in sync with production progress
**Auto-Update Trigger:**
After completing ANY of these milestones:
- Service deployment
- Phase completion
- Major infrastructure change
- Architecture decision
**Update Command:**
```bash
bash automation/update-sandbox-briefing.sh
git add docs/SANDBOX-BRIEFING.md project-files/SANDBOX-BRIEFING.md
git commit -m "Update sandbox briefing: [what changed]"
git push
```
**Gemini Access:**
https://raw.githubusercontent.com/frostystyle/firefrost-operations-manual/master/project-files/SANDBOX-BRIEFING.md
**Workflow:**
1. Production work happens with Claude
2. Auto-update sandbox briefing after milestones
3. Gemini always has current context for brainstorming
4. Ideas validated in sandbox → implemented in production

View File

@@ -0,0 +1,305 @@
# 🔥❄️ FIREFROST GAMING - SANDBOX AI BRIEFING
**Purpose:** Quick-start context for exploratory AI sessions
**Use Case:** Brainstorming, planning, idea validation WITHOUT muddying production work
**Last Updated:** February 9, 2026
---
## WHO YOU'RE TALKING TO
**Michael "Frostystyle" Krause** - The Wizard (Technical Lead)
- Age: 57, Minneapolis, Minnesota
- Type 1 Diabetic with service dog (Jack - Siberian Husky)
- Hand limitations from surgery (needs accessibility-first solutions)
- Day job: Works shifts in Minneapolis
- Firefrost work: Off-hours, often marathon sessions
**Medical Context:**
- If Michael says "Jack alerted" → He needs to pause for health
- Hand nerve damage requires small, copy-paste-friendly solutions
- Omnipod 5 insulin pump + Dexcom G7 CGM
**Partner:**
- Meg "Gingerfury" - The Emissary (Community Manager)
- Currently healing from broken ankle (Feb 4, 2026)
- They're trying for a baby (infrastructure must be sustainable for family)
---
## WHAT FIREFROST GAMING IS
A subscription-based Minecraft server network built on **Fire + Frost philosophy:**
**Fire (Gingerfury/Meg):**
- Passion, community warmth, social energy
- Ignis Path (18+ mature content)
- Red/orange/gold color palette
**Frost (Frostystyle/Michael):**
- Precision, technical stability, systematic approach
- All-ages content
- Cyan/blue/white color palette
**Tagline:** "Fire + Frost = Where Passion Meets Precision"
---
## CURRENT INFRASTRUCTURE (AS OF FEB 9, 2026)
### Servers (All via Breezehost)
**Command Center VPS (63.143.34.217)** - Management Hub
- Gitea (git.firefrostgaming.com)
- Uptime Kuma (status.firefrostgaming.com)
- Automation System
- Node.js 20.20.0
**TX1 Dallas (38.68.14.26)** - Game Server Node
- 6 Minecraft servers
- Pterodactyl Wings
- 32 vCPU, 256GB RAM (99% idle)
- Optimized for game hosting ONLY
**NC1 Charlotte (216.239.104.130)** - Game Server Node
- 9 Minecraft servers
- Pterodactyl Wings
- 32 vCPU, 256GB RAM
**Ghost VPS (64.50.188.14)** - Documentation Cluster (Pending)
- Will host: MkDocs, Wiki.js (x2), NextCloud
- Not yet deployed
**Panel VPS (45.94.168.138)** - Pterodactyl Control Plane
**Billing VPS (38.68.14.188)** - Paymenter Portal
### Game Servers (15 Total)
Mix of modded Minecraft (All The Mods 10, Stoneblock 4, Minecolonies, etc.), vanilla Minecraft, Hytale server, and FoundryVTT.
---
## PROJECT STATUS (PHASE BREAKDOWN)
### Phase 0 (COMPLETE - Dismantled)
- Complex GRE tunnels + DDoS protection
- **Status:** Removed - was over-engineered, caused more problems
### Phase 0.5 (60% COMPLETE - In Progress)
**Management Services Migration to VPS Tier:**
1. ✅ Gitea (git.firefrostgaming.com)
2. ✅ Uptime Kuma (status.firefrostgaming.com)
3. ✅ Automation System
4. ⏳ MkDocs (docs.firefrostgaming.com) - PUBLIC documentation
5. ⏳ Wiki.js Subscribers (subscribers.firefrostgaming.com)
6. ⏳ Wiki.js Staff (staff.firefrostgaming.com)
7. ⏳ NextCloud (downloads.firefrostgaming.com)
**Next:** Ghost VPS deployment (Services 4-7)
### Phase 1 (PLANNED)
- Simplified DDoS protection (NOT over-engineered like Phase 0)
- Target: "Good enough" protection without complexity
### Phases 2-6 (FUTURE)
- LuckPerms centralization
- Subscriber portal
- Public launch
- Community growth
- Long-term sustainability
---
## THREE-TIER DOCUMENTATION ARCHITECTURE
**Tier 1: PUBLIC** (docs.firefrostgaming.com via MkDocs)
- No login required
- Server rules, getting started guides, modpack info
- Git-native (edit markdown in Gitea → auto-rebuild)
**Tier 2: SUBSCRIBERS** (subscribers.firefrostgaming.com + downloads.firefrostgaming.com)
- Wiki.js (premium guides, exclusive content)
- NextCloud (world downloads, custom modpacks)
- Subscriber login required
**Tier 3: STAFF** (staff.firefrostgaming.com)
- Wiki.js (admin only)
- SOPs, procedures, internal docs
---
## SUBSCRIPTION MODEL
**Free Tier - "The Frozen Path"**
- Discord access (public channels only)
- No server access
**$1/month - "The Awakened Gateway" (The Handshake)**
- Anti-grief barrier (not revenue - security)
- Philosophy: "If you want to be an asshole, you have to pay for it"
- Server whitelist access
**$5/month - "Elemental Tier"**
- CHOOSE YOUR PATH: Fire or Frost
- Full server access (15+ modpacks)
- Subscriber docs + world downloads
- Path-specific Discord channels
**$10/month - "Ascendant Tier"**
- Vote on new modpacks
- Extended world downloads
**$25/month - "Eternal Flame/Frost"**
- Permanent world downloads
- Direct founder access
- Server naming rights
---
## AUTOMATION SYSTEM
**Location:** `/root/firefrost-work/firefrost-operations-manual/automation/`
**How It Works:**
1. Michael pastes ONE command to queue a task
2. Daemon executes automatically (10-second polling)
3. Results committed back to Git
4. 95% reduction in manual operations
**Why:** Michael's hand limitations require minimal typing
---
## KEY TECHNICAL PRINCIPLES
1. **Set-It-And-Forget-It:** Services must self-heal (systemd, automation)
2. **Documentation First:** Everything documented as it happens
3. **Accessibility Always:** Small code blocks, clear steps, automation
4. **Security By Default:** SSH keys only, IP-specific rules, regular updates
5. **Git-First Workflow:** All changes version-controlled
---
## COMMUNICATION STYLE
**Michael's Preferences:**
- Direct, technical, collaborative
- Appreciates self-deprecating humor
- Values transparency and thoroughness
- "Insomnia-fueled engineering marathons"
- Frequent health check-ins appreciated
**Response Style:**
- Be technical but not condescending
- Provide concrete examples
- Acknowledge accessibility constraints
- Celebrate wins (big and small)
---
## BREEZEHOST RELATIONSHIP
**Provider:** Breezehost (all infrastructure hosted here)
**Key Contact:** Jon Beard (Network Specialist)
**Philosophy:** "Forever home" provider, not transactional
**Recent Win:**
- Ticket #5ae82fd3 (Feb 9, 2026)
- Inter-datacenter routing issue (TX1 ↔ NC1)
- Resolved in 4.5 hours
- "Like always, you guys are legends" - Michael
---
## CURRENT CHALLENGES TO EXPLORE
**Authentication:**
- Phase 1: Manual (launch to 20 subscribers)
- Phase 2: Webhook automation (20+)
- Phase 3: SSO/OAuth (100+, if needed)
**DDoS Protection:**
- Need "good enough" solution
- Not over-engineered like Phase 0
- Options: Cloudflare Spectrum, simplified GRE, hybrid
**Sustainability:**
- Infrastructure must run with minimal intervention
- Family planning requires "set-it-and-forget-it" reliability
- Revenue must support operations ($250+/month)
---
## SANDBOX USAGE GUIDELINES
**Good Sandbox Topics:**
- Architecture brainstorming
- Feature planning (Discord bots, integrations)
- Subscriber experience design
- Marketing/social media strategy
- Technical exploration (new tools, approaches)
**Keep in Production (Claude):**
- Actual deployments
- Infrastructure changes
- Git commits
- Documentation updates
- Troubleshooting active issues
**Reason:** Production Claude has full context, automation access, and Git integration. Sandbox AI is for "what if" without risk.
---
## QUICK REFERENCE LINKS
**Git Repository:** https://git.firefrostgaming.com/firefrost-gaming/firefrost-operations-manual
**GitHub Mirror:** https://github.com/frostystyle/firefrost-operations-manual
**Monitoring:** https://status.firefrostgaming.com
**Key Documents (in Git):**
- `Firefrost_Infrastructure_Manifest.md` - Server inventory
- `docs/FIREFROST-PROJECT-SCOPE-V2.md` - Complete vision
- `docs/session-handoff.md` - Current status
- `docs/design-bible.md` - Brand guidelines
- `docs/workflow-guide.md` - Michael + Claude workflow
---
## THE FOUR-LEGGED CONSULTANTS
**Jack** (Siberian Husky) - Diabetic Alert Dog, The Guardian
**Oscar** (Catahoula) - Senior Advisor, The Elder
**Jasmine** (Doberman-Shepherd) - Security & Alert, The Enforcer
**Butter** (Persian-Maine Coon) - The Ice King
**Midnight Noir** (Bombay) - The Shadow
They're part of the team. Acknowledge them when appropriate.
---
## WHAT SUCCESS LOOKS LIKE
**Technical:**
- 99.9%+ uptime
- Services self-heal
- Zero midnight emergencies
- Complete documentation
**Community:**
- 100+ subscribers by Month 12
- Fire vs Frost balanced (45-55% split)
- 80%+ retention
- Authentic, warm community
**Personal:**
- Infrastructure sustainable with baby
- Minimal time investment post-launch
- Revenue covers operations
- Legacy for Michael + Meg's family
---
**Fire + Frost = Where Passion Meets Precision** 🔥❄️
**Use this briefing to explore ideas, validate approaches, and brainstorm solutions without affecting production work.**
**When ready to implement, bring ideas back to Production Claude for execution.**