A pipeline is the at-a-glance picture of the work: every matter laid out as a card, sorted into columns by the stage it is at. It is the human-facing view of the caseload, generated from the matters themselves rather than maintained as a separate copy, so what you see is always what is actually true. Open it to scan where everything stands, move a matter forward without leaving the board, and jump straight to any matter that needs you.
What it does
The pipeline is a kanban board over your matters. Each card is one matter, and each column is a stage that matters move through.
-
Matters grouped into stage columns. The board reads the projected state of every matter and groups the cards into ordered lanes: pending, active, blocked, and completed. The columns appear in a stable order, with the always-on lanes shown even when empty, so the shape of the board does not jump around as work moves. Each lane carries a live count of the matters in it.
-
A card per matter, with its real status. Every card shows the matter’s title and its number (prefix and sequence), and the column it sits in tells you the step-stage it has reached. A coloured dot on the card surfaces the matter’s lifecycle status, distinct from the stage, so a matter that is on hold, completed, or cancelled is visible at a glance rather than hidden inside a lane.
-
Advance a matter from the board. Each card carries an Advance affordance. Press it and the matter completes its active step and moves to the next one, then the board refreshes itself so the card lands in its new column. You drive the work forward from the same place you are watching it, without opening each matter first.
-
Jump to a specific step. Where a situation calls for it, the board can send a matter straight to a named step rather than walking it one advance at a time. The free-jump is a first-class move, not a workaround, and the board re-pulls afterwards so the picture stays current.
-
Always a regenerable view, never a second copy. The pipeline is projected from the matters in Postgres, which remain the single source of truth. The board is a view of that truth, so it can be rebuilt at any time and can never quietly drift into a second version of reality. Click through any card and you are on the matter’s own detail screen, the authoritative record behind the card.
How you use it
-
Open the pipeline. Go to the pipeline view and the board loads your caseload: the stage columns across the top, each with its count, and the matter cards filling the lanes they belong to. Empty leading lanes still show so the board reads consistently.
-
Scan where the work stands. Read the columns left to right to see what is pending, what is active, what is blocked, and what is done. Glance at the coloured dots to spot the matters that are paused or closed without opening anything.
-
Advance a matter in place. Find the card, press Advance, and the matter completes its current step and moves on; the board refreshes and the card reappears in its new lane. If the advance cannot proceed, the error surfaces on the board rather than failing silently.
-
Open a matter. Click a card to go straight to that matter’s detail view, where the full step pipeline, activity, documents, and parties live.
-
Refresh. Pull the board again at any time to reconcile it with the latest state of the matters, since the view is always derived rather than stored.
You can drive all of this by chat, from the board screens, or on the command line. They are the same governed actions underneath, so the matters behave identically however you reach them.
The kernel verbs behind it
Every action on the pipeline is a named verb that passes through the one front door: permission-checked, scope-checked, and audited before it runs. These are the verbs the board is built from, plus the board-lifecycle verbs that maintain the projection it reads.
Building and driving the pipeline:
board.issue.list- read the projected issues whose stage groups the cards into columns.matter.list- the matter index behind each card, supplying its number, prefix, and lifecycle status.matter.advance- complete a matter’s active step and move it to the next, straight from its card.matter.goto- jump a matter to a specific step when the situation calls for it.board.issue.sync- reconcile a single projected issue back to its matter and step (a view refresh).
Maintaining the projection underneath:
board.create- author a board.board.edit- edit an existing board’s configuration.board.get- read a board.board.list- list the boards in the workspace.board.publish- mint the instantiable version; DRAFT to PUBLISHED.board.step.condition.set- set the rule that decides when a card moves between columns.board.regenerate- tenant-wide reconcile: re-project every matter, step, and gate from Postgres into the issue set, with a drift report.board.stop-projecting- stop projecting a board’s view while leaving the matters untouched.board.sync.status- read the projection’s sync state.board.archive- withdraw a board from new instantiation.
See the full set in the board verb reference.