The current Battlemat project makes the most sense as a campaign workspace rather than as a standalone tactical page.
That shift is important because the table needs more than a map. It needs a place where scene state, Character Sheets, continuity, and campaign artifacts can remain coherent together.
Why a campaign workspace?
The old prototype proved that a tactical surface could be compelling on its own. What it did not solve was the larger question of continuity.
Campaign play needs a container that can hold more than movement and turns. It needs to keep track of who is in the world, what their artifacts look like, what has changed, and what should survive after the scene ends.
That is why the current public model is organized as four parts:
- Campaign
- Battlemat
- Character Sheets
- Campaign Management
Campaign: the container
Campaign is the saved playable container.
It gathers the material that gives play continuity:
- tactical state
- characters
- portraits
- notes
- continuity
- backup and export artifacts
This is the part that makes the workspace feel like a real campaign rather than a collection of detached tools. The campaign is where the world holds together.
Battlemat: the tactical surface
Battlemat is the tactical surface.
It shows committed state: where actors are, what the scene looks like, whose turn or status matters right now, and what movement or combat consequences have become table-facing truth.
That role is deliberately narrow.
The Battlemat is not the whole app and it is not the rules oracle. It is the tactical surface players can trust while the wider workspace carries the heavier burden of continuity.
Character Sheets: living artifacts
Character Sheets are the character-facing artifact layer.
Full sheets live with the campaign. Portraits matter. Notes matter. Preparation details matter. What the player sees on the sheet should remain attached to the ongoing life of play instead of drifting into a folder of disposable side documents.
This is why Character Sheets belong inside the workspace model rather than floating beside it. They are not just records. They are living campaign artifacts.
Campaign Management: keeping the artifact portable
Campaign Management is the maintenance, export, and recovery area.
Backup, export, and restoration belong here. This is also where the idea of the Backup Passport Package fits conceptually: as a portable campaign artifact that supports handoff and deliberate restoration.
That wording matters.
This is not about quick-load habits, save-slot thinking, or turning the workspace into an account portal. Restoration should be understood as deliberate restoration: a careful act of re-establishing campaign material when needed.
Why the website stays separate
The public website has a different job.
It explains the project, publishes dev-log articles, provides player-safe lore, and offers how-to-play guidance. The live runtime belongs in the separate campaign workspace, not inside the public hub.
That separation keeps the website readable and keeps the workspace free to do the heavier work of play.