Guild Competition — Multi-Guild Loyalty Platform
Vision for multiple guilds (independent loyalty programs) competing against each other on the same platform.
Core Concepts
Guild
An Organization that runs its own loyalty program — its own tiers, classes, points, members, and brand. Examples:
- Dungeon Books Guild — indie fantasy bookstore
- Victory Points Guild — board game café
- The Coffee Crypt Guild — themed coffee shop
Each guild is a self-contained loyalty ecosystem. Members, tiers, XP, and classes are scoped to the guild.
Shop
A guild’s own physical location(s). A guild can have multiple shops (e.g., Dungeon Books Downtown, Dungeon Books Eastside).
Kiosk Host
A partner location that hosts another guild’s kiosk but doesn’t run its own loyalty program. The kiosk belongs to the guild, not the physical location.
Example: A coffee shop near Dungeon Books agrees to host a Dungeon Books kiosk. Dungeon Books members can tap their card there to check in. The coffee shop doesn’t have its own guild — it’s just a quest location in the Dungeon Books network.
The Distinction
| Full Guild | Kiosk Host | |
|---|---|---|
| Runs own loyalty program | Yes | No |
| Has own tiers/classes | Yes | No |
| Has own members | Yes | No |
| Hosts kiosks | Yes (own kiosks) | Yes (another guild’s kiosks) |
| Organization record | Yes | No (just a shop under another guild) |
How It Maps to the Data Model
The existing hierarchy already supports this:
Organization (Guild)
└── Shop (own location OR partner kiosk host)
└── Kiosk (device, belongs to the guild via shop)
└── Check-ins (scoped to shop + org)
A kiosk host is just a Shop under another guild’s Organization. The kiosk device at that location has an API key that resolves to the guild’s org, not the host’s.
Competition Model (Future)
Guild vs Guild
- Leaderboards — total member XP, check-in volume, active members
- Territory — guilds claim neighborhoods based on member density / check-in activity
- Seasonal events — cross-guild competitions (“Which guild can log the most check-ins in October?“)
- Alliances — guilds can form alliances, shared quest boards, cross-guild XP bonuses
Member Identity
A person could be a member of multiple guilds (shops they frequent). Their identity is per-guild — Level 5 Mage at Dungeon Books, Level 2 Rogue at Victory Points.
Cross-Guild Quests
“Visit 3 allied guild locations this month” — enabled by the quest hub / kiosk host model.
What Exists Today
- Organization → Shop → Kiosk hierarchy ✅
- Kiosks collection with per-device API keys ✅
- Multi-tenant plugin scoping all data to Organization ✅
- Check-in XP scoped to org ✅
What’s Needed
- Guild onboarding flow (self-serve org + shop + kiosk setup)
- Guild profile / public page
- Cross-guild member identity (one person, multiple guild memberships)
- Leaderboard queries (aggregations across orgs)
- Competition events system
Related
- guild-quest-hub-network — partner kiosk host model
- membership-platform — full system architecture
- guild-kiosk-build — kiosk implementation
- guild-seasons — seasonal event framework