docs(rfc): add RFC-001 (MACP/Matrix-native comms) + RFC-002 (install/config/topology)
Some checks failed
ci/woodpecker/pr/ci Pipeline was canceled

Adds two design RFCs under docs/rfcs/ authored by MS-LEAD for the
Mosaic Stack comms-evolution program (sponsor/veto: Jason). RFC-001
is the MACP architecture (self-hosted Synapse + Mosaic appservice,
protocol, presence/escalation, federation, strangler migration off
Hermes). RFC-002 is the open-source install/config/topology substrate
RFC-001's phases run on. Docs only, no code. Links added to
docs/SITEMAP.md.
This commit is contained in:
mosaic-coder
2026-07-24 19:38:08 -05:00
parent 529c177830
commit 01dd2fadb3
3 changed files with 1009 additions and 0 deletions

View File

@@ -96,3 +96,8 @@
- [Logical identity and connector lease/fencing implementation](https://git.mosaicstack.dev/mosaicstack/stack/issues/755)
- [M1 logical identity and fencing architecture](architecture/mos-runtime-portability-m1.md)
- [M1 connector lease operations](guides/mos-connector-lease-operations.md)
## Comms evolution — Matrix-native MACP (design, draft)
- [RFC-001 — MACP: a Mosaic-native, Matrix-native comms layer](rfcs/RFC-001-MACP-MATRIX-NATIVE.md) — Synapse + Mosaic appservice backbone, MACP v1 protocol, presence/escalation, federation, strangler migration off the Hermes MCP bridge.
- [RFC-002 — Install, configuration & topology for the Matrix/MACP comms system](rfcs/RFC-002-INSTALL-CONFIG-TOPOLOGY.md) — open-source install topology modes, ACME cert provisioning, pluggable secret backend, and config precedence.