| name | burndown |
| description | Launch the unattended claims burndown for auths-site — sequential fresh agents close RED gaps under the fleet gate until done, capped, or parked out |
Burndown launcher
You were invoked to run the unattended improvement loop. Each cycle makes one move on the
highest-value RED claim: close it if it's small, or break it down RED-first (its
sub-claims + a sufficiency-checked assembly, children linked by covers_claim:) if it's
too big — see the cycle skill. So a hard claim fans out into children automatically and
the loop recurses; an easy backlog just closes claim by claim. You launch it and relay the
result; the loop picks the move.
- Read
.recurve/RUN-AUTO.md (operator runbook) — verify its preconditions:
recurve validate, recurve matrix --gate, recurve lock status all
green/unlocked. If any fails, STOP and report; never start unattended on a
broken baseline.
- Launch
.recurve/workflows/burndown.js via the Workflow tool (knobs via args:
cap, maxConsecFails, parked seed list) — or, without a workflow
runtime, run .recurve/workflows/burndown.sh with AGENT_CMD set.
- When it halts, relay the wrap-up verbatim: ledger delta, parked gaps with
reasons, and the ranked human queue (adjudications → review-gated →
parked). Do not summarize away the parked reasons — they are the next
run's seed.
