PH3.2 — Triage: accept, reject, accept-all, pin and rejection locks, E_UNTRIAGED, I_GAP_UNFILLED, I_REJECTED_ELSEWHERE #24

New issue

Open

opened 2026-09-11 09:02:13 +00:00 by bart · 0 comments

bart commented

2026-09-11 09:02:13 +00:00

Collaborator

Parent

Row PH3.2 in docs/12-implementation-plan.md (branch, owned paths and doc section are defined there).

What to build

A planner accepts or rejects each proposed assignment (or accepts all) on a draft; accepts become pin locks, rejects become rejection locks with a reason code, the version enters review, and the validator reports untriaged items, unfilled gaps and jobs rejected elsewhere.

Acceptance criteria

Accept/reject/accept-all endpoints create the right lock rows and audit rows in one transaction
Transition table for draft → review including forbidden moves
Bad-plan fixtures for E_UNTRIAGED, I_GAP_UNFILLED, I_REJECTED_ELSEWHERE each trigger exactly their code
Rejection requires a reason code from the catalogue

Blocked by

#20 — Plan orchestration: snapshot builder, result writer, solver_run/plan_version lifecycle, publish/supersede
#19 — Validator: one rule per E_/W_/I_ code over snapshot and result

## Parent Row **PH3.2** in `docs/12-implementation-plan.md` (branch, owned paths and doc section are defined there). ## What to build A planner accepts or rejects each proposed assignment (or accepts all) on a draft; accepts become pin locks, rejects become rejection locks with a reason code, the version enters `review`, and the validator reports untriaged items, unfilled gaps and jobs rejected elsewhere. ## Acceptance criteria - [ ] Accept/reject/accept-all endpoints create the right lock rows and audit rows in one transaction - [ ] Transition table for draft → review including forbidden moves - [ ] Bad-plan fixtures for `E_UNTRIAGED`, `I_GAP_UNFILLED`, `I_REJECTED_ELSEWHERE` each trigger exactly their code - [ ] Rejection requires a reason code from the catalogue ## Blocked by - #20 — Plan orchestration: snapshot builder, result writer, solver_run/plan_version lifecycle, publish/supersede - #19 — Validator: one rule per E_/W_/I_ code over snapshot and result

bart added the

ready-for-agent

label

2026-09-11 09:02:13 +00:00

bart added a new dependency

2026-09-11 09:02:27 +00:00

#20 T-E — Plan orchestration: snapshot builder, result writer, solver_run/plan_version lifecycle, publish/supersede

bart added a new dependency

2026-09-11 09:02:27 +00:00

#19 T-D — Validator: one rule per E_/W_/I_ code over snapshot and result

bart referenced this issue

2026-09-11 09:02:27 +00:00