Game System Design Platform (GSDP)

Living GDD Keep your game’s design connected as it changes.

A system-first workspace for designing games as entities + relationships
so your intent stays navigable through prototypes, iteration, and shifting scope.

  • ✓

    Structured entities for characters, quests, items, mechanics, and more.

  • ✓

    System-first navigation (IDE-style) to scan and connect systems quickly.

  • ✓

    SystemLink™ makes dependencies explicit, not buried in prose.

Not a “design bible.” Not a rules engine. A navigable map of design intent and what connects — your shipped build stays runtime truth; this helps the team reason together when scope shifts.

Join Early Access See it in action →

Indie-friendly pricing. Subscribers on this list get paid-launch pricing and terms before they’re on the public site — so you see the full picture before checkout, not after.

GDDs don’t fail because you’re lazy. They fail because games change.

Prototypes evolve, systems interlock, and intent shifts. Over time, a doc either becomes a second job… or it quietly drifts away from what’s actually in the game.

Living GDD doesn’t remove the discipline — shipping still wins if nobody touches the map. It tries to lower the cost of small updates: entities are quick to open, links and reverse references surface “what touches what,” and status plus overview make “still says in progress” harder to ignore than a forgotten doc page.

✕

“Design bibles” become dense, stale, and ignored.

✕

Two realities form: the doc reality and the game reality.

✕

Relationships stay implicit — so changes create invisible ripple effects.

✕

Under time pressure, “keeping it updated” loses to shipping.

This is not a design bible.

Living GDD is meant to support discovery — not pretend you can lock a game down on paper. It’s structured enough to reduce cognitive load, but lightweight enough to evolve with you.

✓

Not a promise of certainty.
Games are discovered through prototyping and playtests. Living GDD evolves alongside that discovery.

✓

Not a replacement for conversation.
It supports playtests and team context by keeping intent and dependencies visible.

✓

Not exhaustive by default.
Capture the minimum structure early. Add detail only when it pays off.

✓

Not a single static “truth.”
It’s a map you update when you choose to — structured so stale status, open tasks, and explicit links can surface inconsistency faster than hunting prose.

How this differs from Notion, Docs, or Obsidian

Those tools are excellent for writing and freeform notes. Living GDD isn’t trying to replace them — it focuses on something they don’t model well: game systems as connected, evolving entities.

Where general-purpose notes struggle (for games)

  • Relationships and dependencies are implied, not explicit.
  • Design intent gets buried under pages and content lists.
  • When something changes, ripple effects are easy to miss.
  • Structure decays unless someone constantly curates it.

What a Game System Design Platform adds

  • Characters, quests, items, mechanics, and locations are first-class entities.
  • SystemLink™ keeps relationships visible and navigable.
  • Fast scanning built for connected systems, not long pages.
  • A living design map that evolves alongside prototypes and playtests.

A Game System Design Platform keeps your game’s knowledge connected.

Living GDD evolves the traditional GDD into a structured workspace built for iteration. Capture intent, connect systems, and keep design context navigable — without pretending a document can “lock down” a game before it exists.

Living GDD · Sample Project

Entities

  • Characters
  • Quests
  • Items
  • Locations
  • Factions
  • Mechanics

Eira, Flamebound

Main protagonist · Fire-tuned mage

Role

Main character · Narrative anchor

Tagline

“If the world breaks its rules, why can’t I?”

Alignment

Good

What exists today (and what I’m exploring next)

Living GDD evolves alongside real workflows: prototypes first, then structure where it earns its keep. Here’s what’s available now — plus areas I’m actively exploring based on feedback.

Available Now

  • • Structured entities
  • • Categories
  • • Three-panel navigation
  • • SystemLink™ (typed design links)
  • • Status tracking & entity tasks
  • • Project overview (counts & drill-down)
  • • Entity graph view (explore links)
  • • Per-entity file attachments (categorized)

In Progress / Likely Next

  • • Version history & change timelines
  • • Expanded status workflows
  • • Example / template projects
  • • Search & filters
  • • Richer overview metrics

Potential Directions

  • • Dialogue tree views
  • • Quest graph views
  • • Crafting system views
  • • Location map views
  • • Deeper graph layouts & filtering
  • • Studio collaboration ideas

Built for indie teams and solo devs

Designed for long dev cycles, part-time schedules, and small teams wearing too many hats. Keep your design knowledge navigable and connected — without turning documentation into a second job.

Minimum necessary

Capture the intent and dependencies that matter. Avoid exhaustive lists that rot the moment you iterate.

Update-friendly

No magic sync — you still choose to update. Status in lists, project overview, and per-entity tasks make “what’s out of date?” easier to see and chip away at than rewriting long pages. Typed links remind you what else might need a pass when one system moves.

Grows with you

Start simple. Add structure as prototypes become real systems. No “GDD rewrite” phase required.

Build with iteration in mind.

Join early access to help shape Living GDD — devlogs, system-design notes, and product updates. Before paid plans go live on the marketing site, we’ll email this list with the full breakdown: what each tier includes, limits (seats, storage, projects), renewal rules, and how to subscribe — so nothing is a surprise at checkout.

No spam — devlogs, product updates, and launch/pricing news when it matters.