Put who owns each step on the board
We planned a Tuesday FAQ update for the plans page on a BaseHalf board, connected the goal, constraints, and named owners for each step to the briefing, and had Claude Code write a plan that names who does each step by when.
A shared FAQ update falls apart when the plan is a list of tasks and the names live in a chat. Leaving an owner off the board is not the same as writing who does each step, and by when, where the next person can see it.
I was planning a Tuesday FAQ update on the plans page, to publish three answers (annual billing, seats, and refunds) by 18:00, Asia/Shanghai, on 2026-11-17. There are no design changes, legal has to see the refund wording before it goes out, there is one pull request, and the live page has to be checked after the merge, still on Tuesday, before 18:00. Alex drafts the three answers by 11:30. Mei reviews only the refund answer from 13:00 to 13:30. Alex opens the pull request by 15:00. Rina merges and checks the live page by 18:00. Someone later suggested a fourth answer about education discounts. That is not part of Tuesday's three answers, and it has no owner on this board.
I opened a folder in BaseHalf 0.7.0 and spread the pieces as cards: the goal, the constraints, four step notes with those owners and times, and the later idea. I then wrote briefing.md and connected the goal, the constraints, and the four steps, in that order. I did not connect the education-discount idea. Sitting next to the briefing is not enough. If the plan is going to name an owner, that step 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 owner-plan.md as specified, and not edit the existing notes. The briefing asked for each upstream step in that order, with the owner and the time already written on the step, not a generic task list with the names left off, the constraints kept in view, and no invented steps, owners, or times.
After 33 seconds, at 18:30 Asia/Shanghai, the file was there. Claude Code was v2.1.325, Opus 5.5, with xhigh effort, on Claude Ultra. 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 a table of the four steps: Alex by 11:30, Mei from 13:00 to 13:30, Alex by 15:00, and Rina by 18:00. Under that, each step keeps the wording from its note. The constraints are tied to the steps they affect: no design changes in the draft, legal review before the pull request, one pull request, and the live-page check finished before 18:00. It also records a gap that is in the notes: step 3 says to request review, and step 4 says to merge after review, but no note names the reviewer. The education-discount 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 owners were on the step notes before the agent ran. The agent wrote a new file in the same folder. It does not invent who owns a step. If you do not connect those notes, they are only scenery. If you connect them, they can become a plan that still names who does each step when you open the folder tomorrow.