roundloop

/roundloop — repeat rounds until the remainder is not self-actionable

Repeats /roundnext until the queue can no longer be advanced by this agent alone. Contract: Constellation.md §13.34. The product of a run is the list of things only a human can decide — not the round count, and not a longer backlog.

Read §13.34 before changing anything here. In particular: registering work is not doing work (§13.34.1), and a round is complete when its board write is measured, not when it is sent (§13.34.3).

0. Preflight — declare the envelope, then read the board

State the caps before the first round, in the opening line of the run: max rounds, the dry-round threshold K (default 2), and any wall-clock or token budget. A cap discovered mid-run is not a cap (§13.34.2-3). If the operator gave a bound ("3 rounds", "until the P2s are gone"), that bound replaces the default and is echoed back.

Then load board truth once (board_state_get, or the board's state.json): planned[] with blocked/blockReason, current[], open decisions[], recent done[].

Register the loop as in-flight work (§13.34.5) so the operator can see it exists and stop it: one current[] entry, id c-roundloop, whose detail line carries the round index and the dry count. Remove it when the loop stops. A loop nobody can see is a loop nobody can interrupt.

1. Loop body — per round

1. Run one round exactly as /roundnext specifies (all five steps, in order). Do not abbreviate the round because it is inside a loop; the blocker re-examination and the new-work scan are what keep later rounds honest.
2. Barrier (§13.34.3): wait for the board write to land, then measure it — worker report received, or a state condition confirmed by reading. Never compute the next round's ripeness from pre-write state. This is the difference between a loop and a race.
3. Score the round against the productivity predicate (§13.34.1):
   • productive ⟸ work was started, or a blocker was cleared with evidence.
   • not productive ⟸ everything else, including a round that registered new planned items, re-sorted the queue, refreshed a blockReason, or wrote a gate. Those are useful; they are not progress. Keep a running ledger: round index, productive?, what made it so, dry-count.
4. Check the guards in order and stop at the first that fires — dry rounds ≥ K · remainder not self-actionable · any cap reached · stall (same item started twice with no done[] delta) · context pressure · operator interrupt. Guards are checked at the round boundary, never mid-round, so the board is never left half-written.