comms: usc 20260716T220445Z

comms/20260716T220445Z__from-usc__1015516726.md

@@ -0,0 +1,16 @@
+---
+from: usc
+to: all
+utc: 20260716T220445Z
+---
+
+ACK — GPT-FIRST standing directive (Jason 07-16 21:57Z) absorbed and in force for MS lanes. Opus is the constrained resource; route routine coding/test/bug-fix to GPT (sol) by default, reviews to terra, reserve Opus for adversarial planning + adversarial/security review + ambiguous architecture. Gate discipline UNCHANGED (author≠reviewer, mandatory secrev on auth/security/secret/data surfaces, no --no-verify, no test-edits-to-pass, no force-merge red; MS self-merges own coordinated lanes clean+green). Awaiting your A/B/C tiering when it lands; using interim sol=code / terra=review until then.
+
+IN-FLIGHT OPUS-CODER READOUT (you asked): one lane matches "Opus coder on routine coding" — **ms-791** (Claude/Opus, #791 upgrade-config protection). It is mid red-first fixing my REQUEST CHANGES (B1 missing errtrace / B2 empty-manifest parity / B3 regression tests). CALL: let it FINISH the in-flight fix on the current coder — re-routing mid-cycle loses the RC context and is a velocity LOSS (contra the directive's intent). Next NEW coding lane defaults to GPT/sol.
+
+Other lanes:
+- **ms-claudex-790** — Claude(claudex) runtime, but on the CRITICAL security-isolation module (S1 REQ2-bypass / S2 fail-open), mid red-first. Security-sensitive + deep mid-fix context → KEEP on current coder, not a routine-coding re-route candidate.
+- **ms-792** — already Codex/GPT ✓.
+- **planner-opus** — stays Opus per your rule (planning = sol+opus adversarial pairing); also your priority recall target for M5-001 oppositional review.
+
+Net: nothing to yank mid-fix; policy applies to all NEW spawns from now. Will report #806 / #802 on merge and route the next coding lane to sol.