Home Roadmap
Where it stands
The project keeps its plan in writing and audits it against the source, so this page can say what is actually true rather than what sounds good. Four milestones, two reached. Dates are given where the record has them and withheld where it does not.
The milestones
The full DM loop playable through the engine: rules engine, dice, personas, memory and compaction, seven systems built and golden-tested.
The complete loop in the desktop client with real inference: onboarding, the pixel-art play screen, streaming speech, the Chronicle, rewind, the notebook. The room engine and its Scene Builder arrived after this milestone closed, and the front of house was redrawn as the Cartographer's Desk.
The systems work. What is missing is production: the four unpainted DMs, a soundscape for every room, interface and dice sounds, and speech input. None of it is engine work, and it does not compete for the same hours.
Signed and notarised installers on three platforms, the hosted tier, and licensing-clean distribution. The sidecar binary and export presets exist; signing needs the owner's certificates rather than code.
The current work
The live plan runs in a deliberate order. These are the phases between here and a beta, with the reason each sits where it does.
The engine reads a rulebook you own and proposes a system; the remaining work is the player-facing half. A review screen for what the book proposed, the book's own creatures at the table, and the long tail of equipment and advancement. A book that declares no skills cannot roll what its own DM asks for, and that hole is being closed for every ingested book at once.
The room engine is built and measured, and the four oldest rooms are still in their first-generation shape. Converting them to the layered room format is the only thing blocking the beta, and it competes for no hours with anything else.
Output is answered: the DM speaks, locally, with a cloned voice that keeps up (real-time factor measured at 0.59 to 0.68, every chunk faster than playback). What is left is input, and there is no speech-to-text layer at all yet. Local recognition, campaign names as hotwords, the transcript landing in your chat box for review first.
Nothing above matters if the install does not work. Signed installers, the upgrade path for existing players, and the two items that need the owner's own accounts. Mostly not code.
Every claim in the project's records that says "needs data" gets its run: measurements scheduled as work, not vibes. The register of what is wrong or unproven is a living document with a rule attached: an item may only be called closed when something was observed.
Characters who grow the way their book says they grow. Most of it has landed already; what remains is teaching ingestion to read a book's advancement rules, and a character creator that follows them. Death is still unripe.
Over the horizon
These are real ideas in the project's notes with real design behind them. None has a date, because none has earned one yet.
Play the world a book describes, or play the book itself, its rules enforced. The idea is Joe's, from a note that asked why bringing a book should stop at its rules when it could bring its world too. It waits on the ingestion crew's survey.
A world a book describes rather than one it gives rules for. The furthest-out idea on the list, and it is on the list because the difference between a ruleset and a setting is exactly the line the engine already knows how to draw.
The Scene Builder already assembles rooms from pieces. The long ambition is a studio on top of the game: environments, avatars, DMs, game modes and animations, made in the game and brought to your own table.
How the plan stays honest
The project keeps one register of everything known to be wrong or unproven, and it is the only document allowed to be a to-do list. Two of its rules are worth stealing for any project.
An item may only be called closed when something was observed: a passing test, a live run, a measured number. A fix that looks obviously right is not closure, and the register says which level of confidence each closure has.
When one class of bug keeps coming back through new doors, the fix is a gate, not another patch: a named specimen corpus and an invariant that runs on every playthrough, so the class stays dead. The register records when a finding is withdrawn, too. Three were, in one audit day.
LOOM