Skip to content
flumeflumeflume

flume is designed, not built. Its design book holds the design whole.

How it fits

flume stands between what decides the work and what lands it. millpond, headwater, sounding, crew and your own sessions decide what to launch; flume makes the place and runs the stages; sluice lands the result. Each tool stands alone, with its own Claude Code and herdr plugins.

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

Section titled “The family”

millpond · the inbox

Sends an item to one worktree through flume, as a fix or a change. millpond records the send and hands flume the brief, and writes the landing against the item from sluice’s record of the branch. An inbox crew keeps sends nothing to flume itself.

headwater · releases

Its fix key hands a release’s brief to flume as a fix, and an agent makes the bump and submits it to sluice. In a repository crew runs, the key hands the release to millpond instead, and the bump comes as a chore from crew’s plan.

sounding · questions

A question runs as flume’s kind question. flume makes the place on sounding/<name> and runs the session; sounding keeps the question, its rounds and the conclusion you decide. A sounding waiting on you shows in flume’s herdr sidebar.

sluice · landing

Lands what the last stage submits, tested as merged. flume never lands anything itself: it reads sluice’s verdict and tidies the place once the work lands.

crew · teams and plans

Keeps everything that spans many places: plans, bolts, slots, the dispatcher, conductors, approvals, and conflicts between units. crew asks flume for each place and each stage’s agent, as it asks sluice for each landing.

Flywheel · the Method

The Method the family belongs to. crew becomes Flywheel, which is built later on the same parts as millpond.

Who launches

Section titled “Who launches”
Caller Launches
You /launch <brief> in any session, or the herdr plugin’s key
millpond an item’s send, as a fix or a change
headwater the fix key, as a fix with the release’s brief
sounding a question, as the place and session of a sounding
crew each unit, chore or fix of a team, as a place of a kind crew carries in the launch, every stage after the first waiting on crew’s word

Whoever launches, the place, the stages, prompt delivery and tidying stay the same. Only the brief and who reads the result change.

What flume never does

Section titled “What flume never does”
  • It never decides what to launch. A caller names the repository, the kind, the brief, the name and the base.
  • It never plans across items. crew’s planner orders work today, and Flywheel’s does later.
  • It never lands anything. A stage submits to sluice, and sluice decides.
  • It never keeps an item’s record. millpond does. flume keeps only the live state of the places it runs.
  • It never removes what it did not make, and never removes a branch that holds commits its base lacks.

Built once, used everywhere

Section titled “Built once, used everywhere”

flume holds the one implementation of places, a fresh agent per stage, prompt delivery, stages that end on their deliverable, and tidying. It grows out of crew’s rules for teams and plans (teams.2 to teams.4, teams.11, teams.15, and plan.9, plan.10, plan.12 and plan.17), and millpond, headwater, sounding and crew all build on it.

Built in the open by agentplot, under the MIT licence.