ThesisBuzz: The Open Source Workspace Where Humans & AI Build Together teaches a practical agent architecture move: This video introduces Buzz, Block's Apache-2.0, Rust, Nostr-based self-hostable workspace where humans and AI agents collaborate on a relay you own, unifying chat, code, docs, issues, and automation into one signed event log; it covers the seven surfaces, the relay-centric architecture, and how agents act as first-class members with their own keys and audit trail.
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
0:00One signed event log
“Buzz, a hive-mind communication platform from Block, the company behind Square and Cash App. It's a self-hostable workspace where humans and AI agents build together on a relay you own. Every message, every reaction, every workflow step is...”
Buzz, from Block (Square, Cash App), replaces the usual seven-tab stack (Discord, GitHub, Notion, Linear, CI, Slack) with one domain, one identity, and one event log, built on Nostr where every action is a signed event of six fields (id, public key, kind number, tags, content, signature) and humans and agents share the same format with different key pairs, so trust lives in the protocol. List the tools your team currently glues together and map each to the single Buzz surface (stream, forum, DMs, agents, workflows, search) that would absorb it.
5:05Relay-centric architecture
“edits resolve against the working directory. Agent personas bundle a model and a system prompt. A team is a named group of personas. Ralph for code review, Scout for research, Reviewer for crossfire verification. Built-in personas ship with...”
The relay is the single source of truth (Axum + Rust), verifying signatures, persisting events to Postgres, fanning out via Redis pub/sub, indexing for search, triggering workflows, and serving Git repos over websocket; crates layer up from zero-I/O BuzzCore through BuzzDB, BuzzAuth, BuzzPubSub, BuzzSearch, and BuzzWorkflow to BuzzRelay, kind numbers (custom kinds start at 40,000) are the only dispatch switch, and a hash-chain audit log makes every action tamper-evident without blockchain. Draw the request path of a single message through the relay (verify signature, Postgres, Redis fan-out, search index, workflow trigger) and note why a new feature just means a new kind number.
8:27Agents as members
“visible compromise in isolation. The road ahead. The vision is sovereign. Your project at your domain. Code lives there. Conversation lives there. Agents connect to it. Automation flows through it. Artifacts publish from it. The relay is the...”
In Buzz, agents are members not bots, each with their own keys, channel memberships, and audit trail, scoped by identity like a teammate; Buzz Agent is a Rust ACP agent speaking over stdio, calling an LLM, and using MCP tools with per-session context that summarizes when full, Buzz Dev MCP gives any agent a sandboxed shell and file editor, and personas/teams (Ralph for review, Scout for research, Reviewer for crossfire) plus branches-as-channels and NIP-34 patches put agent work in the same room as the evidence. Define one agent persona (model plus system prompt) and describe how it would join a feature-branch channel and post a first-pass code review alongside teammates.
ExampleSource-backed work packet
Convert the video into a scoped task that includes the transcript claim, target workflow, acceptance criteria, and proof. The output should be a one-page agent harness map with tool boundaries and proof signals..
ExampleClaim vs. demo brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the workflow.
ExampleTeach-back module
Transform the lesson into a definition, a mechanism diagram, one misconception, one practice exercise, and a check-for-understanding question.