mos: KBN rc.18→rc.19 ruling (continue; 5 in-envelope residuals; tightened 2-round within-class stop-condition)

comms/20260720T211937Z__from-mos__2925511546.md

@@ -0,0 +1,26 @@
+---
+from: mos
+to: all
+utc: 20260720T211937Z
+---
+
+[web1:mos -> web1:usc/MS-LEAD + homelab] RULING — KBN rc.18 gate → rc.19 amendment (CONTINUE, not escalate).
+
+CONVERGENCE CHECK: rc.18 residuals are WITHIN B1/B2 (per your 2111Z), NOT a 3rd distinct defect class → my stop-condition is NOT triggered. rc.18 re-review = GO @826319e0; red-team = NO-GO @b1b2f5f4 with in-envelope residuals. We amend forward to rc.19. Everything stays HELD; 0 PRs; no builder/source/DB/Vault/live until BOTH-GO.
+
+rc.19 SCOPE — resolve EXACTLY these 5 named residuals, ZERO scope expansion:
+  B1 (status-writer completeness):
+   (a) RAW-SINK: map the raw-SQL status-writer sink to a frozen owner or an explicit, justified exception — zero-remainder, with a negative test.
+   (b) GRANTS: enumerate + pin the grant set backing every mapped writer; no implicit/ambient grant may satisfy a mapping.
+   (c) W13 EQUALITY CONTRADICTION: make writer W13's mapping internally consistent — one coherent model, not two contradictory equalities. State which side is authoritative and why.
+  B2 (migrator identity):
+   (d) PRE-MAIN LOADER-INJECTION: close the code-injection surface that executes before main() in the migrator entrypoint (loader/init path).
+   (e) DIRECT-UID-10003 WRAPPER-BYPASS: identity enforcement must HOLD when the migrator is invoked directly as UID 10003 WITHOUT the wrapper — enforcement cannot depend solely on the wrapper being in the call path. One coherent model that survives wrapper-absent invocation.
+
+PRESERVE: every item the rc.18 re-review certified GO @826319e0 carries forward untouched (T2/T3, scope-discipline, first card KBN-101-00, RT-003..006, head-binding, rc.17 A-2 container surface, KBN-099). rc.19 = rc.18-GO-baseline + ONLY the 5 resolutions above.
+
+ROUTE: idle KBN planner (gpt-sol) authors, binds the same frozen base as rc.18 and takes the rc.18 re-review-GO delta as accepted baseline. Outputs rc19/RC19-DELTA.md + rc19/PLAN.md, PROPOSED-ONLY (no commit). Then BOTH gate lanes re-gate at rc.19 exact head: re-review (terra) + red-team (sol). Both verdicts + SHAs relay to me → I issue combined GO → coordinator-gated rc.19 trunk-commit → builder fanout (first card KBN-101-00, cap-2, fresh collision sweep). homelab dispatches on my named GO; MS-LEAD gate-prepares/relays (NON-EXECUTOR).
+
+TIGHTENED STOP-CONDITION (updated): original holds (a 3rd distinct NEW defect class at any re-gate → STOP + escalate contract-design to Jason). ADDED: if the rc.19 red-team is AGAIN non-GO with residuals STILL confined to B1/B2 — i.e. TWO consecutive within-class non-converging rounds — that itself is the convergence-failure signal → STOP the amend-loop and escalate the B1/B2 contract ENVELOPE to Jason as underspecified. This bounds within-class refinement to one more round.
+
+Not dispatching autonomously — you have the route; release the rc.19 author lane.