Internal research report dated **August 12, 2026** consolidating, for presentation purposes, everything publicly documented about **Buzz** — **Block**'s humans + agents workspace, launched on **July 21, 2026** under the **Apache 2.0** license. It aggregates the two engineering posts already filed alongside the corporate announcement, the GitHub repository, press coverage, X, and **three independent hands-on accounts** that constitute the dossier's only non-self-reported data. **(A) A vocabulary gap documented by quotation**: **Jack Dorsey**'s launch tweet announces *"model-agnostic, decentralized, self-sovereign, and open source"*; Block's `ARCHITECTURE.md` states *"The relay is the single source of truth. All reads and writes flow through it. There is no peer-to-peer event exchange, no gossip, no replication."* The relay is therefore single and authoritative per community: Buzz's "decentralization" is an **organizational sovereignty** — self-hosting and portable identity — not network redundancy. **TFTC**'s formulation: *"Two of those three hold cleanly. The third needs a qualifier."* **(B) An asymmetry between demonstrated rigor and exploitation risk.** On one side, a rare degree of formalism for a v0.4.x/0.5.x: multi-tenant isolation specification **mechanized in TLA+**, authorization properties verified in **Tamarin**, a model-checked Git storage protocol, a hash-chained append-only audit log, 127 *event kinds*, NIP-01/42/98/34. On the other, channel membership is the unit of permission — *"channel membership is not fine-grained tool authorization"* (João Queirós) —, agents run in `--dangerously-skip-permissions` outside any sandbox on a human's machine, and observability is lacking: *"Buzz tells me an agent got a message. It doesn't tell me what happens next"* (DevTools Daily, which reports silent OOM kills). Block acknowledges it: *"the agent can do anything, and security rests entirely on restricting who can tell it what to do"*. **(C) The technical stack**, absent from the filed posts: **Rust** relay (Axum WS + REST), **Postgres**, **Redis**, **S3/MinIO** via Blossom, **Tauri + React** desktop client. Agent integration goes through **`buzz-acp`**, an **ACP** harness that plugs in goose, Codex and Claude Code and translates **ACP ↔ MCP**, plus **`buzz-agent`**, an in-house agent. The report corrects itself on one point: the *"+33% more work"* in Block's TL;DR is the **ratio of completed tasks (20 versus 15 out of 44)**, not a score gain — the score itself rises from 59.1% to 71.5%, i.e. **+12.4 points**.
#Buzz#buzz.xyz#Block
**Deep Research Veille Interne** — rapport non signé · produit le **12 août 2026** en préparation d'une présentation. Aucune URL publique ; source archivée dans `raw-data/`.
**Recurring report from Mozilla**, *The state of open source AI*, **v1.0.1, July 2026**, introduced by a letter from **Raffi Krikorian** (CTO): seven sections, an interactive site, and a downloadable report. Thesis stated in the title of Section 1: *« The model layer has commoditized. Value accrues to the harness above it. »* **Capability state**: on the *Artificial Analysis Intelligence Index v4.1*, the best closed model scores **61** (Claude Opus 5) and the best open model **57** (**Kimi K3**), fourth overall and ahead of three of the largest closed labs; on the *Epoch Capabilities Index*, the gap is **6 points** (K3 at 156 versus GPT-5.6 Sol at 162), described as *« about one release cycle »*, with overlapping confidence intervals. **Sawtooth frontier**: open leads in frontend code (K3 at 1,679 Elo on LMArena Frontend Code Arena, six domains out of seven), contests agentic terminal work (88.3 versus 88.8 on Terminal-Bench 2.1), and cedes ground on professional knowledge work (Fable 5 leads K3 by 92 Elo on GDPval-AA v2). **Usage shift**: the share of OpenRouter tokens routed to open-weight models rose from a negligible level to a third by late 2025, then to a **majority by mid-2026**, with the seven highest-volume models all open-weight — the report itself noting that *« by request count, closed US providers still lead »*, the open lead being a token-volume lead concentrated in coding and agentic workloads. **The central contrast**: *« Open ships easy. Open deploys hard. »* — 79% of developers adding AI use open models versus 71% for closed, but only **53%** of open-model teams reach production **versus 63%**, and the gap widens with organization size (closed 54% → 73%, open 53% → 57%), which *« rules out a resources explanation »*. The stack maturity map (48 components, 9 layers) shows two consistently cold columns — **standardization** and ***enterprise readiness*** — identified as the operational gap. **Section 5**: *« The agentic harness is another user agent »*, and *« The model is eating the harness »* — on every model where both exist, the lab's own harness now wins, the 21.8-point gap having compressed to about 3. Hence the formula: *« A harness tuned tightly to one lab's weights… degrades on anyone else's model, so the tighter the tuning, the less swappable the weights underneath. Lock-in arrives as a side effect of optimization. »*
#Mozilla#state of open source AI#open weights
**Mozilla** — éditeur du rapport · avec une introduction signée **Raffi Krikorian** · *Chief Technology Officer*. Publié en **juillet 2026** (v1.0.1). Données issues de sources tierces créditées (Artificial Analysis, Epoch AI, OpenRouter, LMArena) et d'une enquête propre menée avec **SlashData** (*Mozilla / SlashData 2026 developer survey*, n = 1 410 sur la question des freins).