99b2e3ea37
WHAT WAS DONE: - Created BLOCKERS.md at repo root (4 soft launch critical tasks) - Created BACKLOG.md at repo root (organized future work parking lot) - Archived old tasks.md to docs/archive/tasks-historical-march-30-2026.md - Archived 50 Gitea issues to docs/archive/gitea-issues-archive-2026-04-01.md - Replaced tasks.md with migration notice and redirects - Closed all 50 Gitea issues with migration message WHY: Old system problems: - 97 task entries with 8 duplicates (tasks 52, 65, 69, 71, 83, 85, 87, 88) - Heavyweight maintenance burden - Gitea Issues + Kanban unused and abandoned - Not accessible to non-technical team members (Meg, Holly) - Desynchronized duplicates (Tier S section vs sequential list) New system benefits: - Clear focus: 4 blockers vs 89 backlog items - Simple markdown (easy to update) - Preserved all historical context in archives - Planning Trinity Console v2 Task Module for non-technical interface SOFT LAUNCH REALITY CHECK: Based on Michael's input, soft launch is blocked by: 1. Ghost homepage (2-3h) - content ready 2. Legal pages (1-2h) - Terms/Privacy 3. Unsubscribe flow (2-3h) - cancellation UI 4. End-to-end test (2-3h) - workflow verification Total: 8-11 hours of focused work Target: April 15, 2026 (14 days) Social campaign starts: April 2, 2026 (TOMORROW) GITEA CLEANUP: - Closed 50 open issues (all had been abandoned) - Each issue received migration notice comment - All preserved in gitea-issues-archive-2026-04-01.md - Issues feature will be disabled (Kanban decommissioned) NEXT STEPS: - Update DOCUMENT-INDEX.md to reference new files - Plan Trinity Console v2 Task Module (Gemini consultation) - Start on actual soft launch blockers FILES ADDED: - BLOCKERS.md (74 lines) - BACKLOG.md (227 lines) - docs/archive/gitea-issues-archive-2026-04-01.md (50 issues archived) - docs/archive/tasks-historical-march-30-2026.md (3151 lines preserved) FILES MODIFIED: - docs/core/tasks.md (replaced with redirect notice) IMPACT: - Clean foundation for tracking work - Historical context fully preserved - Ready for non-technical task interface (Trinity Console v2) - Clear path to April 15 soft launch Signed-off-by: Claude (Chronicler #54) <claude@firefrostgaming.com>
4.4 KiB
🚨 SOFT LAUNCH BLOCKERS
Target Launch Date: April 15, 2026 (14 days from now)
Social Media Campaign Starts: April 2, 2026 (TOMORROW)
Last Updated: April 1, 2026 by Chronicler #54
🎯 DEFINITION OF SOFT LAUNCH
Goal: Successfully onboard and manage 10 paying subscribers
Success Criteria:
- Website live with clear value proposition
- Legal protection (Terms of Service, Privacy Policy)
- Payment processing functional (Paymenter + Stripe)
- Subscribe → Discord role → Server access workflow verified
- Unsubscribe flow tested and working
- Can handle payment failures gracefully
✅ MUST COMPLETE BEFORE LAUNCH
1. Ghost Homepage - Fire/Frost Content
Time: 2-3 hours
Status: ⏳ NOT STARTED
Assigned: Unassigned
Blocks: Marketing, social media links, subscriber funnel
What's needed:
- Implement homepage content from
docs/planning/ideas/features/ghost-homepage-content.md - Hero section with Fire/Frost path selection
- Origin story section
- Value propositions
- Clear CTAs to subscription page
Resources:
- Content READY at:
docs/planning/ideas/features/ghost-homepage-content.md - Mobile fix already deployed (Task #88 complete)
Done when: firefrostgaming.com shows Fire/Frost branding and converts visitors to subscribers
2. Ghost Legal Pages - Terms & Privacy
Time: 1-2 hours
Status: ⏳ NOT STARTED
Assigned: Unassigned
Blocks: Legal liability, accepting payments
What's needed:
- Terms of Service page
- Subscription terms
- Cancellation policy
- Refund policy (digital goods = no refunds)
- Age requirements (13+)
- Account termination clause
- Privacy Policy page
- Data collection (email, Discord ID, payment info)
- Data usage (account management, communication)
- Third-party services (Stripe, Discord, Paymenter)
- GDPR compliance
- Data deletion requests
Resources:
- Can use Gemini/ChatGPT for boilerplate, customize for Firefrost
- Reference: Stripe's legal requirements, Minecraft server ToS examples
Done when: Both pages published, linked in footer, legally protected
3. Unsubscribe Flow - Cancellation UI
Time: 2-3 hours
Status: ⏳ NOT STARTED
Assigned: Unassigned
Blocks: Ethical payment processing, user autonomy
What's needed:
- Paymenter: Add "Cancel Subscription" button to user dashboard
- Trinity Console: Verify grace period dashboard shows cancellations
- Email: Cancellation confirmation message
- Discord: Role removal on cancellation
- Whitelist: Server access revocation
Notes:
- Trinity Console Grace Period module already built
- Database schema supports cancellation flow
- Need to connect Paymenter UI to existing backend
Done when: User can cancel subscription, enters grace period, gets downgraded to Awakened after 3 days
4. End-to-End Workflow Test
Time: 2-3 hours
Status: ⏳ NOT STARTED
Assigned: Unassigned
Blocks: Confidence in system reliability
What's needed:
-
Test full happy path:
- New user visits firefrostgaming.com
- Chooses Fire or Frost path
- Selects tier (Elemental $5)
- Completes Paymenter checkout
- Links Discord account
- Receives Discord role
- Gets whitelisted on game servers
- Logs in and plays
- Cancels subscription
- Enters grace period
- Gets downgraded to Awakened after 3 days
-
Test failure scenarios:
- Payment failure → grace period
- Chargeback → immediate ban
- Double subscription during grace period
Done when: All workflows verified, edge cases handled, team confident in system
📊 SUMMARY
Total Blockers: 4 tasks
Estimated Time: 8-11 hours of focused work
Days Remaining: 14 days
Urgency: MEDIUM (doable but need to start NOW)
Next Session Priorities:
- Ghost homepage (content ready, just needs implementation)
- Legal pages (can draft with AI assistance)
- Unsubscribe UI (backend ready, needs frontend)
- Testing (validate everything works)
🎯 POST-LAUNCH PRIORITIES (Not Blockers)
These improve operations but don't prevent soft launch:
- Paymenter → Pterodactyl auto-provisioning (manual is fine for 10 users)
- Holly's Builder rank setup (can do post-launch)
- Rank system deployment (Phase 1 can wait)
- Additional automation and polish
Fire + Frost + Foundation = Where Love Builds Legacy 🔥❄️
This file is the single source of truth for soft launch blockers. Update it frequently.