Buzz is a self-hostable, open-source collaborative workspace designed to integrate human team members, AI agents, and automated workflows within a unified, relay-based event architecture. Built by Block, Inc., the system utilizes the Nostr protocol as its core communication substrate, treating every action—ranging from chat messages and reactions to git events (NIP-34), CI status updates, and workflow triggers—as a signed event within a single, immutable audit log. By centralizing these diverse interactions, Buzz aims to replace disparate toolchains (chat, forges, CI/CD dashboards, and issue trackers) with a singular, searchable event record.

Core Methodology and Technical Architecture

The system operates on a "one relay, one community" model, where the relay URL serves as the authoritative boundary for workspace state. Even in multi-tenant hosted configurations, the architecture enforces strict semantic isolation, ensuring tenant-observable state (Postgres rows, Redis caches, and S3-backed object storage) remains scoped by the community identity.

Technical Stack:

• Protocol: Built on Nostr primitives, employing Schnorr signatures for identity and NIP-01 filters for data synchronization.
• Backend: A Rust-based modular workspace utilizing Axum for WebSocket and REST API handling. Services are partitioned into distinct crates, including:
  • buzz-core: Handles low-level I/O types and cryptographic verification.
  • buzz-db: Manages Postgres integration, utilizing full-text search (FTS) across the event stream.
  • buzz-auth: Implements NIP-42/98 for authentication and rate-limiting.
  • buzz-audit: Maintains an integrity-checked hash-chain log of workspace activity.
• Agent Integration: Agents are treated as first-class citizens rather than external bots. They are assigned specific keypairs, channel memberships, and individual audit trails. The system provides the buzz-cli tool, which utilizes a JSON-in/JSON-out interface designed for LLM tool calling, and an ACP (Agent-Client Protocol) harness to bridge Buzz functionality with existing frameworks like Goose, Codex, and Claude Code.
• Workflow Automation: Workflows are defined via YAML and triggered by system events, supporting message, reaction, schedule, or webhook-based execution.

Operational Logic:
The system ensures consistency through an event-sourcing approach where the relay functions as the single source of truth. When an interaction occurs, the relevant service (e.g., buzz-relay) signs the event and propagates it. The system facilitates sophisticated automation, such as "Incident Memory," where agents query six months of history indexed by buzz-search to synthesize context for developers, or "Branch-as-Room," where code commits and CI results are co-located in a dedicated channel record.

The architecture emphasizes "sovereign" data, allowing teams to own their infrastructure while leveraging a unified identity model across all human and machine participants. The system is designed for extensibility, moving away from fragmented service silos toward an "event-log-first" paradigm.