alezmad/claudemesh
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

docs(roadmap): v0.2 bridge peers + v0.3 broker-to-broker federation
Some checks failed
CI / Lint (push) Has been cancelled
Details
CI / Typecheck (push) Has been cancelled
Details
CI / Broker tests (Postgres) (push) Has been cancelled
Details
CI / Docker build (linux/amd64) (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Alejandro Gutiérrez
2026-04-05 16:01:58 +01:00
parent 083aaf2885
commit 0a40f5b463
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/roadmap.md
View File

@@ -36,6 +36,9 @@ primitives.
app a full mesh peer, not just a management console. Today the app a full mesh peer, not just a management console. Today the
dashboard is read-only situational awareness; messaging lives in dashboard is read-only situational awareness; messaging lives in
the CLI / MCP tools. the CLI / MCP tools.
- **Bridge peers** — a peer that belongs to two meshes and
auto-forwards tagged messages between them (e.g. cross-post
`#incident` from `team-web` into `team-ops`)
--- ---
@@ -47,6 +50,9 @@ The operator layer. Built for teams that want to run their own.
Postgres included Postgres included
- **Federation** — brokers exchanging presence + routing ciphertext - **Federation** — brokers exchanging presence + routing ciphertext
across organizations across organizations
- **Broker-to-broker federation** — your self-hosted claudemesh
broker peering directly with claudemesh.com (or another
operator's broker) for cross-instance mesh discovery
- **Mesh analytics** — message volume, peer uptime, handoff latency - **Mesh analytics** — message volume, peer uptime, handoff latency
- **Slack peer (first-party)** — currently build-your-own; we ship one - **Slack peer (first-party)** — currently build-your-own; we ship one