risk-check status is unsatisfiable for the non-numeric worker key seams.md permits #222

New issue

Closed

opened 2026-08-18 20:49:53 +00:00 by john · 1 comment

john commented

2026-08-18 20:49:53 +00:00

Owner

Verified live 2026-08-18: risk-check run --plan 1-fix returns {"ok":false,"reason":"bad-args","detail":"risk-check run --plan needs a plan number after it: --plan <k>"}.

risk-check status derives its plan list from lifecycle brackets, and seams.md explicitly permits a non-role worker key on --bracket-plan ("the worker key when it is not the role name"). Execute.md fix and continuation dispatches need one. Phase 2 of an earlier cycle used 1-fix, 1-cut and 1-cut-b, and status then refused with risk-record-missing for a range that had in fact been checked.

So the two halves of one seam disagree about what a plan key is, and the blocking gate is the thing that cannot be satisfied.

Verified live 2026-08-18: `risk-check run --plan 1-fix` returns `{"ok":false,"reason":"bad-args","detail":"risk-check run --plan needs a plan number after it: --plan <k>"}`. `risk-check status` derives its plan list from lifecycle brackets, and `seams.md` explicitly permits a non-role worker key on `--bracket-plan` ("the worker key when it is not the role name"). Execute.md fix and continuation dispatches need one. Phase 2 of an earlier cycle used `1-fix`, `1-cut` and `1-cut-b`, and status then refused with `risk-record-missing` for a range that had in fact been checked. So the two halves of one seam disagree about what a plan key is, and the blocking gate is the thing that cannot be satisfied.