---
{
  "n": 5,
  "title": "Revising the board's drafts",
  "abstract": "",
  "refs": [],
  "seen": [
    "system",
    "agent"
  ],
  "data": {
    "starts_on": "message.revised",
    "system": true,
    "environment": "test333",
    "files": {},
    "started_by": "user",
    "quiet": true,
    "only_when_idle": false,
    "talks_in": "the New work panel",
    "unless": {},
    "lasting": false,
    "dispatch": "board-filler"
  },
  "created": 1790221144.1083379,
  "updated": 1791235675.092911,
  "deleted": 0.0,
  "completed": 0.0,
  "outcome": "",
  "type": "sequence"
}
---
The user typed a change in a board's New work panel while its drafts show. Change only what they asked for, keep every other draft as it is, and say one line. Never start over and never ask round one again.

## Read the change
Read their words and the drafts made for this request on the board. Work out which cards the change is about. When it is unclear, ask one short question on the board with the cards it might mean as options: journal board ask <board n> "<question>" --set options='[...]' --set pick=<n>. When it is answered, or clear from the start: journal sequence next <this sequence> --about <ref>.

## Change the drafts
Change only the cards they named: journal ticket update <n> with a new title, --abstract or --brief, or delete a card they dropped (journal ticket delete <n> --why "<their words>"). Anything new they ask for becomes cards of its own, one per part, never a to-do. For a card they asked to add, first raise the count to the total the panel should show: journal board expect <board n> <count>, then journal ticket create as in drafting. When they ask you to choose cards for them, check the ones you would keep: journal board pick <board n> "<ticket>, <ticket>". When every change is made: journal sequence next <this sequence> --about <ref>.

## Recheck the drafts
Check the drafts still meet every clause of the goal (journal board show <board n>), that at least 6 remain unless they asked for fewer, and that the order between cards still holds (journal ticket depend). Draft what a removal left uncovered. Then journal sequence next <this sequence> --about <ref>.

## Say one line
Say it in the panel in one short line with journal board say <board n> "<line>", of at most 200 characters about what changed, like "Made the sign-in card smaller and added one for invites." No paragraphs and no ticket numbers. Then say you wait for the user with journal board wait <board n>, and finish with journal sequence next <this sequence> --about <ref>.