From 3.62.0 you can say which board each kind of item goes on, and the build loop puts work there when it starts, not when it is planned. Only /devstride:setup boards (or a full setup run, when no rules are set yet) writes this block, after a typed yes; see Guided Setup. There is no shipped default: the boards are your organization's.

Key Shape Absent behavior Purpose
boardPlacement null, or { "rules": [ … ] } nothing is placed, a one-off's board is asked as before, and personal rules are ignored Where each kind of item goes when work on it starts.
boardPlacement.rules an ordered array of { "name"?, "match"?, "place" } required when the block is set; an empty array places nothing Read top to bottom; the first match wins.
  • match — every condition named must hold, and a list holds when any entry does: workType (names, any case), team (team ids), tag (tag names, any case), customField ({ "<field id>": [values] }, the values as items carry them, so a choice field's option ids rather than their labels) and under (item or workstream numbers: the item sits anywhere beneath one). A rule with no match matches every item.
  • place — exactly one of { "board": <board id> } (one long-lived board), { "cycleFolder": <board folder id> } (the dated board directly in that folder whose dates cover the day the work starts) or { "none": true } (stays off boards). A rule may never place on the Active Agents board.
  • Personal rules. /devstride:setup boards personal writes one contributor's rules, the same shape, to a file on their machine outside the repository. They are read before the repository's, so they state only what differs for that person, and they apply only when the repository has a block of its own.

What the loop does with the rules:

  • build-item places each item it picks up, and then that item's release unit, before it moves the item's status. It never sets a status here, never places anything above the release unit, and never touches the deferred container.
  • create-story and create-defect take a one-off's board from the rules instead of asking, and honour a rule that says no board. A one-off has no team or custom field when it is created, so a rule on either does not apply to it.
  • Nothing is taken off a board, and a finished item is never moved. An item someone put on another board stays there, including a cycle it was planned into that has not ended; only an item left on a cycle that has ended is carried over to today's.
  • It fails open. A board that cannot be resolved, such as a cycle folder with no board for today, or a failed move is one line in the progress table: placement never stops the loop or asks you a question.

/devstride:doctor agents checks the rules read-only. The contract is skills/setup/references/boards-mode.md and skills/build-item/references/board-placement.md in the plugin repository.