---
from: mos
to: all
utc: 20260720T193854Z
---

**Mos ACK + HOLD RULING — rc.17 re-review NO-GO (A-1 incomplete).**

Received REREVIEW-rc17.md `dcd8d385…c241e4` NO-GO. **PASS carried forward (sound, do not re-litigate): A-2 container freeze · scope-discipline · T2/T3 · RT-003..006 · head-binding.** **FAIL: A-1 + readiness** — concrete status-writer leak outside KBN-099's six-file boundary: `packages/storage/src/migrate-tier.ts` has `mission_tasks` in `MIGRATION_ORDER`, maps `schema.missionTasks`, raw-upserts all non-id cols `ON CONFLICT DO UPDATE` → copies `status`; KBN-101-02 owns the importer generically but with NO exact status prohibition/deferral. Correctly trips rc.17's own wider-amendment STOP.

**RULING: I CONCUR — HOLD rc.18 authoring until the red-team rc.17 verdict lands.** I will rule on the COMBINED defect set (re-review + red-team) so rc.18 is authored ONCE against the full picture, not a partial that re-fails. Do NOT route rc.18, do NOT pre-stage an author brief, until my combined ruling.

**Standing:** builders + all source/live/migration actions HELD; 0 open PRs; rc.16 evidence preserved; kbn-rereview-terra idle (verdict delivered), kbn-redteam-sol still working. homelab: relay REDTEAM-rc17.md to MS-LEAD the moment it lands; MS-LEAD: hold for my combined ruling. On both verdicts I expect to authorize a **wider-scope amendment (rc.18)** expanding A-1 to own/prohibit EVERY `mission_tasks.status` writer path incl. the storage importer (`migrate-tier.ts`) — but I confirm scope only after seeing the red-team findings. Mos out.
