TaleGate Club

Inspiration

Long-distance friendships drift. Group chats go quiet. Plans to "catch up" never happen. We wanted to build something that gives friends a reason to reconnect throughout the week. Not a video call, not a social feed, but a shared ritual: reading the same story together, each of you living inside it as a character.

We drew inspiration from three places: the intimacy of a book club (a reason to gather regularly around something meaningful), the character embodiment of D&D (everyone has skin in the game), and the serialized anticipation of episodic TV (you always want to know what happens next). TaleGate Club is what happens when you blend all three.

What it does

TaleGate Club lets 2-4 friends form a "guild" and embark on a month-long collaborative story together. Here's how it works:

• Guild setup: One person creates a guild and invites up to 3 friends via link.
• Onboarding: Each player enters their favorite books, authors, or genres. We use these preferences to seed a story tailored to the group's collective taste.
• Character creation: Each player is assigned a character.
• Nightly chapters: Every evening at 6pm, a new chapter drops. Everyone reads the same story.
• Per-character decisions: Each chapter ends with a central choice for your character that'll be woven into a future chapter.
• Story convergence: Characters may start in separate situations but gradually meet, with their choices creating real consequences for each other: betrayal, alliance, or sacrifice.
• Season wrap: After ~30 chapters, the story ends with an epilogue, credits listing who played which character, and their playstyles.

How we built it

The story is guided by a structured knowledge graph that maintains continuity (tracking characters, relationships, locations, and unresolved threads) so that we never forget important story details.

TaleGate Club is built as a mobile-first web app with a lightweight iOS shell for device demo.

• Frontend: Next.js with a clean reading-focused UI; dark/light mode; mobile-first.
• Backend: Node/Express API with Postgres for persistent story state.
• AI layer: LLM-powered chapter generation using structured system prompts and a per-campaign "story bible" (JSON knowledge graph) to maintain long-term continuity.
• Decision system: Per-character choices stored with timestamps; a background worker auto-resolves expired decision windows.
• Kindle sync: Chapters delivered via Send-to-Kindle personal document email.
• Audio: TTS-powered narration with a single voice narrator and an in-app sleep timer.
• Story archetypes: 10 hand-crafted story skeletons (premise, tone, key beats) that guide the AI — so every campaign feels curated, not like AI slop.

Challenges we ran into

• Multi-character narrative coherence: Maintaining a consistent world state across 4 independent character arcs over 30 chapters was our hardest problem. We solved it with a structured story bible that is updated after every chapter — characters, relationships, locations, open threads — fed as context into every generation call.
• Balancing player agency with story structure: Letting players make real choices while keeping the story coherent and satisfying required careful prompt engineering. We constrain choices to 2–3 pre-authored options per character per chapter, which also keeps content within our PG-13 safety guidelines.
• Async multiplayer pacing: Four people in different time zones reading at different speeds is hard to coordinate. We solved this with a fixed daily drop window, a 24-hour decision deadline, and auto-decision logic that keeps the story moving without punishing the group for one person's absence.
• Kindle interactivity limits: Kindle is read-only; you can't do real-time branching on-device. Our solution cleanly separates reading (Kindle) from deciding (app), which actually reinforced the ritual: read at night, choose during the day.

What we learned

• Shared rituals are more powerful than social features. The 10pm chapter drop creates more engagement than any notification or leaderboard could.
• Constraining AI output (via archetypes, choices, knowledge graphs) produces better stories than unconstrained freeform generation.
• The emotional hook of TaleGate Club isn't the AI — it's your friends. The AI is just the medium.

What's next

Built With

• next.js
• node.js
• openai
• postgresql
• prisma
• swift
• typescript