Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Deciding a conclusion

The operator decides each conclusion: on a card, in sounding’s herdr plugin, or on crew’s rail. A conclusion gets one decision, and the operator gives it once (6).

AnswerWhat follows
AcceptSettles the item. millpond keeps the conclusion as the item’s record, and each piece of work the conclusion proposes becomes an item of its own, or an entry in crew’s plan.
Go onStarts the next round in the same worktree. The conclusion moves to rounds/<n>.md, and the operator’s notes join the next session’s question.
DropRecords the reason and removes the worktree.
sounding open Working round n conclude Waiting on the operator accept Settled the item's record; new items drop Dropped the reason kept, the worktree gone go on rounds/<n>.md kept, notes join the question
Each round ends waiting on the operator. Accept and drop end the sounding; go on starts another round in the same place, with the last conclusion kept and the operator's notes in the question.

Accept

Accept ends the sounding and settles its item. millpond keeps the conclusion as the item’s record, and each piece of work the conclusion proposes becomes an item of its own. In an inbox crew keeps, crew’s planner turns each piece into an entry in its plan. Either way the work reaches main on a branch of its own, through sluice (The place).

The record outlasts the sounding. When a later signal arrives on the same subject, curation answers it by naming the conclusion (116), and the operator is not asked again.

Go on

Go on starts the next round in the same worktree. The conclusion moves to rounds/<n>.md, and the operator’s notes join the next session’s question: what the answer missed, what to try next, what to leave alone. The start hook hands the new session its question, its sources and every earlier round (The question and its sources).

Drop

Drop records the reason and removes the worktree. Nothing from the place lands. Offers the sounding already made stay in the inbox, since each is a capture of its own and an unmoved signal is never discarded (118).

A conclusion is never a signal

An accepted conclusion enters the inbox as a record, never as a signal. Three facts about the inbox require it:

  • The item’s signals already have their move. Curation joined them into the item, and curation never judges a signal that has a move again (107). A conclusion made into a signal would put the same subject in front of curation a second time.
  • The operator has already decided it. Approval given once is never asked again (6). A signal would bring the conclusion back as a decision, through curation’s batches and the item it joined.
  • What the operator accepted settles signals. Curation answers a later signal on the subject with answered, naming the conclusion as the record that settled it (116).

Only offers come back as signals. An offer is about something beyond the question, which no move has judged and no decision has settled, so it starts where every capture starts.

a conclusion: a record Accepted conclusion The item's record kept by millpond answered names it (116) A later signal on the subject an offer: a capture An offer beyond the question millpond land a capture, its own excerpt its one signal Curation gives it a move
An accepted conclusion enters the inbox as a record, and curation answers later signals by naming it. Only an offer enters as a capture, and only its signal is curation's to move.

From a question to a landed bump

One question, from the release that raised it to the bump that lands:

  1. headwater reports version 5 of a library the repository declares as ^4.2. The release lies outside the declared range, so taking it changes the manifest (headwater’s book).
  2. The release lands in millpond as a capture that is its own excerpt. Curation joins its signal into an item that asks whether to take the release.
  3. millpond sends the item to a sounding, with the release’s signal and capture as its sources.
  4. The session reads the notes, makes the bump in its place, and runs the repository’s checks there to see what breaks.
  5. It concludes: take version 5. Its evidence is what the checks showed, what it would change is the code the new version touches, and the work it proposes is the bump.
  6. The operator accepts. millpond keeps the conclusion as the item’s record, and the bump arrives as a new item.
  7. The bump is made on a branch of its own, and sluice lands it.
  8. The next signal on the subject reaches curation, which answers it by naming the conclusion.

The prototype bump in step 4 never lands. The bump in step 7 does, on its own branch, through sluice.