Create individual task files for Decap CMS task management
- Created /tasks/ folder with individual task markdown files - Each task has frontmatter (number, title, priority, status, owner) - Blockers marked with blocker: true field - Sample tasks created: #26, #51, #87, #93, #94, #98, #99 Benefits: - Click individual tasks in Decap CMS instead of editing giant BACKLOG.md - Filter by priority (BLOCKER, P1, P2, P3, etc.) - Sort by status, number, blocker flag - Mobile-friendly (each task = separate entry) - BLOCKERS.md and BACKLOG.md remain as reference docs Task structure: --- number: 26 title: Task Name priority: P1 status: In Progress blocker: false owner: Michael full_spec: docs/tasks/full-spec-location/ --- Task content here...
This commit is contained in:
26
tasks/task-026-modpack-checker.md
Normal file
26
tasks/task-026-modpack-checker.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
number: 26
|
||||
title: Modpack Version Checker
|
||||
priority: P1
|
||||
status: In Progress
|
||||
blocker: false
|
||||
owner: Michael
|
||||
full_spec: docs/tasks/modpack-version-checker/
|
||||
---
|
||||
|
||||
# Task #26: Modpack Version Checker
|
||||
|
||||
**Commercial product for BuiltByBit** — passive income potential
|
||||
|
||||
## Status
|
||||
Phase 5 code written but not deployed. Blueprint developer mode corrupted after database wipe.
|
||||
|
||||
## Next Steps
|
||||
1. Blueprint reinstallation on Dev Panel
|
||||
2. Deploy Phase 5 (UpdateBadge.tsx, cron command, status route)
|
||||
3. Testing and publication
|
||||
|
||||
## Links
|
||||
- Full spec: `docs/tasks/modpack-version-checker/`
|
||||
- Phases 1-4: Complete
|
||||
- Phase 5: Code backed up to `/root/modpackchecker_backup`
|
||||
28
tasks/task-051-ignis-protocol.md
Normal file
28
tasks/task-051-ignis-protocol.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
number: 51
|
||||
title: Ignis Protocol (18+ Space)
|
||||
priority: BLOCKED
|
||||
status: Awaiting Legal Consultation
|
||||
blocker: false
|
||||
owner: Michael
|
||||
blocked_by: LegalCORPS Minnesota consultation
|
||||
---
|
||||
|
||||
# Task #51: Ignis Protocol
|
||||
|
||||
**18+ Discord space** — Age verification compliance
|
||||
|
||||
## Overview
|
||||
Create 18+ verified space in Discord for adult subscribers.
|
||||
|
||||
## Blocker
|
||||
Awaiting pro-bono legal consultation from LegalCORPS Minnesota on age verification compliance requirements.
|
||||
|
||||
## Next Steps
|
||||
1. Complete legal consultation
|
||||
2. Determine compliant age verification method
|
||||
3. Implement verification system
|
||||
4. Create 18+ channels/roles
|
||||
|
||||
## Status
|
||||
On hold until legal guidance received.
|
||||
27
tasks/task-087-arbiter-lifecycle.md
Normal file
27
tasks/task-087-arbiter-lifecycle.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
number: 87
|
||||
title: Arbiter Lifecycle Handlers
|
||||
priority: BLOCKER
|
||||
status: Complete
|
||||
blocker: true
|
||||
owner: Chronicler #62
|
||||
completed_date: 2026-04-06
|
||||
full_spec: docs/tasks/arbiter-2-1-cancellation-flow/
|
||||
---
|
||||
|
||||
# Task #87: Arbiter Lifecycle Handlers
|
||||
|
||||
**✅ COMPLETE** — Soft launch blocker resolved April 6, 2026
|
||||
|
||||
## What Was Implemented
|
||||
- Discord role sync on new subscriptions
|
||||
- Grace period handling (3 days) on cancellation
|
||||
- Automatic downgrade to Awakened when grace expires (hourly cron)
|
||||
- Chargeback = immediate ban + role removal
|
||||
|
||||
## Philosophy
|
||||
"We Don't Kick People Out" — expired grace → permanent Awakened tier
|
||||
|
||||
## Links
|
||||
- Implementation: Arbiter 3.5.0
|
||||
- Spec: `docs/tasks/arbiter-2-1-cancellation-flow/`
|
||||
31
tasks/task-093-trinity-codex.md
Normal file
31
tasks/task-093-trinity-codex.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
number: 93
|
||||
title: Trinity Codex (Dify/Qdrant RAG)
|
||||
priority: P1
|
||||
status: Architecture Complete
|
||||
blocker: false
|
||||
owner: Unassigned
|
||||
full_spec: docs/tasks/task-093-trinity-codex/
|
||||
---
|
||||
|
||||
# Task #93: Trinity Codex
|
||||
|
||||
**RAG system for Trinity** — knowledge base with AI-powered search
|
||||
|
||||
## Overview
|
||||
Self-hosted AI knowledge base using:
|
||||
- **Dify**: RAG orchestration platform
|
||||
- **Qdrant**: Vector database for embeddings
|
||||
- **Source**: firefrost-operations-manual docs
|
||||
|
||||
## Status
|
||||
Architecture complete. Ready for implementation.
|
||||
|
||||
## Next Steps
|
||||
1. Deploy Dify on TX1
|
||||
2. Deploy Qdrant on TX1
|
||||
3. Configure document ingestion
|
||||
4. Test query accuracy
|
||||
|
||||
## Links
|
||||
- Full spec: `docs/tasks/task-093-trinity-codex/`
|
||||
34
tasks/task-094-restart-scheduler.md
Normal file
34
tasks/task-094-restart-scheduler.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
number: 94
|
||||
title: Global Restart Scheduler
|
||||
priority: P1
|
||||
status: Spec Complete
|
||||
blocker: false
|
||||
owner: Unassigned
|
||||
full_spec: docs/tasks/task-094-global-restart-scheduler/
|
||||
---
|
||||
|
||||
# Task #94: Global Restart Scheduler
|
||||
|
||||
**680-line spec complete** — reduces manual server work
|
||||
|
||||
## Overview
|
||||
Centralized scheduler for all Minecraft server restarts across NC1 and TX1.
|
||||
|
||||
Features:
|
||||
- Web UI for Trinity to manage restart schedules
|
||||
- Per-server scheduling with drag-and-drop
|
||||
- Pterodactyl API integration with rate limiting
|
||||
- SortableJS for visual reordering
|
||||
|
||||
## Status
|
||||
Complete specification exists (680 lines including database schema, Express routes, EJS/HTMX templates).
|
||||
|
||||
## Next Steps
|
||||
1. Review spec at `docs/tasks/task-094-global-restart-scheduler/`
|
||||
2. Implement backend (Express + PostgreSQL)
|
||||
3. Implement frontend (EJS + HTMX + SortableJS)
|
||||
4. Test with Pterodactyl API
|
||||
|
||||
## Links
|
||||
- Full spec: `docs/tasks/task-094-global-restart-scheduler/`
|
||||
32
tasks/task-098-discord-automation.md
Normal file
32
tasks/task-098-discord-automation.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
number: 98
|
||||
title: Discord Server Channel Automation
|
||||
priority: P2
|
||||
status: Scope Expanded
|
||||
blocker: false
|
||||
owner: Unassigned
|
||||
full_spec: docs/tasks/task-098-discord-channel-automation.md
|
||||
---
|
||||
|
||||
# Task #98: Discord Server Channel Automation
|
||||
|
||||
**QoL for Holly** — Bot command to auto-create server channels
|
||||
|
||||
## Overview
|
||||
Discord bot command to automatically create:
|
||||
- Server category
|
||||
- 4 standard channels (general, builds, support, screenshots)
|
||||
- Role creation/deletion
|
||||
- Reaction-based role automation
|
||||
|
||||
## Status
|
||||
Scope expanded April 7, 2026 by Chronicler #66 (The Indexer)
|
||||
|
||||
## Next Steps
|
||||
1. Implement bot command
|
||||
2. Test channel creation
|
||||
3. Add role automation
|
||||
4. Deploy to Discord bot
|
||||
|
||||
## Links
|
||||
- Full spec: `docs/tasks/task-098-discord-channel-automation.md`
|
||||
32
tasks/task-099-claude-projects.md
Normal file
32
tasks/task-099-claude-projects.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
number: 99
|
||||
title: Claude Projects Setup
|
||||
priority: P1
|
||||
status: Ready to Implement
|
||||
blocker: false
|
||||
owner: Unassigned
|
||||
full_spec: docs/tasks/task-099-claude-projects-architecture.md
|
||||
---
|
||||
|
||||
# Task #99: Claude Projects Setup
|
||||
|
||||
**Browser-only work** — Create 3 separate Claude Projects with Master Documents
|
||||
|
||||
## Overview
|
||||
Separate Claude Projects to prevent context bloat:
|
||||
- **Firefrost Dev** — Coding, MVC, Arbiter
|
||||
- **Firefrost Ops** — Operations, handoffs
|
||||
- **Firefrost Marketing** — Brand, social, FOMO
|
||||
|
||||
## Implementation Steps
|
||||
1. Create 3 Projects in claude.ai
|
||||
2. Draft 12 Master Documents
|
||||
3. Upload to Project Knowledge
|
||||
4. Test micro-session workflow
|
||||
|
||||
## Time Estimate
|
||||
2-3 hours (browser work, no SSH needed)
|
||||
|
||||
## Links
|
||||
- Full spec: `docs/tasks/task-099-claude-projects-architecture.md`
|
||||
- Gemini consultation: `docs/consultations/2026-04-07-model-switching.md`
|
||||
Reference in New Issue
Block a user