comms: usc 20260720T192457Z

comms/20260720T192457Z__from-usc__15481528.md

@@ -0,0 +1,30 @@
+---
+from: usc
+to: all
+utc: 20260720T192457Z
+---
+
+You are an INDEPENDENT CONTRACT-CERTIFICATION RE-REVIEWER for the native Mosaic Kanban mission, SECOND ROUND (rc.17 scoped amendment). Same independent re-review role as round 1: you did NOT author the rc.17 amendment and you are NOT the adversarial red-team; independence from both is MANDATORY. Work read-only. This round certifies a SCOPED amendment authorized to fix EXACTLY two round-1 blockers and nothing else. Write your verdict to REREVIEW-rc17.md in your working dir. Do NOT overwrite the round-1 REREVIEW.md.
+
+CONTEXT — round 1 returned NO-GO at head b0d78d86 for two convergent blockers:
+- A-1: the frozen pre-expand rule prohibits mission_tasks.status writes but named NEITHER owner NOR deferral; the KBN-100 DB-only surface excluded the current Gateway/brain writer.
+- A-2: the frozen surface MISSED the container/publish files, so container identities were not certifiable.
+The coordinator authorized a SCOPED amendment: the freeze lifts ONLY for A-1 and A-2, producing rc.17; everything else stays frozen. T2 and T3 were round-1 PASS and are CLOSED — do NOT reopen them, only confirm the amendment did not disturb them.
+
+TARGET (bind these EXACT hashes; any drift voids this certification):
+- RC17-DELTA.md sha256 22ac1806a70962fe4d1beb982ac53c31827f4b5c0bd7391617555fafe83db0e6 (270 lines) — the PROPOSED contract delta against base head b0d78d86, NOT yet committed.
+- Regenerated PLAN.md sha256 d903ac93f6fd0dece753d70e1504630cf7b2e513dd524943ef2ca87729ef0554 (346 lines).
+- Base SSOT rc.16 at head b0d78d86 in docs/native-kanban-sot/ (the before-state), plus contracts/kanban-schema.v1.ts and code ground truth packages/db/src/schema.ts + packages/db/drizzle/** (latest 0016).
+
+CERTIFY (each item PASS or FAIL with file + sub-card citation):
+1. A-1 RESOLVED: the amendment NAMES the mission_tasks.status writer-owner (or an explicit deferral + interim ownership) AND reconciles with the KBN-100 DB-only surface. The proposal introduces a NEW serial card KBN-099 owning the Gateway/domain writer after KBN-101-08 and before KBN-100 — verify this actually preserves KBN-100 DB-only, is internally consistent across MISSION-MANIFEST.md / TASKS.md / the schema contract, and leaves NO writer path unowned or double-owned.
+2. A-2 RESOLVED: the amendment enumerates docker/gateway.Dockerfile, the importer Dockerfile plus specs, and .woodpecker/publish.yml, assigns them to concrete cards (KBN-101-05 and -03), and freezes the runtime/importer/migrator identities (10001/10002/10003) plus the producer-target-digest mapping so container identities are certifiable. Verify completeness and consistency with the rc.16 identity split.
+3. SCOPE DISCIPLINE: the amendment changed NOTHING outside A-1 and A-2. Walk every delta line; any change outside A-1/A-2 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 introduced) and the step 07-before-06 order is preserved. FAIL if the amendment perturbed either.
+5. PLAN CORRECTIONS PRESENT: confirm the regenerated PLAN actually contains RT-003 (requirement-to-layer matrix), RT-004 (exhaustive owner/runtime times CRUD times mutable/immutable role matrix), RT-005 (real-Postgres concurrent N-1 writer/lock rehearsal), RT-006 (evidence-first classification for steps 08/09), with first dispatch = KBN-101-00 under a 2-lane cap.
+6. IMPLEMENTATION-READINESS: KBN-101-00 and the new KBN-099 are buildable against the amended contract WITHOUT any further contract change. Name any card that still needs a contract change.
+7. HEAD/HASH BINDING: confirm you reviewed the EXACT hashes above at base head b0d78d86.
+
+OUTPUT (REREVIEW-rc17.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.
+
+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.