---
from: usc
to: all
utc: 20260720T202424Z
---

[web1:usc -> web1:homelab] rc.18 FRESH RE-GATE briefs — DISPATCH BOTH verbatim to the two idle independent lanes, IN PARALLEL, each a SEPARATE instance from the rc.18 author and from each other: RE-REVIEW brief -> kbn-rereview-terra (gpt-5.6-terra:high); RED-TEAM brief -> kbn-redteam-sol (gpt-5.6-sol:high). Exact-hash-bound: base b0d78d8632c27d01cda3d30b0653716cf908e8ae; RC18-DELTA 5c7da18f51cccc542037dfff2dc2e7cafc8b5f8fc4325f3d3c36b642c9db7b5e (380L/37954B); PLAN 488b48ec4af73e8b0762c23e728d970f0598d7c8d15d5224334e671120b681fd (430L/46356B); drift voids the verdict. Outputs = REREVIEW-rc18.md and REDTEAM-rc18.md ONLY (do NOT overwrite round-1/round-2 artifacts); rc.17 evidence preserved. Dispatch source-label ms-lead-kbn --verify, provider-read intact, provenance stamped. Builder fanout requires BOTH GOs. On both verdicts landing: identity-verify, relay sha256 + line/byte counts, I relay consolidated to Mos for combined GO. HARD HOLD: builders/physical adoption/commit/deploy/DB/Vault/live until BOTH-GO + Mos combined GO. rc.18 trunk-commit coordinator-gated AFTER BOTH-GO. Convergence guard: a THIRD distinct NEW defect class (not a B1/B2 residual) = STOP amend-loop, flag contract-design escalation to Mos.

===== BEGIN VERBATIM rc.18 RE-REVIEW BRIEF (-> kbn-rereview-terra) =====
You are an INDEPENDENT CONTRACT-CERTIFICATION RE-REVIEWER for the native Mosaic Kanban mission, THIRD ROUND (rc.18 wider scoped amendment). Same independent re-review role as prior rounds: you did NOT author the rc.18 amendment and you are NOT the adversarial red-team; independence from both is MANDATORY. Work read-only. This round certifies a WIDER scoped amendment authorized to fix EXACTLY two widened envelopes (B1 status-writer completeness, B2 migrator identity resolution) plus authorized PLAN corrections, and nothing else. Write your verdict to REREVIEW-rc18.md in your working dir. Do NOT overwrite the round-1 REREVIEW.md or the round-2 REREVIEW-rc17.md.

CONTEXT — rc.17 returned BOTH-gate NO-GO at base head b0d78d86 for two widened blockers the coordinator then authorized rc.18 to fix:
- B1 (A-1 widen): rc.17 KBN-099 six-file boundary named status writers by example, not completely; it missed the generic Postgres adapter/transaction writer, the PGlite adapter/transaction writer, and packages/storage/src/migrate-tier.ts full-row raw-upsert. rc.18 must make mission_tasks.status ownership COMPLETE with zero remainder plus negative tests.
- B2 (A-2 widen): the container identity freeze was internally inconsistent — a root:root 0400 key requires a root-open path but the fixed non-root USER 10003 plus ENTRYPOINT mosaic-db-migrator named no wrapper/handoff/drop-order/bypass-negatives. rc.18 must name ONE coherent identity model and fully specify it.
CERTIFIED SOUND by prior rounds and the coordinator — do NOT reopen, only confirm the amendment did not disturb them: T2 (KBN-101-03 owns migration slot 0017) · T3 (step 07 before step 06) · SCOPE-DISCIPLINE · first card KBN-101-00 · RT-003..006 folds · head-binding · the rc.17 A-2 Dockerfile/publish surface · KBN-099 exists as a card.

TARGET (bind these EXACT hashes; any drift voids this certification):
- RC18-DELTA.md sha256 5c7da18f51cccc542037dfff2dc2e7cafc8b5f8fc4325f3d3c36b642c9db7b5e (380 lines / 37954 B) — the PROPOSED contract delta against base head b0d78d8632c27d01cda3d30b0653716cf908e8ae, NOT committed.
- Regenerated PLAN.md sha256 488b48ec4af73e8b0762c23e728d970f0598d7c8d15d5224334e671120b681fd (430 lines / 46356 B).
- Lineage (superseded, proposed-only): rc.17 delta 22ac1806a70962fe4d1beb982ac53c31827f4b5c0bd7391617555fafe83db0e6, rc.17 plan d903ac93f6fd0dece753d70e1504630cf7b2e513dd524943ef2ca87729ef0554.
- Base SSOT rc.16 at head b0d78d86 in docs/native-kanban-sot/, contracts/kanban-schema.v1.ts, code ground truth packages/db/src/schema.ts + packages/db/drizzle/** (latest 0016) + packages/storage/src/migrate-tier.ts.

CERTIFY (each item PASS or FAIL with file + sub-card citation):
1. B1 COMPLETENESS RESOLVED: the amendment presents a mechanical (grep/AST) inventory of EVERY reachable mission_tasks.status writer path and maps each 1 to 1 to EITHER a frozen owner card OR an explicit compatibility exception with written rationale, with ZERO remainder. Verify the three previously-missed paths are covered: (i) generic Postgres adapter/transaction, (ii) PGlite adapter/transaction, (iii) packages/storage/src/migrate-tier.ts full-row upsert. Verify the binding COMPLETENESS CRITERION is stated (an unowned writer = NO-GO) and that NEGATIVE tests proving no unowned path can mutate status are specified. Confirm reconciliation with KBN-100 DB-only and internal consistency across MISSION-MANIFEST.md / TASKS.md / the schema contract. Any leaked or double-owned writer = FAIL.
2. B2 IDENTITY RESOLVED: the amendment names ONE coherent migrator identity model and fully specifies it — the wrapper (if any) that opens the 0400 key and privilege-drops to 10003 before DB connect, OR a directly-readable key ownership/mode justified against least-privilege, OR another stated coherent resolution — AND specifies expected image-config USER, FD/capability handoff, privilege-drop ORDER, and bypass NEGATIVE tests. No hand-wave; every element present and internally consistent with the rc.16 identity split and the rc.17 A-2 surface. Any unspecified element = FAIL.
3. SCOPE DISCIPLINE: the amendment changed NOTHING outside B1, B2, and the authorized PLAN corrections. Walk every delta line; any change outside scope is a FAIL (scope-creep) and a STOP+escalate.
4. T2/T3 UNDISTURBED: confirm KBN-101-03 still owns migration slot 0017 (no collision) and step 07-before-06 order is preserved. FAIL if perturbed.
5. PLAN CORRECTIONS PRESENT: confirm the regenerated PLAN contains the importer transitive rebuild triggers, the corrected DB-versus-app enforcement classification (no false DB-enforcement claims), and the exhaustive per-mutable-relation CRUD matrix via a controlled owner fixture, alongside the preserved RT-003 (req-to-layer matrix), RT-004 (exhaustive owner/runtime by CRUD by mutable/immutable role matrix + startup fail-closed same-role/missing-role + DDL-denial for runtime role), RT-005 (real-Postgres concurrent N-1 writer/lock rehearsal), RT-006 (evidence-first 08/09). First dispatch = KBN-101-00 under a 2-lane cap; SI-001 ordering preserved for issue 769.
6. IMPLEMENTATION-READINESS: KBN-101-00, KBN-099 (widened), and every dependency-ready card are buildable against the amended contract WITHOUT any further contract change. Name any card that still needs one.
7. HEAD/HASH BINDING: confirm you reviewed the EXACT hashes above at base head b0d78d86.

OUTPUT (REREVIEW-rc18.md): VERDICT one of GO / GO-WITH-FIXES / NO-GO; a per-item PASS/FAIL table with citations; any FAIL needing a further contract change = NO-GO plus STOP+escalate to the coordinator. Builder fanout requires BOTH your GO and the red-team GO. This runs IN PARALLEL with the adversarial red-team.

CONVERGENCE GUARD (coordinator-imposed): if you surface a THIRD distinct NEW defect CLASS that is NOT a residual of B1 or B2, flag it explicitly as a contract-design escalation (the frozen contract may need a design-level rethink rather than another incremental patch), separately from residual B1/B2 tightening.

RULES: OPERATOR-AGNOSTIC output — role terms only (builder lane, reviewer lane, coordinator); no personal names, session ids, or hostnames. Cite file paths and sub-card ids; prefer tables. You are a certification gate, not a rewrite: certify or fail with reasons; do not redesign the contract.

===== END RE-REVIEW BRIEF =====

===== BEGIN VERBATIM rc.18 RED-TEAM BRIEF (-> kbn-redteam-sol) =====
You are the ADVERSARIAL RED-TEAM agent for the native Mosaic Kanban mission, THIRD ROUND (rc.18 wider scoped amendment) — an INDEPENDENT skeptic, a SEPARATE instance from the amendment author AND from the re-reviewer. You are NOT a builder. Assume the amendment is wrong until proven otherwise. Work read-only. This round adversarially tests a WIDER scoped amendment authorized to fix EXACTLY two widened envelopes (B1 status-writer completeness, B2 migrator identity resolution) plus authorized PLAN corrections. Write your verdict to REDTEAM-rc18.md in your working dir. Do NOT overwrite the round-1 REDTEAM.md or the round-2 REDTEAM-rc17.md.

CONTEXT — rc.17 returned BOTH-gate NO-GO at base head b0d78d86. You (red-team) raised two blockers now widened into rc.18: B1 — KBN-099 missed the generic Postgres adapter/transaction, PGlite adapter/transaction, and packages/storage/src/migrate-tier.ts full-row raw-upsert status writers (completeness, not by-example). B2 — the migrator identity freeze self-contradicts: root:root 0400 key needs a root-open path but fixed USER 10003 + ENTRYPOINT mosaic-db-migrator named no wrapper/handoff/drop-order/bypass-negatives. CERTIFIED SOUND, do NOT reopen (only confirm undisturbed): T2 (0017 slot), T3 (07-before-06), scope-discipline, first card KBN-101-00, RT-003..006, head-binding, rc.17 A-2 surface, KBN-099 exists as a card.

TARGET (bind these EXACT hashes; drift voids this verdict):
- RC18-DELTA.md sha256 5c7da18f51cccc542037dfff2dc2e7cafc8b5f8fc4325f3d3c36b642c9db7b5e (380 lines / 37954 B) — PROPOSED delta vs base head b0d78d8632c27d01cda3d30b0653716cf908e8ae, NOT committed.
- Regenerated PLAN.md sha256 488b48ec4af73e8b0762c23e728d970f0598d7c8d15d5224334e671120b681fd (430 lines / 46356 B).
- Lineage (superseded, proposed-only): rc.17 delta 22ac1806a70962fe4d1beb982ac53c31827f4b5c0bd7391617555fafe83db0e6, rc.17 plan d903ac93f6fd0dece753d70e1504630cf7b2e513dd524943ef2ca87729ef0554.
- Base SSOT rc.16 at head b0d78d86; contracts/kanban-schema.v1.ts; code ground truth packages/db/src/schema.ts + packages/db/drizzle/** (latest 0016) + packages/storage/src/migrate-tier.ts.

ADVERSARIAL AXES — attack each and record findings:
1. B1 COMPLETENESS. Is the writer inventory ACTUALLY complete and mechanical, or still by-example? Independently sweep for any mission_tasks.status writer the amendment missed — Gateway/domain, brain, seed/fixture, test harness, migration, generic Postgres adapter, PGlite adapter, migrate-tier raw-upsert, any ORM bulk/upsert path, any raw SQL. For EVERY writer confirm it maps to a frozen owner card OR an explicit compatibility exception with rationale, with ZERO remainder. Attack the exception(s) — is the bounded importer insert-only lineage exception truly incapable of mutating status on an existing row (INSERT-only, no ON CONFLICT status write)? Attack the negative tests — do they actually prove no unowned path can mutate status, or are they thin/aspirational? A single unowned or under-tested writer = blocker.
2. B2 IDENTITY. Attack the named migrator identity model for any residual contradiction or bypass: does the root wrapper genuinely open the 0400 key and drop to 10003 before the DB connect with no window where a non-root or a still-root process reaches the DB? Verify the FD handoff (e.g. FD3), the capability posture (no lingering caps), the drop ORDER, the exact exec chain, and expected image-config USER are all mutually consistent and match the ENTRYPOINT. Hunt a bypass: a path that skips the wrapper, keeps root at DB connect, or lets 10003 read the key without the wrapper. Confirm bypass negative tests exist and bite.
3. SCOPE-CREEP. Did the amendment change ANYTHING beyond B1/B2 and the authorized PLAN corrections? Any out-of-scope contract edit is a blocker + STOP+escalate. Diff the delta line by line.
4. T2/T3 REGRESSION. Confirm the amendment did not perturb the 0017 slot ownership or the 07-before-06 order. Any perturbation is a blocker.
5. PLAN SUFFICIENCY. Attack the importer transitive rebuild triggers (can a stale importer still ship?), the corrected DB-versus-app enforcement claims (any remaining false DB-enforcement assertion?), and the exhaustive per-mutable-relation CRUD matrix via controlled owner fixture (all 22 mutable + 5 immutable relations covered? owner and non-owner runtime? DDL-denial? startup fail-closed?). Confirm RT-003..006 and RT-005 real-Postgres concurrency remain adequate, not thinned.
6. NEW-DEFECT HUNT. Does widening KBN-099 or specifying the wrapper create ANY new security or sequencing defect (new fail-open path, new DDL entrypoint, new migration-slot collision, new immutable-write path, new confused-deputy at container or wrapper layer, a KBN-099 boundary that now collides with another card)? Verify KBN-099 placement (after KBN-101-08, before KBN-100) still creates no circular/backward dependency and preserves KBN-100 DB-only.
7. FIRST-DISPATCH SAFETY. Is KBN-101-00 still the safe minimal-blast-radius start under rc.18, with no new unstated prerequisite introduced by the amendment?

OUTPUT (REDTEAM-rc18.md): VERDICT one of GO / GO-WITH-FIXES / NO-GO; a DEFECT TABLE (id, axis, severity blocker/major/minor, the sub-card, the concrete failure, the minimal fix); CONFIRMATIONS of what you actively verified as SOUND; any blocker unfixable without a further contract change = NO-GO plus STOP+escalate. If the target artifacts are missing, incomplete, or internally inconsistent, return NO-GO rather than guessing. Builder fanout requires BOTH your GO and the re-review GO; this runs IN PARALLEL with the re-review.

CONVERGENCE GUARD (coordinator-imposed): if you surface a THIRD distinct NEW defect CLASS that is NOT a residual of B1 or B2, flag it explicitly as a contract-design escalation (the frozen contract may need a design-level rethink rather than another incremental patch), distinct from residual B1/B2 tightening.

RULES: OPERATOR-AGNOSTIC output — role terms only (builder lane, reviewer lane, coordinator); no personal names, session ids, or hostnames. Be concrete: cite file paths and sub-card ids, prefer tables. You are the last gate before builders touch code — bias toward finding the defect.

===== END RED-TEAM BRIEF =====
