Project Overview

Canonical orientation page for the current system model.

Read this first

1. System architecture
2. Domain language
3. Event-driven system

If you are changing X, read Y

• Replay/snapshots/recovery behavior: Event replay
• Game-system extension mechanics: Game systems
• Authorization semantics: Campaign Authorization Model
• Identity and auth boundaries: Identity and OAuth

What it is

Fracturing.Space models a tabletop RPG campaign as a deterministic, event-sourced state machine. Every change is an ordered event, enabling full replay, inspection, and branching from any point in history.

Why it exists

Long-running campaigns suffer from fragmented records and single-GM continuity. A deterministic, authoritative core enables reproducible outcomes, reliable history, and programmatic or AI-driven tooling on top.

What it supports today

• Campaign, session, participant, and character management
• Deterministic, server-side resolution of mechanics
• Event journal with replayable state
• gRPC APIs for AI orchestration
• Duality Dice as the initial rules system

What it does not include (yet)

• A full end-user UI or VTT
• Integrated chat/voice/media
• Hosted multi-tenant deployment
• Turnkey AI narration

Non-goals

• Emulating human improvisation
• Encoding subjective narrative quality into core rules
• Shipping proprietary game content

Status

Early and experimental. Interfaces may change as additional systems and deployment models evolve.