/ admin / work

The units of work for this store, as a board. Two levels, like the board this one is modelled on at sgraph.ai/en-gb/dev/workstreams/: the top board has one card per workstream and the column it sits in is derived from its own tasks, and opening a card gives that workstream's tasks in the same four columns. A workstream is never dragged — it moves because a task in it moved, which means the summary cannot disagree with the detail.

How a unit of work gets here

A unit of work is an object in this file. The board, the counts, the rail badge and the per-workstream page are generated from it, and a build check fails the release on a task with a status this board does not have or a source that names a review that does not exist. Adding work is adding a line; there is no second place to update.

A workstream is never dragged. The column a workstream card sits in is computed from the tasks inside it — all done and it is done, anything in progress and it is in progress — so the board above cannot say something the board inside a card contradicts. The progress bar is done over total and nothing else; it is not an estimate and it is not a percentage of effort.

The four columns

Where this shape came from

The two-level board — workstream cards whose column is derived, opening into that workstream’s own tasks in the same four columns — is the one running at sgraph.ai/en-gb/dev/workstreams/, read on 16 September 2026. The column names and their colours are that board’s, kept deliberately, so somebody who reads both reads one scale rather than two.

What is not adopted is how it is fed. That board reads its JSON out of an encrypted vault at runtime with a published read key, which is the right answer for a site built to do that. This one renders at build time from a file in the repository, because every page on this store opens no connection and exists and runs 11 Sep 2026