On Automatic
The Views

The lens, on real vaults.

Every screenshot below is the app reading an actual Campaign Vault: the public example vault from the spec repository, and a region exported by Hexes on Automatic. Nothing is mocked up.

The run view

Tonight's screen, dealt from the vault: previously-on from the session log, the region's travel rules, and per-terrain encounter tables with every monster linked. The in-world date sits in the toolbar with a one-click +1 day.

The run view for the Silverwick Expanse region: previously-on panel, travel rules table with speed, navigation, survival and forage columns, and encounter tables with linked monsters.
Run view · a region exported by Hexes on Automatic · day 23 of the campaign clock

The dashboard

The campaign at a glance: the kind census with stub counts, the worklist of what still needs an owner, vault health, regions and sessions — and the party's position, straight from the campaign note.

The dashboard for the Greenreach Vale example vault: entity census, worklist, health panel, regions and sessions.
Dashboard · the public example vault (30 notes, 4 of them pure GM material)

Notes with receipts

Every note renders with its provenance line — id, path, generator, spec version — reference chips, declared relationships, and the generated sections framed and attributed. Your own prose sits outside the fences, visibly yours.

An NPC note: hidden-from-players badge, provenance header, reference chips, declared relationships, GM prose and a framed generated-identity section, backlinks underneath.
An NPC note · “hidden from players” badge, generated section framed with its generator's name

The relationship map

Factions as rectangles, NPCs as stadiums, declared edges drawn deterministically — the same layout every time. GM secrets are dashed; directed kinds carry arrows. Click a node to open its note.

The relationship map of the example vault: faction rectangles and NPC nodes joined by labeled edges, secret edges dashed.
Relationship map · 17 declared edges, secrets dashed

The boards

The commission board lists every work order Hexes left for Dungeons, and every stub still waiting for one. The quest board tracks objectives with done and hidden marks, givers and targets.

The commission board: three open site commissions with the files that carry them, and four settlement stubs with no work order yet.
Commission board · three site work orders from Hexes, four settlement stubs waiting for Towns
The quest board: an active quest with objectives, one done, one hidden, and giver and target chips.
Quest board · objectives with done and hidden marks

The player view

One toggle re-renders the whole app through the spec's leak rules. Unrevealed notes vanish from lists and search, GM prose and secret edges disappear, the atlas goes dark past what the table has charted — and the GM-only views leave the nav entirely.

Player view of the example vault's atlas: the map dark with nothing charted yet, entity counts reduced to what has been revealed, GM views absent from the navigation.
Player view ON · the same vault, showing only what the table has learned

The same rules drive the player/ export: one button derives a standalone player vault, byte-identical to what the reference validator would produce, that you can sync or hand to the table.