2a4558deec
WHAT WAS DONE: Added critical tax compliance question to Ignis Protocol legal consultation document. WHY: Gemini identified state tax nexus as major blind spot for RV operations. Running subscription business while traveling across state lines triggers economic nexus laws for sales tax and complex income tax situations. WHAT WAS ADDED: New question #6 in Legal Consultation Goals section covering: - Economic nexus obligations for sales tax - Income tax compliance across state borders - State registration requirements - Documentation needs (work location vs subscriber location) - Automated tax compliance tools (Stripe Tax/TaxJar) - Simplified tax regimes for nomadic businesses - Timeline pressure (RV travel Sept 2027) FILE DETAILS: - Location: docs/planning/ignis-protocol-specification.md - Section: Legal Consultation Goals - Added: 8 sub-questions under question #6 CONTEXT: Based on Gemini's architectural review of Trinity Console expansion. This blind spot could cause serious legal/financial issues when founders begin RV travel in September 2027. Signed-off-by: Claude (Chronicler #54) <claude@firefrostgaming.com>
19 KiB
19 KiB
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"?
6. State Tax Nexus & RV Operations (CRITICAL):
- Operating a subscription business from an RV traveling across state lines
- What are our economic nexus obligations for sales tax collection?
- How do we handle income tax compliance when business operations cross state borders?
- Do we need to register with each state we operate from temporarily?
- What documentation is required to track where work is performed vs where subscribers reside?
- Should we integrate automated tax compliance (Stripe Tax/TaxJar) or manual tracking?
- Are there simplified tax regimes for nomadic digital businesses?
- RV travel timeline: September 2027 (need solution in place before then)
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:
- User attempts to access
/ignis/*route - Redirected to age verification page
- User confirms: "I am 18 years or older" (checkbox)
- User enters birth date (must calculate to 18+)
- [AGE VERIFICATION METHOD - TBD WITH ATTORNEY]
- Manual admin approval (first-time access only)
- Upon approval: Ignis access granted, Discord role synced
- 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:
- Adult space does NOT mean "anything goes"
- Still respectful, no harassment or illegal content
- Mature language/humor allowed, not pornographic content
- 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:
- Immediate suspension of account upon discovery
- Review how bypass occurred
- Strengthen verification layer that failed
- Document incident with timestamps
- Consult attorney if minor was active for extended period
- 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:
- Evaluate Discord's verification method when announced
- Determine if we can rely on Discord's verification
- Update our system to complement (not duplicate) Discord's
- 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:
- Monitor state law developments
- Consult attorney if challenged
- Adjust content policy if needed
- 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:
- Add volunteer moderators from trusted Ignis members
- Implement automated filtering tools
- 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
Ignis Protocol (18+ Space) Questions
- Age Verification Method: What is legally sufficient for our use case?
- Credit Card as Proxy: Is Stripe payment ($1+ subscription) enough as ONE layer of verification?
- Manual Approval: Can manual admin review serve as second verification layer?
- ID Upload: Do we need government ID upload, or is that overkill for "mature discussion"?
- Third-Party Service: Should we use Yoti, Stripe Identity, or similar?
- Discord Integration: Can we rely on Discord's upcoming age verification?
- Data Retention: How long must we keep age verification records?
- COPPA Compliance: How do we ensure Fire/Frost (13+) compliance while collecting data for Ignis (18+)?
- State Law Threshold: Is "mature discussion" considered "harmful content" under Utah/Louisiana laws?
- Liability Limitation: What Terms of Service language protects us if a minor bypasses verification?
- Ban Policy: Must we immediately ban discovered minors, or can we have a warning system?
- Parental Notification: Are we obligated to notify parents if we discover a minor in Ignis?
Commercial Software Products (NEW - Added April 1, 2026)
Context: Firefrost Gaming is developing commercial Blueprint extensions for Pterodactyl Panel to be sold on the BuiltByBit marketplace as passive income products. First product: Modpack Version Checker ($15).
- Software Licensing: What license should we use for commercial Blueprint extensions? (GPL, MIT, proprietary?)
- Intellectual Property Protection: How do we protect our code from being resold or redistributed without permission?
- License Enforcement: What mechanisms can we legally include to prevent unauthorized distribution?
- Terms of Sale: What must be included in the BuiltByBit product listing Terms of Sale?
- Support Obligations: What are our legal obligations for customer support after sale?
- Warranty Disclaimers: What liability disclaimers are necessary for "as-is" software?
- Update Policy: Can we legally abandon updates, or do we have ongoing obligations?
- Code Obfuscation: Is it legal to obfuscate PHP code to prevent easy copying?
- DMCA Takedowns: If someone pirates our extension, what's the process for DMCA takedown on BuiltByBit?
- Refund Policy: What refund obligations do we have for digital products?
- End User License Agreement (EULA): Do we need a separate EULA, or is BuiltByBit's TOS sufficient?
- Derivative Works: If buyers modify our code for their own use, what are our rights?
- Business Entity Protection: Should Firefrost Gaming LLC own the IP, or should it be under a separate entity?
Next Steps
- LegalCORPS Consultation - Present this document to volunteer attorney
- Legal Documentation - Draft Terms, Privacy, Age Verification Policy based on attorney guidance
- Implementation Plan - Build technical architecture only AFTER legal approval
- Community Communication - Announce Ignis plans to existing community (AFTER legal review)
- 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. |
| 1.1 | 2026-04-01 | Chronicler #52 | Added 13 intellectual property protection questions for commercial software products (Blueprint extensions for BuiltByBit marketplace). Covers licensing, IP protection, DMCA, warranties, and business entity structure. |
END OF DOCUMENT
Status: 🔄 PLANNING PHASE
Next Action: LegalCORPS legal consultation
Owner: Michael "Frostystyle" Krause
🔥❄️ Firefrost Gaming: Where Community Meets Security 🔥❄️