mosaicstack/stack
1
0
Fork 0
Code Issues 85 Pull Requests Actions Packages Projects Releases 15 Wiki Activity

[EPIC] Comms-evolution: Mosaic-native Matrix layer + MACP standard (RFC-001 + RFC-002) #887

New Issue
Open
opened 2026-07-25 00:43:46 +00:00 by jason.woltje · 1 comment
jason.woltje commented 2026-07-25 00:43:46 +00:00
Owner
Copy Link

Umbrella for the Mosaic Stack comms-evolution program (MS-LEAD lead, under Jason direct authorization; Mos orchestrator). Replaces Hermes-as-backbone with a self-hosted Matrix layer via strangler migration; tmux stays P0.

Design foundation (canonical): RFC-001 (architecture) + RFC-002 (open-source install/config/topology), landed via PR #886 under docs/rfcs/.

Phases (each becomes a mission; acceptance criteria in the RFCs):

  • P1 Presence/availability (first slice; fixes coordinator-dark) — ✅ PR #888 MERGED (dev-validated; live-DEPLOY HELD til Synapse/appservice phase)
  • P2 Native appservice + orchestrator auto-enroll + room provisioning + harness auto-detect
  • P3 MACP v1 spec ratified (framework home)
  • P4 Federation (per-site homeservers, DNS+cert hard-gate, cross-site escalation)
  • P5 Signed-authorship for gate actions + Hermes retired at parity

Key rulings (Jason): Matrix transport (not Nostr/Buzz; adopt Buzz patterns); native Appservice backbone off Hermes; federation requires DNS+cert (IP-only = standalone only); certs via one ACME integration (step-ca or Lets Encrypt); pluggable secret backend (Vaultwarden suggested default, Vault power-user); DB-backed tunable config; server_name immutable.

Linked PRs: #886 (RFC docs) MERGED + #888 (P1 presence) MERGED. P1 landed; deploy held til Synapse/appservice phase; P2-P5 staffed by Mos.

Umbrella for the Mosaic Stack comms-evolution program (MS-LEAD lead, under Jason direct authorization; Mos orchestrator). Replaces Hermes-as-backbone with a self-hosted Matrix layer via strangler migration; tmux stays P0. Design foundation (canonical): RFC-001 (architecture) + RFC-002 (open-source install/config/topology), landed via PR #886 under docs/rfcs/. Phases (each becomes a mission; acceptance criteria in the RFCs): - [x] P1 Presence/availability (first slice; fixes coordinator-dark) — ✅ PR #888 MERGED (dev-validated; live-DEPLOY HELD til Synapse/appservice phase) - P2 Native appservice + orchestrator auto-enroll + room provisioning + harness auto-detect - P3 MACP v1 spec ratified (framework home) - P4 Federation (per-site homeservers, DNS+cert hard-gate, cross-site escalation) - P5 Signed-authorship for gate actions + Hermes retired at parity Key rulings (Jason): Matrix transport (not Nostr/Buzz; adopt Buzz patterns); native Appservice backbone off Hermes; federation requires DNS+cert (IP-only = standalone only); certs via one ACME integration (step-ca or Lets Encrypt); pluggable secret backend (Vaultwarden suggested default, Vault power-user); DB-backed tunable config; server_name immutable. Linked PRs: #886 (RFC docs) MERGED + #888 (P1 presence) MERGED. P1 landed; deploy held til Synapse/appservice phase; P2-P5 staffed by Mos.
jason.woltje commented 2026-07-25 21:12:02 +00:00
Author
Owner
Copy Link

Status update (MS-LEAD, 2026-07-25): P1 is landed. PR #886 (RFC-001/002 docs) MERGED (fabde1c8, id-11 review-15). PR #888 (P1 presence) MERGED (2698ddb7, id-11 review-16). #888 live-DEPLOY remains HELD (Mos-ruled: not actionable until the Synapse/appservice phase stands up a target — revisit then). Next Matrix phases P2→P5 per RFC roadmap, staffed by Mos. Strangler: tmux + mos-comms stay until parity.

**Status update (MS-LEAD, 2026-07-25):** P1 is landed. **PR #886 (RFC-001/002 docs) MERGED** (fabde1c8, id-11 review-15). **PR #888 (P1 presence) MERGED** (2698ddb7, id-11 review-16). **#888 live-DEPLOY remains HELD** (Mos-ruled: not actionable until the Synapse/appservice phase stands up a target — revisit then). Next Matrix phases P2→P5 per RFC roadmap, staffed by Mos. Strangler: tmux + mos-comms stay until parity.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#887
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?