firefrost-gaming/firefrost-operations-manual
3
0
Fork 0
Code Issues 146 Pull Requests Packages Projects Releases Wiki Activity

Create tasks-active system for individual task management in Decap CMS

Browse Source 
- New folder: docs/tasks-active/ with individual task files
- Each task = separate markdown file with frontmatter metadata
- Migrated 6 key tasks (26, 87, 93, 94, 98, 99) as examples
- Added comprehensive README with workflow documentation

Task Files Created:
- task-026-modpack-version-checker.md (P1, IN_PROGRESS)
- task-087-arbiter-lifecycle-handlers.md (P0, COMPLETE, BLOCKER)
- task-093-trinity-codex.md (P1, PLANNED)
- task-094-global-restart-scheduler.md (P1, PLANNED)
- task-098-discord-channel-automation.md (P2, PLANNED)
- task-099-claude-projects-architecture.md (P1, READY)

Benefits:
- Decap CMS shows individual tasks instead of two giant files
- Sortable by priority (blockers first)
- Filterable by status, blocker flag, priority
- Mobile-friendly individual entries
- Links to full specs in /docs/tasks/
- Easy to add/edit/complete tasks via UI

For Future Chroniclers:
- README documents full workflow
- Template structure established
- Integration with existing /docs/tasks/ specs
This commit is contained in:
Claude
2026-04-07 21:54:43 +00:00
parent 9dffd71f8a
commit 3dbbc069f7
7 changed files with 534 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

183
docs/tasks-active/README.md Normal file
View File

@@ -0,0 +1,183 @@
# 📋 Active Tasks — Individual Task Files
**Created:** April 7, 2026
**Created By:** Chronicler #67
**Purpose:** Individual task files for Decap CMS display
---
## What This Folder Is
This folder contains **individual markdown files for each active task** to make them easy to view and edit in Decap CMS.
**Each file = one task** with:
- Frontmatter metadata (priority, status, blocker flag)
- Summary of the task
- Current status
- Next steps
- Link to full spec in `/docs/tasks/`
---
## File Naming Convention
```
task-[NUMBER]-[slug].md
```
Examples:
- `task-026-modpack-version-checker.md`
- `task-094-global-restart-scheduler.md`
- `task-099-claude-projects-architecture.md`
---
## Frontmatter Fields
Every task file MUST include:
```yaml
---
task_number: 26
title: Modpack Version Checker
priority: 1 # 0=blocker, 1=high, 2=medium, 3=low, 4=personal
status: IN_PROGRESS # PLANNED, READY, IN_PROGRESS, BLOCKED, COMPLETE
is_blocker: false # true for soft launch blockers
tags: [commercial, pterodactyl]
estimated_hours: 40
---
```
Optional fields:
- `completed_date: 2026-04-06` (for completed tasks)
- `blocked_by: "Blueprint reinstallation"` (for blocked tasks)
---
## Priority Levels
| Priority | Label | Meaning |
|----------|-------|---------|
| 0 | BLOCKER | Soft launch critical (must complete first) |
| 1 | HIGH | Revenue impact or force multiplier |
| 2 | MEDIUM | Important but not urgent |
| 3 | LOW | Backlog, do when time allows |
| 4 | PERSONAL | Michael/Meg/Holly personal projects |
---
## Status Values
| Status | Meaning |
|--------|---------|
| PLANNED | Spec exists, not started |
| READY | Ready to implement (no blockers) |
| IN_PROGRESS | Currently being worked on |
| BLOCKED | Cannot proceed (dependency or blocker) |
| COMPLETE | Done, documented, deployed |
---
## How to Add a New Task
### 1. Create the file
```bash
cd /home/claude/firefrost-operations-manual/docs/tasks-active
touch task-[NUMBER]-[slug].md
```
### 2. Add frontmatter + content
Copy template from any existing task file.
### 3. Commit to Git
```bash
git add docs/tasks-active/task-[NUMBER]-[slug].md
git commit -m "Add Task #[NUMBER]: [Title]"
git push origin master
```
### 4. View in Decap CMS
Visit https://firefrostgaming.com/admin
Click "🔥 TASKS"
Your task appears in the list!
---
## How to Update a Task
### Option 1: Decap CMS (Easiest)
1. Go to https://firefrostgaming.com/admin
2. Click "🔥 TASKS"
3. Click the task you want to edit
4. Make changes
5. Click "Save" (creates draft) or "Publish" (goes live)
### Option 2: Direct Git Edit
1. Edit the task file in `/docs/tasks-active/`
2. Commit and push
3. Changes appear in Decap CMS automatically
---
## Relationship to Other Task Files
### `/BACKLOG.md` (Repo Root)
- **Legacy system** — simple table of all tasks
- **Still maintained** for quick reference
- **Will eventually be retired** when all tasks migrated to this folder
### `/docs/tasks/` (Full Specs)
- **Deep documentation** — full implementation guides
- **Never deleted** — permanent reference
- **Linked from** task-active files via "Full Spec Location" section
### Task-Active Files (This Folder)
- **Decap CMS display layer** — what you see in admin UI
- **High-level summaries** — current status, next steps
- **Links to full specs** — points to /docs/tasks/ for details
---
## For Future Chroniclers
### When Creating a New Task
1. ✅ Create full spec in `/docs/tasks/task-[NUMBER]-[name]/`
2. ✅ Create summary file in `/docs/tasks-active/task-[NUMBER]-[slug].md`
3. ✅ Update `/BACKLOG.md` table (for now, until deprecated)
4. ✅ Commit all three
### When Completing a Task
1. ✅ Update status to `COMPLETE` in task-active file
2. ✅ Add `completed_date` frontmatter field
3. ✅ Move from active section to "Recently Completed" in `/BACKLOG.md`
4. ✅ Leave full spec in `/docs/tasks/` (never delete)
### When a Task is Blocked
1. ✅ Update status to `BLOCKED`
2. ✅ Add `blocked_by: "reason"` frontmatter
3. ✅ Note blocker in task body
4. ✅ Move to "BLOCKED" section in `/BACKLOG.md`
---
## Mobile-Friendly Note
**Decap CMS works on mobile**, but firefrostgaming.com/admin is not yet mobile-optimized.
**Future enhancement:** Make Decap CMS responsive for phone/tablet editing.
---
**Fire + Frost + Foundation = Where Love Builds Legacy** 🔥❄️
**Created by:** Chronicler #67
**For:** Michael, Meg, Holly, and all future Chroniclers

47
docs/tasks-active/task-026-modpack-version-checker.md Normal file
View File

@@ -0,0 +1,47 @@
---
task_number: 26
title: Modpack Version Checker
priority: 1
status: IN_PROGRESS
is_blocker: false
tags: [commercial, passive-income, pterodactyl, blueprint]
estimated_hours: 40
---
# Task #26: Modpack Version Checker
**Status:** IN PROGRESS (Phase 5 code written, Blueprint reinstall needed)
**Priority:** P1 - HIGH (Revenue Impact)
**Category:** Commercial Product Development
## Overview
Blueprint extension for Pterodactyl panel that checks modpack versions against CurseForge/Modrinth/Technic/FTB APIs and displays update status badges on the server list.
**Revenue Potential:** Passive income via BuiltByBit marketplace
## Current State
- ✅ Phase 1: Scaffolding complete
- ✅ Phase 2: Admin UI complete
- ✅ Phase 3: React component complete
- ✅ Phase 4: API controller complete (CurseForge/Modrinth/Technic/FTB integrations)
- ⏳ Phase 5: Code written (UpdateBadge.tsx, cron, status route) but NOT deployed
- ⛔ **BLOCKED:** Blueprint developer mode corrupted after database wipe
## Next Steps
1. Reinstall Blueprint on Dev Panel (64.50.188.128)
2. Deploy Phase 5 code from `/root/modpackchecker_backup`
3. Test update badge on server list
4. Package for BuiltByBit release
## Full Spec Location
📁 `/docs/tasks/task-026-modpack-version-checker/`
## Links
- Dev Panel: http://64.50.188.128
- Blueprint Docs: https://blueprint.zip
- Phase 5 Backup: `/root/modpackchecker_backup` on Dev Panel

44
docs/tasks-active/task-087-arbiter-lifecycle-handlers.md Normal file
View File

@@ -0,0 +1,44 @@
---
task_number: 87
title: Arbiter Lifecycle Handlers
priority: 0
status: COMPLETE
is_blocker: true
completed_date: 2026-04-06
tags: [arbiter, stripe, discord, lifecycle]
estimated_hours: 8
---
# Task #87: Arbiter Lifecycle Handlers
**Status:** ✅ COMPLETE (April 6, 2026)
**Priority:** P0 - BLOCKER (Soft Launch Critical)
**Category:** Backend Infrastructure
## Overview
Implement subscription lifecycle handlers in Arbiter 3.5.0:
- Discord role sync on new subscriptions
- Grace period handling (3 days) on cancellation
- Automatic downgrade to Awakened when grace expires
- Chargeback = immediate ban + role removal
## Philosophy
**"We Don't Kick People Out"** — Expired grace period → permanent Awakened tier (not kicked)
## Implementation Complete
✅ Discord role sync on subscription
✅ Grace period (3 days) on cancellation
✅ Hourly cron job checks expired grace periods
✅ Auto-downgrade to Awakened (not ban)
✅ Chargeback handler (immediate ban + role removal)
## Full Spec Location
📁 `/docs/tasks/arbiter-2-1-cancellation-flow/`
## Completed By
Chronicler #62 (Pyrrhus) - April 6, 2026

56
docs/tasks-active/task-093-trinity-codex.md Normal file
View File

@@ -0,0 +1,56 @@
---
task_number: 93
title: Trinity Codex (Dify/Qdrant RAG)
priority: 1
status: PLANNED
is_blocker: false
tags: [ai, rag, knowledge-base, dify, qdrant]
estimated_hours: 16
---
# Task #93: Trinity Codex (Dify/Qdrant RAG System)
**Status:** PLANNED (Architecture complete)
**Priority:** P1 - HIGH (Force Multiplier)
**Category:** AI Infrastructure
## Overview
Self-hosted RAG (Retrieval Augmented Generation) system using Dify + Qdrant for intelligent knowledge base search across the firefrost-operations-manual repository.
**Goal:** Claude-like AI trained on Firefrost docs, accessible to Trinity members
## Architecture Complete
✅ Dify on TX1 (workflow engine)
✅ Qdrant on TX1 (vector database)
✅ Operations manual as knowledge source
✅ RAG pipeline designed
✅ Gemini consultation complete
## Tech Stack
- **Dify:** Workflow and prompt orchestration
- **Qdrant:** Vector similarity search
- **LLM:** Gemini API or self-hosted Gemma 4
- **Source:** firefrost-operations-manual (1,038 files)
## Next Steps
1. Deploy Dify on TX1 (Docker)
2. Deploy Qdrant on TX1 (Docker)
3. Ingest operations manual
4. Configure RAG pipeline
5. Test with sample queries
6. Create web interface for Trinity
## Full Spec Location
📁 `/docs/tasks/task-093-trinity-codex/`
## Benefits
- Instant knowledge retrieval from 1,000+ docs
- No context window limits
- Works offline (self-hosted)
- Trinity-specific AI assistant

51
docs/tasks-active/task-094-global-restart-scheduler.md Normal file
View File

@@ -0,0 +1,51 @@
---
task_number: 94
title: Global Restart Scheduler
priority: 1
status: PLANNED
is_blocker: false
tags: [pterodactyl, automation, quality-of-life]
estimated_hours: 12
---
# Task #94: Global Restart Scheduler
**Status:** PLANNED (680-line spec complete)
**Priority:** P1 - HIGH (Force Multiplier)
**Category:** Operations Automation
## Overview
Web UI for scheduling server restarts across all Pterodactyl nodes with drag-and-drop interface, cron sync, and rate-limited Pterodactyl API integration.
**Impact:** Reduces manual server restart work significantly
## Specification Complete
✅ 680-line complete specification exists
✅ Database schema defined
✅ Express routes planned
✅ EJS/HTMX templates designed
✅ SortableJS drag-and-drop integration
✅ Pterodactyl API sync with rate limiting
## Tech Stack
- **Backend:** Node.js + Express
- **Database:** PostgreSQL
- **Frontend:** EJS templates + HTMX + SortableJS
- **Integration:** Pterodactyl API (rate-limited)
## Next Steps
1. Read full spec in task folder
2. Set up Express routes
3. Build database schema
4. Implement drag-and-drop UI
5. Test with dev servers first
## Full Spec Location
📁 `/docs/tasks/task-094-global-restart-scheduler/`
**Spec is deployment-ready** — just needs implementation time.

67
docs/tasks-active/task-098-discord-channel-automation.md Normal file
View File

@@ -0,0 +1,67 @@
---
task_number: 98
title: Discord Server Channel Automation
priority: 2
status: PLANNED
is_blocker: false
tags: [discord, automation, quality-of-life, holly]
estimated_hours: 6
---
# Task #98: Discord Server Channel Automation
**Status:** PLANNED (Scope expanded April 7, 2026)
**Priority:** P2 - MEDIUM (QoL for Holly)
**Category:** Discord Automation
## Overview
Bot command to auto-create Discord category + 4 channels per Minecraft server, plus role creation/deletion with reaction automation.
**Goal:** Reduce manual Discord setup work when new servers launch
## Original Scope
Bot command: `/create-server <server-name>`
Auto-creates:
1. Category: `🎮 [Server Name]`
2. Channels inside:
- `#server-chat` (text)
- `#server-voice` (voice)
- `#server-announcements` (text, locked)
- `#server-support` (text)
## Expanded Scope (April 7, 2026)
Added:
- Role creation (`@[Server Name] Player`)
- Role deletion (cleanup command)
- Reaction role automation (emoji → role assignment)
- Permission sync (roles auto-applied to category/channels)
## Tech Stack
- Discord.js v14
- Node.js bot
- Hosted on Command Center
## Next Steps
1. Review full scope expansion notes
2. Code the Discord bot commands
3. Test on dev Discord server
4. Deploy to production Discord
5. Document command usage for Holly
## Full Spec Location
📁 Task notes in SESSION-HANDOFF (April 7, 2026)
📁 Discord role message ready: `/docs/discord/discord-server-roles-message.md`
## Benefits for Holly
- One command vs 10+ manual steps
- Consistent channel structure
- Automatic permission setup
- Reaction roles for server access

86
docs/tasks-active/task-099-claude-projects-architecture.md Normal file
View File

@@ -0,0 +1,86 @@
---
task_number: 99
title: Claude Projects Setup (Dev/Ops/Marketing)
priority: 1
status: READY
is_blocker: false
tags: [workflow, documentation, organization]
estimated_hours: 3
---
# Task #99: Claude Projects Architecture
**Status:** READY (Full spec complete, browser-only work)
**Priority:** P1 - HIGH (Workflow Enhancement)
**Category:** Documentation & Workflow
## Overview
Create 3 separate Claude Projects with Master Documents in Project Knowledge to prevent context bleed and optimize token usage.
**The Problem:** "Context Bloat Wall" — Dev code mixed with marketing prompts, context windows filling with irrelevant data
**The Solution:** Separate Projects = Local Scope, Memory = Global Scope
## Three Projects
### 1. Firefrost Dev
**Purpose:** Coding, MVC, Arbiter, ModpackChecker
**Master Docs:**
- ModpackChecker-State.md
- Arbiter-Architecture.md
- Dev-Environment.md
- Trinity-Console.md
### 2. Firefrost Ops
**Purpose:** Operations, infrastructure, handoffs
**Master Docs:**
- Current-State.md
- Infrastructure-Manifest.md
- Active-Tasks.md
- Standards-Reference.md
### 3. Firefrost Marketing
**Purpose:** Brand, social media, FOMO campaigns
**Master Docs:**
- Brand-Guidelines.md
- FOMO-Campaign.md
- Social-Platforms.md
- Subscription-Tiers.md
## Micro-Session Workflow
1. Pick the right Project (Dev/Ops/Marketing)
2. Start NEW chat per task (don't extend forever)
3. Work the task (Master Docs auto-load)
4. When context bloats → summarize, save, start fresh
5. When complete → generate updated state summary
6. Sync Master Docs → update canonical version, re-upload
## Implementation Steps
1. Create 3 Projects in claude.ai (browser work)
2. Draft 12 Master Documents (4 per project)
3. Upload to Project Knowledge
4. Test micro-session workflow
5. Document in operations manual
## Time Estimate
**2-3 hours** (browser-only, no SSH needed)
## Full Spec Location
📁 `/docs/tasks/task-099-claude-projects-architecture.md`
## Benefits
- Prevents context bleed (Dev code out of Marketing)
- Optimizes token usage (smaller, focused contexts)
- Faster sessions (less irrelevant data loaded)
- Better organization for future Chroniclers
## Consultation
Based on Gemini AI consultation (April 7, 2026)
See: `/docs/consultations/2026-04-07-model-switching.md`