03 — The board
Seven columns, and two of them are gestures.
This is where your control over the system lives. The names are yours — map them under [notion.status] — and doctor checks each one actually exists on the board.
| Status | What it means |
|---|
| Ready | the description is precise enough for an agent to handle it alone. The gesture that triggers work. |
| In progress | claimed by the runner. Stops the next run from taking it again. |
| In review | branch pushed, pull request opened. Yours to review. |
| Validated | you read it and said yes. The second gesture — the runner merges the pull request, or publishes what the ticket holds, and then closes it. |
| Done | that pull request has been merged — or the ticket produced a document, which has nothing to wait for. |
| Failed | something broke: the session, the push, the worktree. Its worktree is kept for the post-mortem. |
| Blocked | the agent would not guess and asked a question instead. Answer in a comment and the ticket runs again. |
In review rather than Done, because nothing is done when the runner lets go of a ticket: a pull request is waiting for a human, and a board that calls that Done stops being believed by the second week. Blocked is its own column rather than a shade of Failed, because a ticket waiting for you and a session that crashed are different days.
What a ticket carries
The body of the page is the brief: write there what you would tell a developer who does not know the subject. Leave the title empty and the runner writes one from the body. The rest is columns, and most are optional:
| Property | Role |
|---|
Project | relation — decides the repository, and therefore whether the ticket is code or a document |
Agent | relation — decides who handles it: one row per role, the body of its page is the role |
Priority | Urgent, High, Normal, Low — which ready ticket runs first |
Model | opus, sonnet, haiku — this ticket’s model, over its agent’s and over runner.model |
Scheduled | hold the ticket until that moment — a ready ticket waits to start, a validated one waits to go out |
Progress | what the session is doing right now, rewritten every ten seconds — Bash · npm test |
Session | written when the ticket is claimed. Make it a URL and its cell becomes a button that opens the conversation in a terminal |
Pull Request, Cost, Duration | filled by the runner at the end |
Three pages, from the widest frame to the narrowest
the context page who you are, what you work with, how you like things written
↓
the project page the conventions of THIS project — and whether it names a repository
↓
the agent page the role: “Dev front”, “Rédaction” — and, if it says so, the model
↓
the ticket the task
Whatever you write on a project page becomes standing instructions for every ticket of that project, written once instead of retyped. That is what turns “write me a post about the new tool” into your voice rather than a generic one — and, on a code project, what carries conventions that belong in no single ticket.
Following the work
While the session works, its steps are written into the ticket on a ten-second cadence: one toggle per run, a bullet per file read and per command run, and what the agent said as a paragraph of its own.
⏳ Live — 12 step(s) · 3 min
• Read src/app/header.component.html
──────────────────────────────────────────────────────────────────
I will remove the banner from the template and the stylesheet rules
that went with it, then run the tests.
• Edit src/app/header.component.html
• Bash npm test -- --watch=false
Every ticket is a real Claude Code session — the same transcript your own sessions produce. claude --resume <id> reopens it from any directory, and keeps working after the worktree is gone. When a ticket finishes, its transcript is filed under the repository, so claude opened there lists it in its session picker.
