Skip to content
soundingsoundingsounding

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

sounding

sounding works one question in one agent session, in a worktree of its own, and ends on a conclusion you decide.

How it worksRead the designGitHub
sounding: one question, one session, one conclusionA session types /sound take mise 2027.1? and goes on with its own work, its progress bar never stopping; beside it, millpond can send an item that asks a question. sounding opens a worktree on the branch sounding/take-mise-2027 and writes question.md. One session works the question there against a 45 minute timebox: it reads the question and the release notes, runs CI on the new version, writes prototype code to try/bump.patch, finds two scripts failing on a renamed flag, and concludes. conclusion.md holds the answer, take mise 2027.1 once two CI scripts pass --locked, its evidence, the work it proposes and what stays open. The card waits on the operator, who accepts it. Prototype code stays on the branch: a sluice submission from sounding/* is refused. sounding one question, one session, one conclusion OPENED FROM your session /sound take mise 2027.1? its own work, going on sounding opened · work goes on or millpond sends an item that asks a question, its signals as sources A WORKTREE OF ITS OWN sounding/take-mise-2027 FILES question.md the question, its sources try/bump.patch prototype code conclusion.md the answer Prototype code stays on this branch: a sluice submission from sounding/* is refused. take mise 2027.1? one session · round 1 waiting working concluding ended read question.md read mise 2027.1's notes ran CI on 2027.1 wrote try/bump.patch 2 scripts fail: --frozen 2027.1 calls it --locked sounding conclude timebox 45 min done at 31 of 45 min THE CONCLUSION not yet written conclusion.md · round 1 answer Take mise 2027.1 once two CI scripts pass --locked. evidence both scripts ran on 2027.1 proposes the scripts, then the bump open Linux runners untried accept accept go on drop waiting on you: a card, or herdr accepted · its work becomes items 1 Ask from any session, or from an item millpond sends. 2 One session works it in a worktree of its own. 3 It ends on a conclusion: the answer, evidence, the work. 4 You decide it: accept, go on, or drop.
sounding: one question, one session, one conclusionA session types /sound take mise 2027.1? and goes on with its own work, its progress bar never stopping; beside it, millpond can send an item that asks a question. sounding opens a worktree on the branch sounding/take-mise-2027 and writes question.md. One session works the question there against a 45 minute timebox: it reads the question and the release notes, runs CI on the new version, writes prototype code to try/bump.patch, finds two scripts failing on a renamed flag, and concludes. conclusion.md holds the answer, take mise 2027.1 once two CI scripts pass --locked, its evidence, the work it proposes and what stays open. The card waits on the operator, who accepts it. Prototype code stays on the branch: a sluice submission from sounding/* is refused. sounding one question, one session, one conclusion OPENED FROM your session /sound take mise 2027.1? its own work, going on opened · work goes on or millpond sends an item that asks a question A WORKTREE OF ITS OWN sounding/take-mise-2027 FILES question.md the question, its sources try/bump.patch prototype code conclusion.md the answer Prototype code stays on this branch: a sluice submission from sounding/* is refused. take mise 2027.1? one session · round 1 waiting working concluding ended read question.md read mise 2027.1's notes ran CI on 2027.1 wrote try/bump.patch 2 scripts fail: --frozen 2027.1 calls it --locked sounding conclude timebox 45 min done at 31 of 45 min THE CONCLUSION not yet conclusion.md · round 1 answer Take mise 2027.1 once two CI scripts pass --locked in place of --frozen. evidence both scripts ran on 2027.1 with --locked proposes 2 pieces of work: the scripts, the bump open the Linux runners are untried accept accept go on drop waiting on you: a card, or herdr accepted · its work becomes items 1 Ask from a session, or from an item. 2 One session works it in its own worktree. 3 It ends on a conclusion. 4 You decide: accept, go on or drop.

Why

Section titled “Why”

Some work ends in an answer: whether to take a major release, or how to settle what a meeting left open. Asked inside a session busy with something else, such a question gets a passing answer that nobody decides and nothing records. sounding gives each question a session, a worktree and an end of its own, and you decide the answer.

One question, one place

sounding open writes the question and its sources into a worktree on sounding/<name>. The session may write prototype code there to test an answer, and nothing lands from that branch.

Three exits

The session concludes, offers a finding beyond its question to millpond as a capture, or asks you a question on a card and waits.

Kept to its question

A stop check keeps the session from ending with no conclusion and no note for the next round. A timebox ends each round, and the session concludes with what it knows.

You decide

Accept settles the question, and the work the conclusion proposes becomes items of its own. Go on starts another round with your notes. Drop records why and removes the worktree.

Where it stands

Section titled “Where it stands”

sounding is designed and not built. Its design lives in agentplot/blueprints with the design of every tool around it, and its statement comes next. The roadmap says what gets built in what order.

How it worksThe question and its place, the three exits, the stop check and the timebox, and rounds.
How it fitsmillpond sends it questions and keeps its conclusions, crew calls it, and Flywheel runs its elaborations on it.

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