diff --git a/docs/core/project-scope.md b/docs/core/project-scope.md index 4c77c2c..5abed29 100644 --- a/docs/core/project-scope.md +++ b/docs/core/project-scope.md @@ -263,16 +263,32 @@ Claude β†’ Reads results directly from Gitea API **Identical mechanical perks, different community identity:** -**πŸ”₯ Path of Fire:** -- Discord: Ignis channels (18+ only) -- Focus: Competitive gameplay, PvP, challenges +**πŸ”₯ Path of Fire (All-Ages, 13+):** +- Discord: Fire Path exclusive channels +- Focus: Magic mods, community-focused, creative gameplay +- Inspired by: Mystical Agriculture, Ars Nouveau, Botania - Led by: Gingerfury (The Emissary) -**❄️ Path of Frost:** -- Discord: Frost channels (all ages welcome) -- Focus: Collaborative builds, exploration, creativity +**❄️ Path of Frost (All-Ages, 13+):** +- Discord: Frost Path exclusive channels +- Focus: Tech mods, automation, precision engineering +- Inspired by: Create, Mekanism, industrial automation - Led by: Frostystyle (The Wizard) +**⚑ Sovereign Tier ($499 lifetime):** +- Gets access to BOTH Fire AND Frost paths +- All exclusive channels from both paths +- Founder-only channels (The Nexus) + +**πŸ”₯ Ignis Protocol (18+ Mature Space - PLANNED):** +- Completely separate from Fire/Frost subscription choice +- Purely age-based access (NOT tier-based) +- Any subscriber 18+ can access after age verification +- Website section + Discord channels +- Mature conversation, adult-only events +- **Status:** Not yet implemented, awaiting legal consultation +- **See:** docs/planning/ignis-protocol-specification.md + --- ## πŸ” AUTHENTICATION STRATEGY diff --git a/docs/core/tasks.md b/docs/core/tasks.md index 4324ffb..2277253 100644 --- a/docs/core/tasks.md +++ b/docs/core/tasks.md @@ -1208,3 +1208,55 @@ Deploy fresh Wiki.js instance for Aurelian PokΓ©dex project on Ghost VPS. **Claudius Stage 3 (The Chronicle Keeper):** Active, Git repos clean --- + +### 49. Ignis Protocol Implementation Planning +**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 + +--- diff --git a/docs/planning/ignis-protocol-specification.md b/docs/planning/ignis-protocol-specification.md new file mode 100644 index 0000000..67a96d5 --- /dev/null +++ b/docs/planning/ignis-protocol-specification.md @@ -0,0 +1,438 @@ +# Ignis Protocol: 18+ Mature Space Specification + +**Status:** πŸ”„ PLANNING - NOT YET IMPLEMENTED +**Created:** March 19, 2026 +**Purpose:** Legal consultation preparation for LegalCORPS Minnesota +**Owner:** Michael "Frostystyle" Krause (The Wizard) + +--- + +## Executive Summary + +**Ignis** is the codename for Firefrost Gaming's planned 18+ mature community space. It is **completely separate** from the Fire vs Frost path subscription system and is **purely age-based**, not tier-based. + +**Critical Legal Question:** +*What is the legally sound method of age verification for an online gaming community that wants to provide a mature discussion space for adults while maintaining COPPA compliance for our 13+ all-ages servers?* + +--- + +## What Ignis IS + +**Purpose:** +- Mature conversation space for adult community members (18+) +- Unfiltered discussion about gaming, industry, and off-topic subjects +- Adult-only events and potentially adult-oriented Minecraft servers +- Safe space for adults to socialize without language/content restrictions + +**Implementation Platforms:** +- Website section at `firefrostgaming.com/ignis/*` (Ghost CMS) +- Discord channels (18+ verified role required) + +**Content Types:** +- Text-based mature conversation (NOT pornographic/explicit sexual content) +- Industry hot takes and unfiltered opinions +- Mature humor and memes +- Adult-oriented social events +- Possibly 18+ Minecraft servers with mature themes/builds + +**Access Model:** +- **Purely age-based** - Any subscriber 18+ can access Ignis +- Independent of subscription tier (Awakened $1 or Sovereign $499 both eligible) +- Age verification required before first access +- Permanent ban for minors discovered in Ignis space + +--- + +## What Ignis IS NOT + +**NOT:** +- ❌ A subscription tier (Fire/Frost are tiers, Ignis is age-gated space) +- ❌ Pornographic or sexually explicit content platform +- ❌ Dating/hookup service +- ❌ Gambling or adult services marketplace +- ❌ Replacement for all-ages community (Fire/Frost paths remain primary) + +**Ignis is comparable to:** +- Reddit's 18+ subreddits (mature discussion, not adult content) +- Discord's NSFW text channels (age-gated, not pornographic) +- Gaming forums with "mature discussion" sections + +--- + +## Relationship to Fire/Frost Paths + +**Fire and Frost Paths (All-Ages, 13+):** +- Subscription-based community identity choice +- Fire Path = Magic mods, community-focused, creative (Meg's domain) +- Frost Path = Tech mods, systems-focused, precision (Michael's domain) +- Tiers: Awakened ($1) β†’ Elemental ($5) β†’ Knight/Master/Legend β†’ Sovereign ($499) +- Sovereign tier gets BOTH Fire AND Frost access + +**Ignis (Age-Verified, 18+):** +- Age-based access control (NOT subscription tier) +- Completely independent system from Fire/Frost choice +- A user can be: "Fire Elemental + Ignis" or "Frost Legend + Ignis" or "Sovereign + Ignis" +- Ignis access does NOT affect Fire/Frost perks, Discord roles, or Minecraft permissions + +**Example Scenarios:** +- **Scenario A:** Player pays $1 (Awakened), is 18+, verifies age β†’ Gets server access + Ignis +- **Scenario B:** Player pays $499 (Sovereign), is 17 β†’ Gets BOTH Fire/Frost + all perks, NO Ignis +- **Scenario C:** Player pays $5 (Fire Elemental), is 22, verifies age β†’ Fire channels + Ignis channels + +--- + +## Current Implementation Status + +### What EXISTS Today (March 19, 2026) +- βœ… Fire vs Frost path structure (documented, implemented in Discord) +- βœ… Subscription tier system (Awakened through Sovereign defined) +- βœ… Ghost CMS website (firefrostgaming.com) with basic content +- βœ… Discord server with Fire/Frost role structure +- βœ… Minecraft servers (13+ EULA compliant) + +### What DOES NOT EXIST (Ignis Components) +- ❌ Age verification system (method not chosen) +- ❌ Ignis website section (/ignis/* route) +- ❌ Ignis Discord channels (no 18+ verified role yet) +- ❌ Legal documentation (Terms of Service, Privacy Policy for age verification) +- ❌ Age verification policy document +- ❌ Ignis content moderation guidelines +- ❌ Any 18+ Minecraft servers + +**Status:** Pure planning phase. No technical implementation has begun. + +--- + +## Legal Consultation Goals + +### Primary Questions for Attorney + +**1. Age Verification Method:** +- What is the legally defensible age verification method for our use case? +- Is payment verification (credit card = 18+) sufficient as a layer? +- Do we need government ID upload? +- Should we use a third-party age verification service (Yoti, Stripe Identity)? +- What documentation do we need to maintain for good-faith compliance? + +**2. Terms of Service & Liability:** +- What language must be in our Terms of Service to limit liability? +- How do we clearly communicate the 18+ requirement? +- What happens if a minor bypasses verification? +- What is our legal obligation if we discover a minor in Ignis? +- Can we implement a "three strikes" ban policy or must it be immediate? + +**3. Privacy Policy & COPPA Compliance:** +- How do we handle data collection for age verification while remaining COPPA compliant? +- What data can we collect from 13-17 year olds on Fire/Frost paths? +- What data can we collect from 18+ users for Ignis verification? +- How long must we retain age verification records? +- What are our obligations under state-specific data privacy laws? + +**4. Discord Integration Concerns:** +- Discord is implementing their own age verification system soon +- How does our verification interact with Discord's system? +- If Discord verifies a user as 18+, can we rely on that? +- If we verify a user as 18+ but Discord doesn't, what happens? +- Should we wait for Discord's system before implementing Ignis? + +**5. Multi-State Compliance:** +- Recent state laws (Utah, Louisiana, Arkansas, Virginia, Mississippi) require age verification for "harmful content" +- Is mature gaming discussion considered "harmful content" under these laws? +- Do we need geo-blocking for specific states? +- What is the threshold between "mature discussion" and "adult content"? + +--- + +## Proposed Architecture (Pending Legal Guidance) + +### Website Implementation (Ghost CMS) + +**Public Frost/Fire Paths:** +- Routes: `firefrostgaming.com/*` (public, all-ages) +- No login required for reading +- No data collection from visitors +- COPPA-safe (read-only content) + +**Ignis Route:** +- Route: `firefrostgaming.com/ignis/*` +- Login required (Ghost membership system) +- Age verification gate before first access +- Clear 18+ warning and confirmation + +**Proposed Age Gate Flow:** +1. User attempts to access `/ignis/*` route +2. Redirected to age verification page +3. User confirms: "I am 18 years or older" (checkbox) +4. User enters birth date (must calculate to 18+) +5. [AGE VERIFICATION METHOD - TBD WITH ATTORNEY] +6. Manual admin approval (first-time access only) +7. Upon approval: Ignis access granted, Discord role synced +8. Subsequent visits: automatic (verified user) + +### Discord Implementation + +**All-Ages Channels:** +- Frost Path channels (13+) +- Fire Path channels (13+) +- Public/Crossroads channels (13+) + +**Ignis Channels (18+ Verified):** +- Role: `@Ignis Verified` (only granted after age verification) +- Channels locked to this role +- Separate Discord category: "πŸ”₯ IGNIS (18+)" + +**Proposed Channel Structure:** +- `#ignis-lounge` (general mature discussion) +- `#ignis-industry` (gaming industry hot takes) +- `#ignis-offtopic` (non-gaming mature chat) +- `#ignis-events` (adult-only event planning) + +### Moderation Strategy + +**Ignis Moderation Principles:** +1. Adult space does NOT mean "anything goes" +2. Still respectful, no harassment or illegal content +3. Mature language/humor allowed, not pornographic content +4. Active moderation by Meg (The Emissary) and trusted moderators + +**Zero Tolerance:** +- Minors discovered in Ignis space β†’ Immediate permanent ban +- Sharing pornographic/illegal content β†’ Immediate permanent ban +- Harassment or doxxing β†’ Immediate permanent ban + +**Three-Strike System (For Other Violations):** +- Warning #1: Explanation of violation +- Warning #2: 7-day Ignis suspension +- Warning #3: Permanent Ignis ban (keeps Fire/Frost access if 13+) + +--- + +## Data Collection & Privacy + +### Data We Currently Collect (All Users) + +**For All Subscribers (Awakened $1+):** +- Email address (Stripe payment, Discord account linking) +- Minecraft username (for server whitelist) +- Payment information (processed by Stripe, not stored by us) +- Discord User ID (for role syncing) + +**For Fire/Frost Path Members (Elemental $5+):** +- Path choice (Fire or Frost) +- Subscription tier (Elemental, Knight, Master, Legend, Sovereign) + +### Additional Data for Ignis (Proposed - Pending Legal Review) + +**What We MIGHT Need to Collect:** +- Birth date (age verification) +- [VERIFICATION METHOD DATA - TBD WITH ATTORNEY] + - Credit card verification timestamp? + - Government ID scan (if required)? + - Third-party verification token (if using service)? + +**What We WILL NOT Collect:** +- Social Security Numbers +- Full government ID images (unless legally required) +- Biometric data +- Financial data beyond payment processing (handled by Stripe) + +**Retention Policy (Draft - Pending Legal Review):** +- Age verification records: [DURATION TBD - attorney guidance needed] +- User activity logs: 90 days maximum +- Deleted account data: Purged within 30 days +- Banned user records: Retained indefinitely (prevent re-registration) + +--- + +## Risk Assessment + +### Risk 1: Minor Bypasses Age Verification +**Likelihood:** Low-Medium (depends on verification method strength) +**Impact:** High (legal liability, community trust, platform risk) +**Mitigation:** +- Multi-layer verification (not just checkbox) +- Manual admin approval for first access +- Active community reporting +- Regular audits of Ignis member list +- Clear Terms of Service with immediate ban policy + +**Response Plan:** +1. Immediate suspension of account upon discovery +2. Review how bypass occurred +3. Strengthen verification layer that failed +4. Document incident with timestamps +5. Consult attorney if minor was active for extended period +6. Notify parents if possible/appropriate + +--- + +### Risk 2: Discord Age Verification Conflict +**Likelihood:** High (Discord implementing own system in 2026) +**Impact:** Medium (technical complexity, user confusion) +**Mitigation:** +- Monitor Discord's age verification rollout announcements +- Plan integration with Discord's system when available +- Consider delaying Ignis launch until Discord system is live +- Maintain our own verification as backup/supplement + +**Response Plan:** +1. Evaluate Discord's verification method when announced +2. Determine if we can rely on Discord's verification +3. Update our system to complement (not duplicate) Discord's +4. Communicate changes clearly to community + +--- + +### Risk 3: State Law Compliance (Utah, Louisiana, etc.) +**Likelihood:** Low-Medium (depends on definition of "harmful content") +**Impact:** High (potential geo-blocking, legal challenges) +**Mitigation:** +- Define Ignis as "mature discussion" not "adult content" +- Document good-faith age verification effort +- Consult attorney familiar with state-specific laws +- Implement geo-blocking for specific states if necessary + +**Response Plan:** +1. Monitor state law developments +2. Consult attorney if challenged +3. Adjust content policy if needed +4. Implement geo-blocking as last resort + +--- + +### Risk 4: Content Moderation Overload +**Likelihood:** Medium (as Ignis community grows) +**Impact:** Medium (Meg's time, content quality, liability) +**Mitigation:** +- Clear community guidelines +- Automated content flags (keyword filters) +- Trusted community moderators (18+ verified, vetted) +- Regular moderator training + +**Response Plan:** +1. Add volunteer moderators from trusted Ignis members +2. Implement automated filtering tools +3. Consider paid moderation if community scales beyond volunteer capacity + +--- + +## Success Metrics + +### Phase 1: Launch Readiness +- βœ… Legal review completed (Terms, Privacy, Age Verification Policy) +- βœ… Age verification method implemented and tested +- βœ… Ignis website section live with access gate +- βœ… Discord channels created with role restrictions +- βœ… Moderation guidelines published +- βœ… First 5 Ignis members successfully verified and active + +### Phase 2: Community Growth +- 10+ Ignis members active and engaged +- Zero minors discovered in Ignis space +- Moderation time <5 hours/week for Meg +- Positive feedback from adult community +- No legal complaints or challenges + +### Phase 3: Maturity +- 25+ Ignis members +- Self-sustaining discussion (not admin-driven) +- Community moderation via trusted volunteers +- Integration with Discord's age verification (when available) + +--- + +## Timeline (DRAFT - Pending Legal Consultation) + +### Pre-Launch (Legal Prep) +- **Week 0:** LegalCORPS consultation (attorney guidance) +- **Week 1-2:** Draft Terms of Service, Privacy Policy, Age Verification Policy +- **Week 3:** Legal review of documentation (follow-up with attorney if needed) + +### Phase 1: Implementation (IF Attorney Approves) +- **Week 4-5:** Build age verification system (website + Discord integration) +- **Week 6:** Create Ignis Discord channels and role structure +- **Week 7:** Beta testing with 3-5 trusted adult community members +- **Week 8:** Soft launch to existing community, first approvals + +### Phase 2: Growth +- **Month 3-6:** Gradual community growth, moderation refinement +- **Month 6:** Review metrics, adjust policies, plan Phase 3 + +--- + +## Open Questions for Attorney + +1. **Age Verification Method:** What is legally sufficient for our use case? +2. **Credit Card as Proxy:** Is Stripe payment ($1+ subscription) enough as ONE layer of verification? +3. **Manual Approval:** Can manual admin review serve as second verification layer? +4. **ID Upload:** Do we need government ID upload, or is that overkill for "mature discussion"? +5. **Third-Party Service:** Should we use Yoti, Stripe Identity, or similar? +6. **Discord Integration:** Can we rely on Discord's upcoming age verification? +7. **Data Retention:** How long must we keep age verification records? +8. **COPPA Compliance:** How do we ensure Fire/Frost (13+) compliance while collecting data for Ignis (18+)? +9. **State Law Threshold:** Is "mature discussion" considered "harmful content" under Utah/Louisiana laws? +10. **Liability Limitation:** What Terms of Service language protects us if a minor bypasses verification? +11. **Ban Policy:** Must we immediately ban discovered minors, or can we have a warning system? +12. **Parental Notification:** Are we obligated to notify parents if we discover a minor in Ignis? + +--- + +## Next Steps + +1. **LegalCORPS Consultation** - Present this document to volunteer attorney +2. **Legal Documentation** - Draft Terms, Privacy, Age Verification Policy based on attorney guidance +3. **Implementation Plan** - Build technical architecture only AFTER legal approval +4. **Community Communication** - Announce Ignis plans to existing community (AFTER legal review) +5. **Phased Rollout** - Beta test with trusted members before public launch + +--- + +## Appendix: Comparison to Similar Platforms + +### How Other Gaming Communities Handle 18+ Spaces + +**Discord:** +- NSFW channels require "18+" checkbox (self-attestation only) +- Implementing stricter age verification in 2026 +- Terms of Service prohibit minors in adult spaces + +**Reddit:** +- 18+ subreddits require account age verification +- Self-attestation + birth date entry +- IP-based age verification in some regions + +**Twitch:** +- Mature content streams require viewer age confirmation +- Relies on account birth date +- No government ID requirement + +**Steam:** +- Age gate for mature games (birth date entry) +- Parental controls for family sharing +- No ID upload required + +**Firefrost's Approach:** +- More rigorous than Discord/Reddit (manual approval layer) +- Less invasive than government ID requirement +- Good-faith, multi-layer verification +- Clear documentation and policies + +--- + +## Revision History + +| Version | Date | Author | Changes | +|---------|------|--------|---------| +| **1.0** | 2026-03-19 | The Wizard (Chronicler #33) | Initial specification for LegalCORPS consultation. Documented current state, legal questions, proposed architecture pending attorney guidance. | + +--- + +**END OF DOCUMENT** + +**Status:** πŸ”„ PLANNING PHASE +**Next Action:** LegalCORPS legal consultation +**Owner:** Michael "Frostystyle" Krause + +--- + +πŸ”₯❄️ **Firefrost Gaming: Where Community Meets Security** πŸ”₯❄️