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

Task #51: Ignis Protocol Implementation Planning #204

New Issue
Closed
opened 2026-03-21 02:34:08 -05:00 by mkrause612 · 1 comment
mkrause612 commented 2026-03-21 02:34:08 -05:00
Owner
Copy Link

Task #51: Ignis Protocol Implementation Planning

Time Estimate: 4-6 hours (brainstorming + architecture)

Documentation: docs/tasks/ (see operations manual)

Time: 4-6 hours (brainstorming + architecture)
Status: 🔄 BLOCKED — Awaiting LegalCORPS attorney consultation
Priority: HIGH - Legal compliance required before ANY implementation
Documentation: docs/planning/ignis-protocol-specification.md

Comprehensive planning session for Ignis (18+ mature space) implementation. Original planning predates current Git documentation system, so this task rebuilds the implementation roadmap with current infrastructure knowledge.

Current State:

  • Ignis specification document created (March 19, 2026)
  • Legal consultation scheduled with LegalCORPS Minnesota (pro-bono)
  • Age verification method: TBD (need attorney guidance)
  • Implementation: NOT started (waiting for legal approval)

Goals:

  1. Define legally sound age verification workflow
  2. Plan website architecture (Ghost CMS /ignis/* route)
  3. Design Discord integration (18+ verified role)
  4. Create content moderation guidelines
  5. Build technical implementation roadmap
  6. Document data collection/privacy requirements

Key Questions to Answer:

  • What age verification method is legally defensible?
  • How does Ignis integrate with existing Fire/Frost subscription system?
  • What happens when Discord implements their own age verification?
  • What content is allowed in Ignis (mature discussion vs adult content)?
  • How do we maintain COPPA compliance for 13+ servers while collecting age data for Ignis?

Prerequisites:

  • ✅ Ignis specification document created
  • ⏳ LegalCORPS attorney consultation completed
  • ⏳ Terms of Service legal review
  • ⏳ Privacy Policy legal review
  • ⏳ Age Verification Policy drafted

Post-Legal Consultation:

  1. Update specification with attorney guidance
  2. Create implementation task directory (docs/tasks/ignis-implementation/)
  3. Build technical architecture plan
  4. Design age verification flow (website + Discord)
  5. Draft Terms of Service language
  6. Draft Privacy Policy updates
  7. Create moderation guidelines
  8. Plan phased rollout strategy

CRITICAL: Do NOT begin any technical implementation until legal consultation complete and attorney approves approach.

See: docs/planning/ignis-protocol-specification.md for complete details and legal questions

Source: docs/core/tasks.md (Task #51)

### Task #51: Ignis Protocol Implementation Planning **Time Estimate:** 4-6 hours (brainstorming + architecture) **Documentation:** `docs/tasks/` (see operations manual) --- **Time:** 4-6 hours (brainstorming + architecture) **Status:** 🔄 BLOCKED — Awaiting LegalCORPS attorney consultation **Priority:** HIGH - Legal compliance required before ANY implementation **Documentation:** `docs/planning/ignis-protocol-specification.md` Comprehensive planning session for Ignis (18+ mature space) implementation. Original planning predates current Git documentation system, so this task rebuilds the implementation roadmap with current infrastructure knowledge. **Current State:** - Ignis specification document created (March 19, 2026) - Legal consultation scheduled with LegalCORPS Minnesota (pro-bono) - Age verification method: TBD (need attorney guidance) - Implementation: NOT started (waiting for legal approval) **Goals:** 1. Define legally sound age verification workflow 2. Plan website architecture (Ghost CMS `/ignis/*` route) 3. Design Discord integration (18+ verified role) 4. Create content moderation guidelines 5. Build technical implementation roadmap 6. Document data collection/privacy requirements **Key Questions to Answer:** - What age verification method is legally defensible? - How does Ignis integrate with existing Fire/Frost subscription system? - What happens when Discord implements their own age verification? - What content is allowed in Ignis (mature discussion vs adult content)? - How do we maintain COPPA compliance for 13+ servers while collecting age data for Ignis? **Prerequisites:** - ✅ Ignis specification document created - ⏳ LegalCORPS attorney consultation completed - ⏳ Terms of Service legal review - ⏳ Privacy Policy legal review - ⏳ Age Verification Policy drafted **Post-Legal Consultation:** 1. Update specification with attorney guidance 2. Create implementation task directory (`docs/tasks/ignis-implementation/`) 3. Build technical architecture plan 4. Design age verification flow (website + Discord) 5. Draft Terms of Service language 6. Draft Privacy Policy updates 7. Create moderation guidelines 8. Plan phased rollout strategy **CRITICAL:** Do NOT begin any technical implementation until legal consultation complete and attorney approves approach. **See:** `docs/planning/ignis-protocol-specification.md` for complete details and legal questions --- --- **Source:** `docs/core/tasks.md` (Task #51)
mkrause612 commented 2026-04-01 18:16:14 -05:00
Author
Owner
Copy Link

This issue is being closed as part of the task system migration on April 1, 2026.

Why: The Gitea Issues + Kanban approach proved too heavyweight for daily operations and lacked accessibility for non-technical team members (Meg, Holly).

New System:

  • BLOCKERS.md - Critical soft launch tasks
  • BACKLOG.md - Future work organized by theme
  • Trinity Console v2 Task Module (planned) - Web-based task management

Archive: All issues preserved in docs/archive/gitea-issues-archive-2026-04-01.md

— Chronicler #54

This issue is being closed as part of the task system migration on April 1, 2026. **Why:** The Gitea Issues + Kanban approach proved too heavyweight for daily operations and lacked accessibility for non-technical team members (Meg, Holly). **New System:** - `BLOCKERS.md` - Critical soft launch tasks - `BACKLOG.md` - Future work organized by theme - Trinity Console v2 Task Module (planned) - Web-based task management **Archive:** All issues preserved in `docs/archive/gitea-issues-archive-2026-04-01.md` — Chronicler #54
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/automation
n8n workflows and automation
 area/billing
Paymenter billing system
 area/development-tools
Internal tools for workflow automation and team productivity
 area/email
Mailcow email system
 area/game-servers
Minecraft or other game servers
 area/networking
Network infrastructure and configuration
 area/operations
General operations and documentation
 area/panel
Pterodactyl Panel
 area/website
Ghost CMS website
 area/wings
Pterodactyl Wings
 duplicate
This issue is a duplicate of another issue
 for/holly
Assigned to Holly (unicorn20089)
 for/meg
Assigned to Meg (GingerFury)
 for/michael
Assigned to Michael (Frostystyle)
 good-first-issue
Good for newcomers
 help-wanted
Extra attention needed
 needs-board-sync
New issue needs to be added to project board
 operations
priority
critical
Emergency — immediate attention required
priority
high
Important — address soon
priority
low
Nice to have, not urgent
priority
medium
Normal priority
status
backlog
Not yet started, in backlog
status
blocked
Cannot proceed, blocked by dependency
status
done
Completed and closed
status
in-progress
Currently being worked on
status
review
Work complete, awaiting review
status
to-do
Ready to start, in queue
type
bug
Something isn't working
type
docs
Documentation improvements or additions
type
feature
New feature or enhancement request
type
infrastructure
Infrastructure, deployment, or DevOps work
type
refactor
Code refactoring or technical debt
type
task
General task or work item
wont-do
This will not be worked on
No Label area/automation area/website for/michael
priority
critical
status
blocked
type
infrastructure
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Gingerfury Unicorn20089 mkrause612
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: firefrost-gaming/firefrost-operations-manual#204
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?