Flywheel

Tools · the Flywheel family

Six tools, one loop.

Each tool does one job and is useful on its own. Flywheel is the Method that joins them into one loop, from what is noticed to what lands, and the engine that runs it.

In use
sluice
Designed, not built
headwater, eddy, millpond, flume and sounding
The Flywheel family: one loop from what is noticed to what landsheadwater reports a new release of mise and eddy lists a recorded planning call; each prints a capture, and millpond keeps both. The release is its own excerpt, so it becomes one signal; a reader reads the meeting into three signals. Curation joins two of them into one item and makes the third, a question, an item of its own. Each item runs down the flume, which launches one agent in one worktree for it: the bump in one worktree, the export in a planner's plan, and the question in a sounding, whose accepted conclusion comes back to millpond as a new item. sluice tests each change as merged and lands both on main, and flume tidies the bump's worktree. The landed bump moves the pin back to headwater, which stops reporting that release. Flywheel is the Method the whole loop belongs to.Flywheelthe Method all of it belongs to1NOTICE2INBOX3LAUNCH4WORK5LAND6THE LOOP CLOSESthe landed bump moves the pin to 2026.10.10headwatermise 2026.10.10new release · reportedpinned · not reportededdyWispr · planningrecorded · 32 minmillpondthe inboxcapturessignalsitemsown excerptreadercurationflumeone worktreean agent on one brancha planner's plana chore for a teamsoundingworks one questionconclusion acceptedlanded · tidiedsluicetests each as mergedlands what passedmiseCSVmainbump miseCSV exportkeep JSONParquet?releasemeetingsentsentbump miseCSV exportbump miseCSV export2 signalsParquet?Parquet
The Flywheel family: one loop from what is noticed to what landsheadwater reports a new release of mise and eddy lists a recorded planning call; each prints a capture, and millpond keeps both. The release is its own excerpt, so it becomes one signal; a reader reads the meeting into three signals. Curation joins two of them into one item and makes the third, a question, an item of its own. Each item runs down the flume, which launches one agent in one worktree for it: the bump in one worktree, the export in a planner's plan, and the question in a sounding, whose accepted conclusion comes back to millpond as a new item. sluice tests each change as merged and lands both on main, and flume tidies the bump's worktree. The landed bump moves the pin back to headwater, which stops reporting that release. Flywheel is the Method the whole loop belongs to.Flywheelthe Method all of it belongs to1NOTICE2INBOX3LAUNCH4WORK5LAND6THE LOOP CLOSESthe landed bump moves the pin to 2026.10.10headwatermise 2026.10.10new release · reportedpinned · not reportededdyWispr · planningrecorded · 32 minmillpondthe inboxcapturessignalsitemsown excerptreadercurationflumeone worktreean agent on one brancha planner's plana chore for a teamsoundingworks one questionconclusion acceptedlanded · tidiedsluicetests each as mergedlands what passedmiseCSVmainbump miseCSV exportkeep JSONParquet?releasemeetingsentsentbump miseCSV exportbump miseCSV export2 signalsParquet?Parquet
The Flywheel family: one loop from what is noticed to what landsheadwater reports a new release of mise and eddy lists a recorded planning call; each prints a capture, and millpond keeps both. The release is its own excerpt, so it becomes one signal; a reader reads the meeting into three signals. Curation joins two of them into one item and makes the third, a question, an item of its own. Each item runs down the flume, which launches one agent in one worktree for it: the bump in one worktree, the export in a planner's plan, and the question in a sounding, whose accepted conclusion comes back to millpond as a new item. sluice tests each change as merged and lands both on main, and flume tidies the bump's worktree. The landed bump moves the pin back to headwater, which stops reporting that release. Flywheel is the Method the whole loop belongs to.Flywheelthe Method all of it belongs to1NOTICE2INBOX3LAUNCH4WORK5LAND6THE LOOP CLOSESthe landed bump moves the pin to 2026.10.10headwatermise 2026.10.10new release · reportedpinned · not reportededdyWispr · planningrecorded · 32 minmillpondthe inboxcapturessignalsitemsown excerptreadercurationflumeone worktreean agent on one brancha planner's plana chore for a teamsoundingworks one questionconclusion acceptedlanded · tidiedsluicetests each as mergedlands what passedmiseCSVmainbump miseCSV exportkeep JSONParquet?releasemeetingsentsentbump miseCSV exportbump miseCSV export2 signalsParquet?Parquet

One loop, from what is noticed to what lands. Flywheel is the Method it belongs to.

  1. 1headwater and eddy notice events and print captures.
  2. 2millpond keeps them as an inbox: captures become signals, and curation joins signals into items.
  3. 3millpond sends each item down flume, which launches one agent in one worktree for it, and tidies the place once the work lands.
  4. 4An item is worked in its worktree or a planner's plan. A question goes to a sounding, whose conclusion comes back as new items.
  5. 5sluice tests the work as merged and lands it.
  6. 6The landed bump moves the pin, so headwater stops reporting that release.

The family

The Method and its engine

Flywheel

in use

  1. Notice
  2. Inbox
  3. Launch
  4. Work
  5. Land

The Method for running a fleet of coding agents, and the engine that runs it.

Read the Method

Each stands alone

  • headwater reads what a repository declares and reports every release newer than its pin, with the notes and advisories. Its Claude Code and Herdr plugins keep unread releases in a sidebar, and one key starts an agent on the bump in a worktree.
  • eddy lists and fetches recorded meetings across meeting services. Its Claude Code plugin pulls a transcript into a session, and its Herdr plugin shows the day’s meetings.
  • millpond keeps an inbox in a git repository of your own. A session curates it through millpond’s tools, you accept each batch, and millpond sends an item to one worktree.
  • flume launches one agent in one worktree for an item, runs its stages, and tidies the place once the work lands. /launch starts one from any session, and each stage ends when its deliverable exists, never when the pane goes quiet.
  • sounding works one question in one session, in a worktree of its own, and ends on a conclusion: the answer, its evidence and the work it proposes. /sound opens one from any session, and you accept the conclusion, send it back for another round, or drop it.
  • sluice tests a change as merged and lands it. It never needs to know where the change came from.

The Method joins them

The tools meet at contracts, never inside each other. headwater and eddy print captures in one format, and millpond records each event once, whichever host ran the adapter. millpond sends an item to flume, which launches its work in one worktree, and the work lands through sluice. An item that asks a question goes to sounding instead, and its accepted conclusion comes back to millpond as new items.

Today the engine that plans across items is Crew, our team runner, which calls millpond and flume as it calls sluice. Flywheel’s engine is designed to stand on the same parts as millpond and read the same inboxes.

So a tool can be taken up alone and joined later. Going from millpond on its own to Crew, and later to Flywheel, changes the host and the curator. The adapters and the inbox stay put: nothing is captured twice, and nothing is imported when Flywheel takes over.