Canonical scene state
Every tactical scene is modeled as one authoritative document containing rooms, openings, objects, actors, round state, and optional narration fields. The renderer follows that state rather than inventing its own.
Every tactical scene is modeled as one authoritative document containing rooms, openings, objects, actors, round state, and optional narration fields. The renderer follows that state rather than inventing its own.
The legacy architecture notes emphasized durable records and versioned updates. That matters because campaigns need memory, and memory needs a source of truth that sits outside the public website.
Artificial intelligence is treated as an instrument, not an oracle: useful for continuity, adjudication, and structured narration when it operates inside explicit boundaries.
Why It Matters
The DM World Engine exists so maps, inventories, Character Sheets, campaign state, and tactical scenes can agree with each other over time. The public site does not ship that runtime, but it can explain the design goal clearly: a campaign where systems remain visible and fiction is earned through interaction with them.
Related reading: Presence-Aware AI at the Table