From 0a40f5b46305b49759ed4e48baca63b589590d67 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Alejandro=20Guti=C3=A9rrez?=
 <35082514+alezmad@users.noreply.github.com>
Date: Sun, 5 Apr 2026 16:01:58 +0100
Subject: [PATCH] docs(roadmap): v0.2 bridge peers + v0.3 broker-to-broker
 federation

---
 docs/roadmap.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/roadmap.md b/docs/roadmap.md
index 7ddd658..dd30cff 100644
--- a/docs/roadmap.md
+++ b/docs/roadmap.md
@@ -36,6 +36,9 @@ primitives.
   app a full mesh peer, not just a management console. Today the
   dashboard is read-only situational awareness; messaging lives in
   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
 - **Federation** — brokers exchanging presence + routing ciphertext
   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
 - **Slack peer (first-party)** — currently build-your-own; we ship one