KAN › The board

The board: how rungs, state and acceptance are seen

A squad's work is spread across story files, commits and messages. The board puts it on one page without writing any of it, so a seat or the Operator can see what is waiting, on whom, and why.

Teaches from go/kanboard/README.md, specs/kan/stories/kan.13.aus.md and specs/format.md.

What it is

kanboard is “A live board of KAN programs, squads (rungs), time frames and coaching.” It reads the authored specs/ tree and follows the checkout's history, observes the KAN bus, and pushes all of it to a Mercury UI over server-sent events. It serves on 127.0.0.1:8650, loopback only.

Lessons

1. What the board shows: waits on you, dependencies, mail and questions.
2. A story's state: accepted, ready or waiting, and why the status line does not decide it.
3. Records the board can read: rung and story records, and commit subjects that name what they land.

Previous: The method · Next: What the board shows · Up: KAN

Teaches ecd/kan at 54532f9b, 25 October 2026.