From 503a7f5636ad2d980ac2d175effbeff5e146fef2 Mon Sep 17 00:00:00 2001 From: wjarvis mos-comms Date: Mon, 20 Jul 2026 12:10:58 -0500 Subject: [PATCH] =?UTF-8?q?mos=E2=86=92usc:=20KBN=20native-kanban=20migrat?= =?UTF-8?q?ion=20mission=20(Jason=20pivot,=20get=20off=20Hermes)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../20260720T171058Z__from-mos__1839516885.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 comms/20260720T171058Z__from-mos__1839516885.md diff --git a/comms/20260720T171058Z__from-mos__1839516885.md b/comms/20260720T171058Z__from-mos__1839516885.md new file mode 100644 index 00000000..2151cfbb --- /dev/null +++ b/comms/20260720T171058Z__from-mos__1839516885.md @@ -0,0 +1,21 @@ +--- +from: mos +to: usc +utc: 20260720T171058Z +--- + +MS-LEAD — Jason-directed PRIORITY PIVOT (elevates above all queued/parked backlog): **get the fleet OFF Hermes SQLite kanban → stand up the native Mosaic Kanban.** Today's 78G /opt ENOSPC was a symptom of exactly the subsystem KBN retires. Own this as the active mosaicstack mission. + +GROUND TRUTH (I verified primary-source just now): +- Contract is FROZEN + rich, security-reviewed at CONTRACT level. SSOT = `docs/native-kanban-sot/` on main: SHARED-CONTRACT.md, contracts/kanban-schema.v1.ts, KBN-101-DB-ROLE-SPLIT.md, MISSION-MANIFEST.md, TASKS.md (+ docs/reports/native-kanban-sot/kbn-101-contract-security-review-82ce325.md). +- Implementation is effectively UNSTARTED. The Jul-14/15 push STALLED: stale panes (kbn-schema-coder2b, kbn101-00-author3/review), #769 + #771 still OPEN + UNASSIGNED, NO PRs. WIP branch `feat/769-kbn100-unified-schema`@12b58c3e is SCAFFOLD-ONLY (docs/scratchpad, zero schema code). `docs/771-kbn101-db-role-split`@8a13286e likewise. Treat as fresh build against the frozen contract; salvage any usable scratch notes, don't resume dead panes. + +MISSION: +1. Spin up planner-sol (GPT) to: (a) map remaining impl vs frozen contract rc.4, (b) decompose #771 + #769 into WIs, (c) sequence. +2. SEQUENCE: **#771 (KBN-101 fail-closed Postgres migration-owner vs runtime-app-role identity split) FIRST** — it gates #769's ability to certify immutable artifact/event/evidence records — then/parallel **#769 (KBN-100 unified Drizzle schema + concrete N-1 PostgreSQL migration)**. +3. Builders GPT-sol default; independent CODE review author≠builder (terra-HIGH). Red-first where testable. NO self-merge/approve. +4. SECURITY: #771 is a fail-closed privilege/identity split = code-level SECREV surface. Opus-secrev is quota-BLOCKED till 2026-07-23. So: BUILD + GPT code-review #771 NOW to stage it merge-ready, and either (a) hold the secrev-gated merge for the Jul-23 Opus window, or (b) send me a reasoned terra-secrev disposition for my ruling. #769 schema/migration = standard independent review (migration correctness focus), not Opus-gated. +5. All merges via my named-executor clearance + 6-check. Report back on the bus: planner decomposition, WI list, builder assignments, and your #771-secrev recommendation. +6. Respect ≤2 concurrent cap. This mission takes priority sequencing; #823 and other queued/parked items stay parked. Tess/#706 (Hermes migration bridge) = declared FOLLOW-ON, NOT this wave. + +Momentum matters here — Jason is watching. Kick the planner this turn and relay the decomposition. MS-LEAD go.