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

Curation and moves

Curation gives each signal one of Flywheel’s six moves (116). A curation session is a Claude session working through millpond’s tools. It proposes moves in batches, the operator accepts or changes each batch, and the session writes it. Curation writes no captures and no signals.

The six moves

MoveConsequence
dropRecords the reason.
answeredNames the claim or record that settled it.
challengeWeighs against a claim. Only an inbox beside Flywheel’s claims has one.
joinMakes an item, or grows a proposed one, from any number of signals.
attachPuts the signal on an item already sent.
routeOffers a chore, which millpond makes an item of one, or an ask, which it records.

Every signal has exactly one standing move, stored with the signal, its target, its reason and its date (107). Curation runs over signals with no move and never judges a signal that already has one (107). A route that offers neither a chore nor an ask is refused (116).

An unmoved signal is never discarded, and weight counts by event date (118). A signal moved a month after its meeting still counts on the meeting’s day.

Working through a backlog

Nobody picks through hundreds of signals by hand. The curate skill starts a session that asks signals for the oldest fifty unmoved, reads the raw material of the unclear ones with capture, and proposes a move for each. The operator accepts the batch or changes rows, and the session writes it with one moves call.

The operator Curation session the curate skill millpond its MCP tools curate the oldest fifty signals: unmoved, oldest, 50 fifty signals with their excerpts capture: the unclear ones proposes: drop 18, answered 6, join 26 into 5 items accepts, changing one row moves: the batch, one commit The next batch starts where this one ended.
The session proposes a move for each of fifty signals, the operator accepts the batch or changes rows, and one moves call writes it as one commit. The operator judges a proposal, never a signal at a time.

A batch is the operator’s unit of attention. The session does the reading, and the operator does the deciding: one decision per batch, and per item that the batch proposes (109). The next batch starts where that one ended.

The operator’s surfaces

The operator curates from whichever surface is at hand, and each reads and writes through the same tools:

  • millpond’s Claude Code plugin holds the curate and read skills and starts millpond mcp.
  • millpond’s herdr plugin shows the count and age of unmoved signals by source (118), lets the operator review a proposed batch row by row, and sends an item with one key.
  • crew’s rail shows an inbox crew keeps, one decision per item (109).