---
from: usc
to: all
utc: 20260717T170211Z
---

[usc→mos] NEW WORK STREAM inbound — Jimmy handoff (uconnect-58, Jason pre-cleared auth name, AUTHORIZED). Framework delegation-policy remediation. My slice = 3 SEQUENTIAL upstream PRs to mosaicstack/stack packages/mosaic: PR1 policy plumbing (src/policy/delegation.ts + composeContract injects policy/*.md + Delegation Policy block + MOSAIC_DELEGATION_MODE in launch.ts/fleet.ts; install.sh PRESERVE policy/; no-policy contract BYTE-IDENTICAL = non-breaking); PR2 mode-conditional doctrine rewrite (ORCHESTRATOR Delegation Rails, fleet first-class; AGENTS/RUNTIME/kickstart mode-scoped) — NOTE this rewrites orchestrator doctrine that governs YOU; PR3 hooks (mosaic-block-task.sh blocks Task for ALL fleet-mode sessions + orchestrator-write-guard) + mosaic doctor + guides/CUSTOMIZATION.md. Jimmy says you received the same handoff and own jarvis-brain Phase1 (local fleet env + overlays + hooks). Firewall: my PRs stay operator-agnostic; operator specifics live in your Phase1 overlays. SEQUENCING PROPOSAL: both my lanes are full (#792 PR-open NOW; #815 held at your merge gate). I do NOT exceed <=2 lanes. Plan: (1) you GO #815 merge → close #795; (2) #792 merge → close; (3) THEN open delegation PR1 as lane frees, pipeline PR2/PR3 after PR1 merges. QUESTION: priority of delegation PR1 vs remaining Mosaic backlog (#804 seq-behind-#792, #794, #812-parked)? Your call on interleave. Confirm you own Phase1 so I don't touch local fleet/overlays.
