Lay out what has to happen first before you promise a date
Put the steps that have to happen before a Thursday invoice PDF can ship in order on a BaseHalf canvas. Connect the answer only to those steps, including the one still waiting on legal, and leave a nice-to-have off the path.
A Monday message asks whether the new invoice PDF can go out on Thursday, and, in the same sentence, whether you can redraw the little receipt icon while you are at it. The cheap mistake is to say yes to Thursday, then notice that legal has not sent the one sentence the PDF still needs. The cheaper work is earlier, and it is visual: put the steps that have to happen first in order, leave the nice-to-have off the path, and write the answer only after the blocked first step is in view.
This is a different step from unpacking a fog until you can name a question, from lining up options against a checklist, from separating observations from interpretations, from sorting facts, assumptions, and open questions, from keeping a problem away from the fixes already being offered, from weighing evidence for and against, from laying out the conditions for a yes, or from separating what was decided from what is still open. Here the question is already named. The risk is that Thursday gets promised as if the path were clear, or that a nice-to-have gets treated as if it were a step on that path.
What has to happen first, and can we promise Thursday?
Say a small team got this mix on Monday:
These are the steps that have to happen, in order, before the invoice PDF can be called shipped:
- Legal has to approve the one-sentence disclaimer that goes on the PDF. As of Monday noon, that sentence has not arrived. This step has not started.
- The PDF template can be finished only after that sentence is in it. The template is not a parallel task.
- The renderer can be wired only after the template exists.
- The invoice email can attach the new PDF only after the renderer works. Until then, the existing email still sends the old attachment.
- A staging send to a real mailbox has to pass before we call it shipped. That last check is not optional if we are going to promise a date.
And then there is one sentence that is not on the path:
- "While we're at it, redraw the little receipt icon." That is a nice-to-have. It does not have to happen before the invoice PDF can go out, and it is not a reason to accept or refuse Thursday.
On a BaseHalf canvas, those notes are ordinary Markdown files in one folder. The left-to-right, then down, order of the five steps is for your eyes. The receipt icon sits off to the side of the question, under a "Not on the path" label, so it cannot pretend to be a Thursday requirement.

A sequence is not a connection, and neither is a selection
Sitting in order on the board does not make a step part of the answer. A connection does. In BaseHalf, a line from A to B means A is upstream of B: A's context flows into B, and the list is saved in B, in the frontmatter of a Markdown note. The answer on this board is connected to the five steps. The first step is part of what the answer stands on. It is why the answer refuses to promise Thursday: legal has not sent the sentence, so every step after it is waiting too.
The receipt icon stays off the path, without a line. The icon may still be worth doing later. The answer does not use it, so it is not declared as its upstream.
You can still point at a slice without changing those lists. A selection is temporary. It is what "this" can refer to if you later ask an agent. It is not written into the answer, and it does not force an agent to read only those files. A request that names something else still wins.
Select the slice the answer already named
For this board, the slice is the answer and the five steps it is connected to. The receipt icon stays visible on the board, and it stays out of the selection.

If you then ask Claude Code or Codex, ask about that slice. Not "can we do Thursday?" Ask whether those five notes can support the hold the answer names: five steps in order, the first still waiting on legal, and no writing of the receipt icon as if it were on the path.
What to keep after you answer
Keep the named question, the answer, and the upstream list that says which steps it rests on. Leave the receipt icon parked, so it is not mistaken for a Thursday requirement the next time someone opens the folder. When legal sends the sentence, update that first step, and only then consider rewriting the answer. Do not connect a nice-to-have just because it sat nearby.
Limits
Five cards in order do not make the path complete, or the names the right ones. If the renderer also waits on a certificate that nobody put on the board, or legal sent the sentence at 11:50 and nobody updated the first card, you will have a tidy board that still misses the failure. The canvas makes it visible which steps you treated as the path, which one you treated as blocked, and which nice-to-have you refused to promote. You still have to get the sentence, or change the answer when it arrives.
Put the steps that have to happen first in order, before you promise a date. Write upstream only for the notes that answer actually uses, including a blocked first step that makes Thursday a promise you cannot keep. Select that slice if you want to ask an agent about it.