System design mapping for games

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.

Games aren’t hard to imagine. They’re hard to keep navigable while they change.

Mechanics, quests, items, and characters don’t sit in neat chapters — they interlock. When that structure only lives in scattered notes and flat pages, iteration means re-deriving “what connects to what” instead of moving the design forward.

Living GDD targets the typed, linked layer: entities and explicit relationships so dependency walks stay short and small edits don’t require rewriting whole sections. Shipping still wins if nobody opens the workspace — but when they do, status, overview, and reverse references make drift easier to spot than hunting prose alone.

✕

Dependencies stay implicit — ripple effects hide until playtests or crunch.

✕

Content lists don’t show how systems actually touch each other.

✕

One change forces a scavenger hunt through unrelated docs for what might be stale.

✕

Under time pressure, curating long documents loses to shipping.

Long-form writing stays in Notion, Docs, or Obsidian. This is the systems layer.

Living GDD doesn’t compete with narrative specs, mood boards, or high-level GDD prose — it gives you typed entities and navigable links for the parts of the design that behave like a graph (who, what, where, which mechanic) so they stay scannable as scope shifts.

✓

Complements prose, doesn’t replace it.
Keep essays, pitches, and art direction where you already work; use this for connected game elements.

✓

Built for discovery, not lock-in.
Games emerge through prototyping and playtests — the map evolves alongside that, without pretending paper is law.

✓

Minimum structure first.
Capture intent and dependencies that matter; add detail when it earns its keep.

✓

Honest about drift.
You still choose when to update — status, tasks, and explicit links make inconsistency easier to see than in prose alone.

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 this systems layer 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 navigable map of your game’s systems — not another static document.

Model characters, quests, items, mechanics, and locations as first-class entities. SystemLink™ keeps relationships visible both ways so intent stays traceable as you iterate — alongside whatever you use for long-form writing, not instead of it.

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 follows how teams actually work: prototypes first, then structured mapping 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 big-bang documentation rewrite when a mechanic lands.

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.