KAN All courses

KAN › The board · lesson 3 of 3

Records the board can read

The board shows only what it can read. Records in the agreed format, and commit subjects that name what they land, are what let it place a change under the right story.

Teaches from go/kanboard/README.md and specs/format.md.

The rule

Stories and rungs follow the shared format: ordered front matter with a real KAN id, then the story's 6W, its uncertainty and decisions, its delivery and its acceptance, each under its own anchor. The rung record references its member stories without copying their promises.

Commits become events. “Each commit on the checkout's first-parent history shows as a LANDED event with the story or rung its subject names”: the reference it starts with, such as kan.15: …, otherwise the first one anywhere in the subject. “Versions (go1.26.5, v2.37) and file names (kan.15.aus.md) are not references.”

Try it

From commit to story

  1. The story record
  2. The rung record
  3. The commit subject
  4. The LANDED event

The story record
Ordered front matter with a real KAN id, then the story's 6W, its uncertainty and decisions, its delivery and its acceptance, each under its own anchor.

In the EchoEdu delivery

This course's story was committed as specs/edu: edu.29, the KAN course at /courses/kan (proposed). The first reference in that subject is edu.29, so the board can place the landing under the story. A subject that names no story, such as a bare Merge pull request, takes the reference of the merged branch's subject instead, so the branch's own commits need to name it. The safest form starts the subject with the story it delivers, as in edu.29: ….

Check yourself

  1. Your commit subject is fix tests in kan.15.aus.md. Which story does the board place it under?
  2. Where does a rung record keep its member stories' promises?
  3. What does a merge commit whose subject names nothing show under?

Previous: A story's state · Up: The board · Next section: The bus

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