A /boss run whose closing gate (audit / milestone fieldtest) surfaces new
follow-up work no longer stops at a manufactured done-state: the
follow-ups — routed inline or filed onto the tracker — re-enter the queue
and take the direction-freedom test, and the loop continues onto the
autonomously-doable subset. Being discovered after the primary task, or
falling outside the originally discussed scope, is not a stopping reason.
The done-state check gains its two edges everywhere it is stated
(Overview, exit list, Iron Law, Step 1, Step 4, notify state 1):
- closing-gate follow-ups re-enter the queue; primary-task-complete is a
sub-goal, never a done-state;
- a queue of only user-reserved leftovers (idea items, user-reserved
acts) IS a legitimate done-state, named in the notify — while a
remaining design fork stays a bounce-back (triggers 1/4, problem-state
notify), never a done-state wrap-up; when both remain, the bounce
governs.
Plus a rationalisation-table row and a red flag pinning the observed
failure shape (file the fieldtest findings, then declare done).
closes#21
Brummel
52c87d19ce