You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1bb8b8d
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: ARCHITECTURE.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -561,7 +561,7 @@ Kind 5 (deletion) is intentionally blocked inbound — the relay's deletion hand
561
561
| KIND_REACTION | 7 | Reaction |
562
562
| KIND_DELETION | 5 | Standard NIP-09 deletion |
563
563
564
-
`to_sprout(to_standard(k))`is NOT lossless for secondary mappings (e.g., kind:1 → KIND_STREAM_MESSAGE → kind:42). Translation invalidates Schnorr signatures (event ID includes kind) — proxy re-signs events with shadow keys.
564
+
`to_buzz(to_standard(k))`is NOT lossless for secondary mappings (e.g., kind:1 → KIND_STREAM_MESSAGE → kind:42). Translation invalidates Schnorr signatures (event ID includes kind) — proxy re-signs events with shadow keys.
565
565
566
566
**Dual auth:** Pubkey-based guest registration (persistent, primary) + invite tokens (ad-hoc, time-limited, secondary). Both use NIP-42 for the authentication handshake. The `proxy:submit` scope on the proxy's API token bypasses the relay's pubkey enforcement for shadow-signed events.
Copy file name to clipboardExpand all lines: VISION.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
-
# 🌱 Sprout — The relay is the workspace
1
+
# 🐝 Buzz — The relay is the workspace
2
2
3
3
> An engineer is debugging a production incident at 2am. They type in the incident channel: "What happened last time we saw this error?"
4
4
>
5
5
> An agent watching the channel searches six months of incident history and posts the threads, root causes, and fixes — then offers to page the engineer who deployed the last one.
6
6
7
-
The platform made it possible. The agent made it happen. Sprout is the pipe — event store, search index, subscriptions, delivery — not the brain. Humans and agents bring the intelligence. Sprout gives them a shared space to use it.
7
+
The platform made it possible. The agent made it happen. Buzz is the pipe — event store, search index, subscriptions, delivery — not the brain. Humans and agents bring the intelligence. Buzz gives them a shared space to use it.
8
8
9
-
One relay is your entire workspace. Work, conversation, agents, automation, artifacts, docs — one domain, one identity system, one search index. `myproject.com` in a browser shows your repos. `git clone repoa.myproject.com` works. Open the Sprout app and you're in the channels where the work happens. No GitHub. No Discord. No stitching five services together. The project lives in one place, and that place is yours. See [VISION_SOVEREIGN.md](VISION_SOVEREIGN.md) for the full picture.
9
+
One relay is your entire workspace. Work, conversation, agents, automation, artifacts, docs — one domain, one identity system, one search index. `myproject.com` in a browser shows your repos. `git clone repoa.myproject.com` works. Open the Buzz app and you're in the channels where the work happens. No GitHub. No Discord. No stitching five services together. The project lives in one place, and that place is yours. See [VISION_SOVEREIGN.md](VISION_SOVEREIGN.md) for the full picture.
10
10
11
11
---
12
12
@@ -43,7 +43,7 @@ The relay enforces all access control. Channel membership is the only gate.
43
43
|**DMs**| Participants only | N/A (up to 9) | Any member |
44
44
|**Guests**| Scoped to specific channels | Invited | N/A |
45
45
46
-
Guests (investors, reporters, partners) get a scoped token with membership in specific channels. Same access model as everyone else. Guests can connect with their own Nostr client (Coracle, nak, Amethyst) through [`sprout-proxy`](NOSTR.md), which translates standard NIP-28 events to Sprout's internal protocol. Two auth paths: pubkey-based guest registration (persistent) or invite tokens (ad-hoc, time-limited).
46
+
Guests (investors, reporters, partners) get a scoped token with membership in specific channels. Same access model as everyone else. Guests can connect with their own Nostr client (Coracle, nak, Amethyst) through [`buzz-proxy`](NOSTR.md), which translates standard NIP-28 events to Buzz's internal protocol. Two auth paths: pubkey-based guest registration (persistent) or invite tokens (ad-hoc, time-limited).
47
47
48
48
---
49
49
@@ -60,7 +60,7 @@ content JSON payload
60
60
sig Schnorr signature
61
61
```
62
62
63
-
Sprout extends the standard Nostr event format with custom kind numbers for enterprise features.
63
+
Buzz extends the standard Nostr event format with custom kind numbers for enterprise features.
64
64
65
65
New message type? New kind integer. Zero breaking changes.
66
66
@@ -93,7 +93,7 @@ One model. TLS in transit. At-rest encryption delegated to the storage layer (e.
93
93
94
94
## Huddles
95
95
96
-
Real-time voice runs over a WebSocket Opus relay built into `sprout-relay`. Sprout authenticates participants (NIP-42), admits them to a room, and forwards Opus frames between peers — no external SFU.
96
+
Real-time voice runs over a WebSocket Opus relay built into `buzz-relay`. Buzz authenticates participants (NIP-42), admits them to a room, and forwards Opus frames between peers — no external SFU.
97
97
98
98
- Agents join the same audio relay as humans — they bring their own STT/TTS
@@ -102,7 +102,7 @@ Voice, room lifecycle, and lifecycle events are wired. Recording and per-track p
102
102
103
103
---
104
104
105
-
## Sprout Mesh
105
+
## Buzz Mesh
106
106
107
107
Relay communities can pool opted-in member hardware into shared AI compute. Existing agents see it as a local OpenAI-compatible provider; the relay gates discovery and trust with the same membership model it already uses for messages, code, and workflows. Models too large for any single machine split across several. See [VISION_MESH.md](VISION_MESH.md) for the full compute-commons vision.
108
108
@@ -139,15 +139,15 @@ Beyond chat: channels are workspaces.
139
139
140
140
The relay hosts git repos. Smart HTTP — standard `git clone`, `git push`, nothing special. Your npub signs pushes. Same domain, same auth, same identity as everything else on the relay.
141
141
142
-
Branches are channels. Create a feature branch, Sprout creates a channel — CI results, review comments, and the merge decision all live there. When the branch merges, the channel archives into a permanent record of why that code exists.
142
+
Branches are channels. Create a feature branch, Buzz creates a channel — CI results, review comments, and the merge decision all live there. When the branch merges, the channel archives into a permanent record of why that code exists.
143
143
144
144
See [VISION_PROJECTS.md](VISION_PROJECTS.md) for the full forge vision: the project model, the merge flow, branch protections, and how agents participate as contributors.
145
145
146
146
---
147
147
148
148
## Agent CLI
149
149
150
-
`sprout-cli` is an agent-first CLI that mirrors and extends the MCP surface — same primitives, plus repo, upload, and canvas operations where the CLI is the canonical interface. JSON-only stdout, structured errors on stderr, two-tier auth (NIP-98 keypair → dev pubkey). Agents can script the entire platform without a GUI.
150
+
`buzz-cli` is an agent-first CLI that mirrors and extends the MCP surface — same primitives, plus repo, upload, and canvas operations where the CLI is the canonical interface. JSON-only stdout, structured errors on stderr, two-tier auth (NIP-98 keypair → dev pubkey). Agents can script the entire platform without a GUI.
151
151
152
152
---
153
153
@@ -190,7 +190,7 @@ Not afterthoughts — ship blockers:
190
190
191
191
## Build Model
192
192
193
-
Greenfield. Agent swarms build in parallel, integrating at the event store boundary. Sprout is being built with AI-assisted development — agents write code, crossfire reviews across multiple models catch blind spots before merge. A complete platform, not a collection of independent microservices.
193
+
Greenfield. Agent swarms build in parallel, integrating at the event store boundary. Buzz is being built with AI-assisted development — agents write code, crossfire reviews across multiple models catch blind spots before merge. A complete platform, not a collection of independent microservices.
194
194
195
195
---
196
196
@@ -205,12 +205,12 @@ Greenfield. Agent swarms build in parallel, integrating at the event store bound
205
205
| ✅ | Channel features — messaging, threads, reactions, canvases, media uploads, editing, deletion, typing indicators, NIP-29, soft-delete |
Copy file name to clipboardExpand all lines: VISION_AGENT.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Vision: sprout-agent + sprout-dev-mcp
1
+
# Vision: buzz-agent + buzz-dev-mcp
2
2
3
3
## The Problem
4
4
@@ -10,9 +10,9 @@ We wanted something we could read in an afternoon and audit with confidence.
10
10
11
11
Two binaries, two protocols, no coupling between them.
12
12
13
-
**sprout-agent** is an ACP agent. It speaks the Agent Client Protocol over stdio, calls an LLM, and uses MCP tools. Multiple concurrent sessions, each with its own MCP servers, history, and context. When context fills up, a session summarizes its own history and continues. It works with Zed, JetBrains, sprout-acp, or anything else that speaks ACP.
13
+
**buzz-agent** is an ACP agent. It speaks the Agent Client Protocol over stdio, calls an LLM, and uses MCP tools. Multiple concurrent sessions, each with its own MCP servers, history, and context. When context fills up, a session summarizes its own history and continues. It works with Zed, JetBrains, buzz-acp, or anything else that speaks ACP.
14
14
15
-
**sprout-dev-mcp** is an MCP server. It gives any agent a shell and a file editor. Ephemeral processes with process-group kill on every exit path. Bounded output. File edits resolve against the working directory. It works with any agent or client that speaks MCP.
15
+
**buzz-dev-mcp** is an MCP server. It gives any agent a shell and a file editor. Ephemeral processes with process-group kill on every exit path. Bounded output. File edits resolve against the working directory. It works with any agent or client that speaks MCP.
16
16
17
17
Together: two crates of Rust purpose-built for headless autonomous coding work.
18
18
@@ -22,20 +22,20 @@ Together: two crates of Rust purpose-built for headless autonomous coding work.
22
22
23
23
**Correctness at the boundary.** ACP compliance is not a checkbox. We report a concrete protocol version. We emit every required notification. We handle cancellation on every path. We kill process trees on timeout. Key safety properties have regression tests that lock them down.
24
24
25
-
**Composability through standards.** The agent does not know what MCP server it talks to. The MCP server does not know what agent is calling it. They compose through protocols, not imports. Run ten agents behind sprout with different MCP configurations. Swap the LLM provider with one environment variable. Point Zed at sprout-agent and you get the same tool-calling behavior in your editor.
25
+
**Composability through standards.** The agent does not know what MCP server it talks to. The MCP server does not know what agent is calling it. They compose through protocols, not imports. Run ten agents behind Buzz with different MCP configurations. Swap the LLM provider with one environment variable. Point Zed at buzz-agent and you get the same tool-calling behavior in your editor.
26
26
27
27
## The Architecture
28
28
29
29
```
30
-
Any ACP client (Zed, JetBrains, sprout-acp, custom)
30
+
Any ACP client (Zed, JetBrains, buzz-acp, custom)
31
31
|
32
32
| stdio ACP (JSON-RPC 2.0)
33
33
v
34
-
sprout-agent (up to 8 concurrent sessions)
34
+
buzz-agent (up to 8 concurrent sessions)
35
35
|
36
36
| stdio MCP (JSON-RPC 2.0) — one per session
37
37
v
38
-
sprout-dev-mcp (or any MCP server)
38
+
buzz-dev-mcp (or any MCP server)
39
39
|
40
40
v
41
41
shell, str_replace, todo; rg + tree on PATH
@@ -56,7 +56,7 @@ Two pipes. Two protocols. Each session gets its own MCP server instances — ful
56
56
## What This Enables
57
57
58
58
- Multiple concurrent sessions in one process — each with independent MCP servers, history, and context (configurable cap, default 8)
59
-
- Ten agents in parallel behind sprout, each with their own MCP configuration
59
+
- Ten agents in parallel behind Buzz, each with their own MCP configuration
60
60
- Any ACP client gets a coding agent without a custom adapter
61
61
- Any MCP server gets a capable caller without a custom adapter
62
62
- A codebase small enough to fork, modify, and understand in a day — two crates, no coupling between them
0 commit comments