Put the done-when checks on the board
We planned a Tuesday morning visitor Wi-Fi card on a BaseHalf board, connected the goal, constraints, and explicit done-when checks to a briefing, then had Claude Code write a plan that keeps those checks as acceptance lines, not only a list of tasks.
A visitor card plan falls apart when "done" means the draft was written. Putting the goal on the board is not the same as writing the checks that say when the card is actually finished, where the next person can see them.
I was planning one visitor Wi-Fi card for the front-desk tray, before Tuesday opening at 09:00, Asia/Shanghai, on 2026-11-17. A visitor at the desk should be able to connect to the existing guest network from the card, without asking a second question. It has to fit on one side of one card, in English and Chinese. There is no new hardware and no new network name. The current password stays on a staff-only slip, and must not be printed on the visitor card. The finished card has to be in the tray before 09:00. Done also means a coworker who did not write the card has followed it once on a phone, and connected without help. Someone later suggested reprinting the card with a QR code. That is not required for Tuesday morning, and it is not one of the done-when checks.
I opened a folder in BaseHalf 0.7.0 and spread the pieces as cards: the goal, the constraints, four done-when notes, and the later idea. I then wrote briefing.md and connected the goal, the constraints, and the four checks, in that order. I did not connect the QR-code idea. Sitting next to the briefing is not enough. If the plan is going to treat a line as a done-when check, that note has to be in the upstream list. Card places are saved under .bh/ and stay out of git. The lines are the upstream lists in the files.

I selected the briefing card. The status bar showed that agents could see briefing. In the Agent Area I started Claude Code and asked it to follow briefing.md, use only that note and the files in its upstream, write done-when-plan.md as specified, and not edit the existing notes. The briefing asked for each upstream done-when check in that order, as an acceptance line, not only as a task to draft or print the card, with the constraints kept in view, and with no invented checks, times, or deliverables, and no later idea treated as a Tuesday morning requirement.
After 29 seconds, at 18:22 Asia/Shanghai, the file was there. The new note appeared in the sidebar and as a card on the canvas, already connected. I opened it and read it myself.

The plan starts with the goal, then keeps the constraints in view, then a Done when section: the card is done only when all four lines are true, and drafting or printing the card does not count as done on its own. The four lines are the checks already written on the notes: a visitor can connect from the card, the password stays off the visitor card, a coworker has followed the card once, and the card is in the tray before 09:00. It also records a gap that is already in the notes: lines 1 and 2 pull against each other, because a visitor has to connect without asking anything, but the password cannot be on the card, and the notes do not say how that is solved; line 3 is where it gets tested. The QR-code idea is not in the plan. The new file's upstream lists the briefing and the six notes it draws on, not the unconnected idea. None of the existing notes were edited.


This board is still an ordinary folder of files. The done-when checks were on their own notes before the agent ran. The agent wrote a new file in the same folder. It does not invent what counts as done. If you do not connect those notes, they are only scenery. If you connect them, they can become a plan that still says when the work is finished when you open the folder tomorrow.