block/buzz: README-based editorial guide

block/buzz describes itself in the README as "A hive mind communication platform". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "What is this, really?", the README says: Buzz is a self-hostable workspace where humans and AI agents share the same rooms.. That establishes the project's stated boundary, not a production test.

The README's "Stuff you do in Buzz" section gives a useful starting point for deciding whether the project fits: Let an agent triage a bug without giving it the keys to the kingdom. Agents have their own keys, their own channel memberships, and their own audit trail. Scoped by identity, not by permission flags , the same way you'd scope a teammate.. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Ask the project a question and get an answer with receipts. Agents search six months of history and post the threads, not vibes.. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "What is this, really?". The source evidence includes: It's a Nostr relay: every message, reaction, workflow step, review approval, and git event is a signed event in one log. Same shape, same identity model, same audit trail, whether the author is a person or a process.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: git clone https://github.com/block/buzz.git && cd buzz . ./bin/activate-hermit # pinned toolchain (tools auto-download on first use) just setup && just build When the README contains no runnable command, this article does not invent one. Open its "Stuff you do in Buzz" section and confirm system dependencies, default ports, and first-run initialization before using a public server.