1. Development build

    Session night — Jot and the GM bar

    Capture a note from anywhere, and keep the tools you reach for mid-session in one bar.

    • Jot: press Ctrl + J anywhere to capture a note. Tag records with @name, or drop a record onto the note. During a live session it files into the session for wrap-up; while you prepare, it lands in the plan.
    • GM bar: docks along the bottom during a session, with Jot, quick NPC, names by ancestry, DCs by level, clocks, rules lookup and Start encounter.
    • Design work has begun on Facts, the foundation for tracking who knows what. See the Roadmap.
  2. Development build

    Campaign memory, themes and a better builder

    Canonex now remembers what changed, looks the way you want, and builds sessions and encounters by drag and drop.

    • Campaign memory on Home: what changed since last session, open and quiet threads, returning faces, and forgotten prep.
    • Last time we saw… on every record sheet, and filters for records never used in a session.
    • Trace a connection in the Campaign Graph to light up the chain between two records.
    • Themes: seven presets or your own colours, fonts, corners and background art.
    • Session builder: the whole Codex beside the outline, ready to drag onto beats.
    • Encounter builder: drag creatures, NPCs, Bestiary entries, places, factions and treasure onto an encounter. Every creature is its own participant, with Elite and Weak by the rules.
    • Reference cards open web pages and PDFs inside the card.
    • The Campaign Library shows each campaign’s art, what’s up next and the party.
    • Deleting a campaign sends it to the Recycle Bin.
  3. Development build

    Following Foundry, the Bestiary and sheet imports

    Live combat state from Foundry, a Bestiary from your own compendiums, and character imports from files.

    • Following Foundry: combats started in Foundry appear in Canonex automatically, with live hit points, AC and conditions for every combatant. A Foundry combat can be recorded as a Canonex encounter.
    • The Bestiary: creatures and NPCs by game system, built from the Foundry compendiums on your disk, with token art where available.
    • Import sheets from Pathbuilder 2e JSON and Foundry actor exports.
    • Re-classify records by dropping them on a type header in the Codex.
    • Party members are tied to each other, and Canonex reopens where you left it.
    • Areas open noticeably faster.
  4. Development build

    The Campaign Graph, player view and custom types

    See the whole campaign as a web, share only what the players should see, and define your own record types.

    • The Campaign Graph: every record and tie, with structural, story and secret ties drawn differently, and a Matrix view.
    • Player view: a separate window that shows only the portrait, handout, map or read-aloud you choose, never the GM desk.
    • Custom record types: a type editor, with type colours in Settings.
    • Layout prefabs: save a proven desk arrangement and reuse it in any session.
    • Every record on the same sheet, with shared templates for what many records have in common.
    • The first version of Canonex follows Foundry.
  5. Development build

    The desk becomes a GM screen

    Pin, lock, snap, save layouts, undo — the desk is now reliable enough to run a session from.

    • Pin cards to the edge of the view and lock them in place; snap to grid.
    • Saved layouts for scenes and runs, switched in an instant.
    • Reference tiles for web addresses: paste a link onto the desk.
    • Undo and redo, and avoid overlaps.
    • Every record type has its own colour.
  6. Development build

    Dossier sheets and the Foundry bridge

    Records get purpose-built sheets, and Canonex connects to Foundry VTT.

    • Dossier sheets: an NPC reads like a dossier, a creature like a combat instrument, with Location, Faction and player character sheets to match.
    • Native PF2e stat blocks that match Foundry imports.
    • Foundry VTT bridge through the REST API relay: link records to actors and pull their sheets.
    • Journals on every record, assets, and a Party board.
    • A zoomable desk with a minimap.
    • Drag records onto sheet sections to tie them.
  7. Development build

    Encounters, parties, running and wrap-up

    The full session loop is in place, from plan to run to wrap-up.

    • Encounter builder and runner foundation.
    • Player characters and parties as records.
    • Scene Runner: the live cockpit for the session being run.
    • Session wrap-up: promote what happened at the table into campaign canon, and carry unfinished material forward.
  8. Development build

    Campaigns, the Codex and sessions

    Canonex becomes an application, with multiple campaigns, a Codex and the first session planner.

    • Campaign Library: several campaigns, each with its own data, and quick switching.
    • Campaign Home and area navigation.
    • The Codex and the record model underneath everything.
    • Sessions: outlines of beats, drag and drop, and context-aware summon.
    • Campaigns are stored as folders of readable files.
  9. Development build

    Development begins

    Canonex starts as a native desktop app built around one idea — the GM's workspace.

    The first prototype proved the defining interaction: summon records onto a desk, move them near each other, and watch their relationships appear.