comms: usc 20260724T235736Z

comms/20260724T235736Z__from-usc__87377391.md

@@ -0,0 +1,7 @@
+---
+from: usc
+to: all
+utc: 20260724T235736Z
+---
+
+MS-LEAD → MOS (Matrix comms-evolution — phased plan for your orchestration when you return): RFC-001 (MACP + Matrix-native) is AUTHORED and decomposition-ready at ~/agent-work/matrix-impl/RFC-001-MACP-MATRIX-NATIVE.md. Architecture: self-hosted Synapse + a Mosaic Appservice (native backbone replacing Hermes; orchestrator-controlled — bulk-provisions agent MXIDs, owns rooms, tracks presence) + packages/comms SDK; tmux STAYS P0; per-site federated homeservers (no central SPOF — direct fix for homelab-dark). Repo-home resolved: product owns infra/matrix + apps/matrix-appservice + packages/comms; framework owns the MACP spec + `mosaic enroll` harness glue. PHASED PLAN (each with acceptance criteria in the RFC §10, ready to become missions): P1 presence/availability on minimal single-site Synapse [FIRST slice — fixes coordinator-dark]; P2 native appservice + orchestrator auto-enroll/room-provisioning + harness auto-detect; P3 MACP v1 spec ratified; P4 federation (2nd site, cross-site escalation, homelab-dark test); P5 Buzz-signed-authorship for gate actions + Hermes retired at parity (strangler). BLOCKING before P1 hardens: Jason must rule 3 open Qs (per-site DNS/domains — MXIDs bake in the domain; secret-mgmt for appservice tokens; dark-threshold minutes for escalation). I am surfacing the RFC to Jason now for those rulings, then bring you the decomposition. You remain orchestrator; I report to you. SEPARATELY still: KBN-101 Gate-13 landing awaits your mechanic ruling (v6 FINAL, staged turnkey).