Docs contents
DOCS / WORKING IN THE DESKTOP
Follow work on the board
The board shows one card per manifest in five columns, from Ready to Landed, and updates live as the ledger records each change.
The board is the desktop's main view of your Works. Each card is one manifest, titled in the words of the brief or petition it came from, and it sits in the column for the stage that manifest has reached. For how manifests and tickets relate, see manifests and tickets.
Open the board
Choose Cadence in the left rail. The view is headed Board, and your Works' North Star appears under the heading when one is set. You do not need to refresh it. The board repaints as each event lands on the ledger.
The five columns
Each column has a label and a short line saying what stage it covers:
- Ready · Work · awaiting a seat. At least one ticket on the manifest is open and has no owner yet. A manifest with a blocked ticket also stays here.
- In flight · Work · latched to a seat. A ticket has been assigned to a seat, but no agent is running on it.
- Dispatched · Hand · run streaming. An agent is running on one of its tickets, or is paused mid-run.
- Needs land · Gatehouse · awaiting land. Every ticket is finished, but the manifest has not been landed. Nothing is left but the land step, covered in dispatch and the gatehouse.
- Landed · Gatehouse · recently completed. The manifest has landed.
A manifest sits in the first column that applies, in that order. Needs land is worth watching: under a per-ticket land policy, the next ticket on that manifest cannot be dispatched until the finished one lands.
At the default window size, scroll sideways to reach the fifth column. In a wider window, all five fit.
Read a card
Each card shows the manifest's title, a line from its brief, and a row of beads, one per ticket in roster order:
- Yellow: an agent is running on that ticket, or is paused.
- Red: the ticket is blocked, or its run ended while the ticket was still assigned.
- Green: the ticket is complete or landed.
- Grey: the ticket has not started.
A card shows at most eight beads. A Needs land card is usually all green. A green card sitting in Ready usually means a follow-up ticket was just added.
Order and context
- The Latest and Oldest chips in the board header set the card order. Latest puts the most recent activity at the top of each column.
- Connection opens a drawer with the connected Works, its path, and the Cadence ladder. The ladder counts tickets at each stage of the org cycle, and pressing a stage scrolls the board to its column. The ↻ button refreshes the counts.
Drill in
Press a card to open the manifest's detail view: its title and description, a Tickets list, and a Resources list of what the manifest shipped. Properties shows the stage and other fields. ‹ Board takes you back. From there, press a ticket to open it. See a ticket's detail and activity.
Advanced
From the command line
The same facts are readable from the terminal, and they come from the same record:
hm manifest list --phase active # manifests still on the board
hm manifest status <manifest-id> # per-ticket states and a land-readiness verdict
hm query board --manifest <manifest-id> # open and latched tickets for one manifest
hm ticket list --state complete # finished tickets not yet landed
hm gatehouse land <manifest-id> --dry-run # what landing a Needs land manifest would doChecked against crates/hm-desktop/ui/src/lib/board.ts, reviewed 2026-09-14. That file is what makes these steps true; this page is a reading of it, and is not where it is edited.