docs: Gemini consultation — subscriber wiki tier system + living lore engine
This commit is contained in:
Claude
@@ -0,0 +1,111 @@
|
||||
# Gemini Consultation: Subscriber Wiki Tier System + Living Lore Engine
|
||||
|
||||
**Date:** April 15, 2026 — Soft Launch Day
|
||||
**From:** Michael (The Wizard) + Claude (Chronicler #92)
|
||||
**To:** Gemini (Architectural Partner)
|
||||
**Re:** Tier-gated subscriber wiki with automated living lore system
|
||||
|
||||
---
|
||||
|
||||
## Hey Gemini! 👋
|
||||
|
||||
Big day for us — Firefrost Gaming went live this morning. Real subscribers, real payments, real community. While we catch our breath, we're thinking about the next layer: a subscriber wiki that creates genuine FOMO and keeps people subscribed.
|
||||
|
||||
We have two interlocking ideas we want your wildest thinking on. Give us everything — practical, experimental, absurd. We'll filter. You generate.
|
||||
|
||||
---
|
||||
|
||||
## The Situation
|
||||
|
||||
**What exists:**
|
||||
- Wiki.js deployed at `subscribers.firefrostgaming.com` — running, but empty
|
||||
- 6 subscription tiers: Awakened ($1 lifetime), Elemental ($5/mo), Knight ($10/mo), Master ($15/mo), Legend ($20/mo), Sovereign ($50 lifetime)
|
||||
- Arbiter (Node.js/Express) handles Stripe webhooks, Discord OAuth, LuckPerms sync
|
||||
- 18 Minecraft servers across TX1 Dallas and NC1 Charlotte
|
||||
- Holly (The Catalyst) is our lead builder — she shapes the worlds
|
||||
- Michael (The Wizard) is the operator — he wants to chronicle what happens in those worlds
|
||||
- Meg (The Emissary) handles community and social
|
||||
|
||||
**The policy already written:**
|
||||
- Awakened+ = access to the wiki (everyone who ever paid us)
|
||||
- World backups accessible to Elemental+ (30-day retention, NextCloud storage)
|
||||
- "We Don't Kick People Out" — cancellation demotes to Awakened, never removes access
|
||||
|
||||
---
|
||||
|
||||
## Idea 1: Tier-Gated Wiki Content
|
||||
|
||||
We want the wiki to have content locked behind tiers — not just "you need to be Elemental to see this page" but genuinely compelling content that makes Legend subscribers feel like insiders and makes Awakened subscribers want to upgrade.
|
||||
|
||||
**Our current thinking by tier:**
|
||||
|
||||
- **Awakened ($1)** — Rules, FAQ, how to connect, path philosophy, server list basics
|
||||
- **Elemental ($5/mo)** — World backup downloads, modpack links, new player server guides
|
||||
- **Knight ($10/mo)** — Server lore documents, State of the Realm reports, early patch notes
|
||||
- **Master ($15/mo)** — Behind the scenes content, mod selection process, voting on future servers
|
||||
- **Legend ($20/mo)** — Direct feedback pipeline, name in server launch credits, early access to new servers, sneak peeks at what's being designed
|
||||
- **Sovereign ($50)** — Everything + Sovereign Wall (permanent name in the realm) + custom in-game title + a personal welcome from The Trinity
|
||||
|
||||
**The FOMO mechanic:** Lower tiers can see that higher-tier content exists but can't read it. Redacted previews. "Something happened in Otherworld on April 15... [unlock at Knight tier]"
|
||||
|
||||
---
|
||||
|
||||
## Idea 2: The Living Lore Engine
|
||||
|
||||
This is the one we're most excited about.
|
||||
|
||||
Each Minecraft server has a story. Otherworld is a D&D-inspired fantasy realm. Cottage Witch is cozy witchcraft. DeceasedCraft is zombie apocalypse survival. These aren't just modpacks — they're worlds with histories.
|
||||
|
||||
**The vision:**
|
||||
- The system detects in-game milestone events (first player join, first boss kill, first death, first claim, server hitting 100 total players, etc.) via RCON or log parsing
|
||||
- Each event triggers a Claude API call that drafts a lore fragment in Michael's voice — 1-3 sentences, written like a chronicle entry
|
||||
- Michael gets a Discord DM: "New lore fragment generated — approve / edit / reject"
|
||||
- One tap to publish to the server's Chronicle page in the wiki
|
||||
- The Chronicle grows automatically over time as players create history
|
||||
|
||||
**The FOMO layer:**
|
||||
- Sovereigns see the Chronicle in real time
|
||||
- Legends see it with a 24-hour delay
|
||||
- Masters see weekly summaries
|
||||
- Knights see monthly recaps
|
||||
- Elemental sees "The chronicle grows..." with entry count but no content
|
||||
- Awakened sees that a Chronicle exists but can't read it
|
||||
|
||||
**Example lore fragment:**
|
||||
> *"On the fifteenth day of the fourth month, a wanderer became the first soul to set foot in the Otherworld. The ancient stones remembered. The realm had begun."*
|
||||
|
||||
Michael wants maximum automation — he's the editor, not the writer. The system drafts, he approves with one tap, it publishes.
|
||||
|
||||
---
|
||||
|
||||
## What We Need From You
|
||||
|
||||
**Question 1: Give us your 20 wildest ideas** for what could live in a tier-gated subscriber wiki for a Minecraft community. Don't filter. We want the absurd, the experimental, the "nobody has ever done this" ideas alongside the practical ones. We'll decide what fits.
|
||||
|
||||
**Question 2: For the Living Lore Engine** — what events should we track beyond the obvious ones? What milestone moments in a Minecraft server's life are worth chronicling? Think about what would actually feel meaningful to a player who reads "their" server's chronicle.
|
||||
|
||||
**Question 3: Architecture check on the Lore Engine** — our plan is RCON polling + log parsing → Arbiter event detection → Claude API draft → Discord DM approval → Wiki.js publish via API. Any holes in that pipeline? Better approaches for the event detection layer?
|
||||
|
||||
**Question 4: The FOMO mechanics** — is redacted content the right approach, or is there a more elegant way to show lower-tier subscribers what they're missing without being annoying? What have you seen work well for subscription content tiers?
|
||||
|
||||
**Question 5: One more wild one from you** — if you were building the most compelling subscriber experience for a Minecraft community and had no constraints, what's the single idea you'd push hardest for that we haven't mentioned?
|
||||
|
||||
---
|
||||
|
||||
## Context That Might Help
|
||||
|
||||
- Michael has accessibility limitations (hand surgery) — any approval workflow needs to be one-tap from mobile
|
||||
- Meg handles the community voice — she'd write the marketing copy around whatever we build
|
||||
- Holly builds the worlds — she's not the lore writer, Michael is
|
||||
- We have Claude API access for the lore generation
|
||||
- Arbiter already handles Discord webhooks, DMs, and role management
|
||||
- Wiki.js has a REST API for content management
|
||||
- We're on launch day — this is post-launch planning, not blocking anything
|
||||
- The Trinity (Michael, Meg, Holly) are the only ones who know the full vision — subscribers experience it from the outside
|
||||
|
||||
---
|
||||
|
||||
Thanks Gemini — this one's for the long game. We're building something that keeps people subscribed for years, not months. Give us your best. 🔥💜❄️
|
||||
|
||||
— Michael (The Wizard) + Claude (Chronicler #92)
|
||||
*Fire + Arcane + Frost = Forever*
|
||||
Reference in New Issue
Block a user