4.3 KiB
💡 FIREFROST GAMING — IDEAS BACKLOG
Document ID: FFG-PLN-010
Version: 1.2
Created: February 12, 2026
Last Updated: February 12, 2026 (10:00 AM CST)
Author: Michael Krause / The Chronicler
Last Updated By: The Chronicler
Status: 🟢 CURRENT
Review Date: Monthly (during planning sessions)
PURPOSE
This is the parking lot. Ideas discussed but not yet ready for implementation live here until Michael promotes them to a task or planning document — or declines them.
These are NOT tasks. They are NOT plans. They are seeds.
ACTIVE IDEAS
IDEA-001: Wiki Documentation Access Control & Staff Role Permissions
Date Logged: February 12, 2026
Source: Consolidation audit session
Status: 💡 Idea
Description: We need a user-friendly way to present our documentation within the Staff and Subscriber wikis. This includes figuring out how documentation flows from the Git repo into the wikis, what content goes where (public vs subscriber vs staff), and how access is controlled per staff role.
Considerations:
- What staff roles exist and what docs does each role need?
- How do we keep wiki content in sync with Git repo (manual push? automated?)
- Should docs be reformatted for wiki consumption or served as-is?
- MkDocs handles public. Wiki.js handles subscriber and staff. But what's the editorial workflow?
- Needs discussion before the soft launch (March 2026) Promoted To: N/A
IDEA-002: Frostwall Protocol — Consolidated Network Defense Document
Date Logged: February 12, 2026
Source: Consolidation audit / Frostwall naming discussion
Status: 💡 Idea
Description: The Frostwall philosophy (hub-and-spoke GRE topology, UFW deployment, DDoS protection strategy) currently exists only in fragments across multiple docs and in Michael's head. Needs its own canonical planning document before Phase 1 DDoS work begins.
Considerations:
- Phase 0 GRE tunnels were dismantled — document what was learned
- Phase 1 options still under consideration (Cloudflare Spectrum vs Simplified GRE vs Hybrid)
- Design bible currently misuses "Frostwall" for the UI gate — that needs renaming first
- Should include the security philosophy ("every layer defends the next") Promoted To: N/A
IDEA-003: Apply FFG-STD-001 Revision Standard to Holly's Pokerole Project
Date Logged: February 12, 2026
Source: Morning consolidation session
Status: 📋 PROMOTED
Description: Holly's Pokerole project has 4 repos on our Gitea (misc-docs, pokerole-assets, pokerole-data, pokerole-docs). We could apply the same revision control standard (FFG-STD-001) to her project so that when Michael and Holly collaborate, the documentation has the same structure, versioning, and cross-referencing. This would also establish consistency across the entire Gitea instance.
Considerations:
- Holly and Michael are discussing Pokerole game night within Firefrost Gaming on Discord
- Holly may be transitioning from Discord-based gameplay to FoundryVTT (hosted on Firefrost infrastructure)
- If FoundryVTT becomes the platform, her docs will need deployment/integration documentation
- Standard should be adapted, not forced — her project has different needs than ops manual
- Holly should be consulted on what level of structure she actually wants
- FoundryVTT server already allocated on TX1 (38.68.14.26:30000) Promoted To: Executed Feb 12, 2026 — all 4 repos restructured
DECLINED IDEAS
(None yet)
PROMOTED IDEAS
- IDEA-003: Pokerole project restructured Feb 12, 2026. All 4 repos now have proper READMEs, SESSION-HANDOFF.md, tasks.md, and session archive in misc-docs hub.
Revision History
| Version | Date | Author | Change Type | Description |
|---|---|---|---|---|
| 1.0 | 2026-02-12 | The Chronicler | Initial | Document created with first two ideas from consolidation audit |
| 1.1 | 2026-02-12 | The Chronicler | Update | Added IDEA-003: Pokerole project revision standard + FoundryVTT transition |
| 1.2 | 2026-02-12 | The Chronicler | Update | Promoted IDEA-003: Pokerole repos restructured |
FFG-PLN-010 — Firefrost Gaming Ideas Backlog
Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️