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/`.
Trade-press brief (**Payments Dive**, *Dive Brief* format, **August 6, 2026**) covering **Block**'s quarterly earnings release: the company has already rolled out several AI tools to its customers — **Moneybot** (Cash App) and **Managerbot** (Square) — and has not yet decided how to charge for them. **Jack Dorsey** on the analyst call: *"We're in a fortunate position where we can experiment with a number of models, and then choose the right one that's going to align all of our incentives with our customers."* **The financial backdrop illuminates that stance.** Six months earlier, Block had laid off roughly **4,000 people, about 40% of its workforce**, in a reorganization explicitly framed around AI. In Q2 2026: gross profit **up 25% to $3.2B**, revenue **up 10% to $6.62B**, but **net income at $89M, down 83%** year over year due to severance costs closing out the restructuring; 2026 guidance was raised. AI's value, then, is being captured through the cost structure before it is captured through price. **The heaviest fact sits in the middle of the brief**, drawn from the shareholder letter: *"Starting in June, agentic AI helped write and review nearly all of our production code changes"* — writing **and** reviewing nearly all production code changes, at a publicly traded payments company, six months after cutting 40% of the workforce. A self-reported claim to investors, with no definition of *"nearly all"* or of what *"review"* covers. **The tooling**: **Goose**, an internal system built two years earlier, described as model-agnostic (it plugs in different commercial models for employees); **Buzz**, launched the previous month for *"agent collaboration, communication, and code repositories."* **On the customer side**: Moneybot monitors Cash App user activity and surfaces accounts, balances, and transactions — over **one million weekly active accounts**; Managerbot runs automated marketing, margin analysis, and suggests *"operational fixes"* to Square merchants. **Evercore ISI** analysts list four monetization paths — SaaS bundles, direct subscriptions, enterprise offerings, usage-based pricing — **none of them tied to outcomes**. Stated order of priority: **product quality → distribution → adoption → pricing model**. Two distribution facts round out the picture: Square is rolling into **Google Maps** with a *"conversational AI experience,"* described as *"the first step in a broader partnership between Square and Google"*; and the **Tags** payment device (keychain and NFC chip wands) shows **three million people on the waitlist**. Analyst quotes: William Blair (*"Block epitomizes the secular shift toward tech-forward digital finance firms"*) and Bank of America on the *"post-reset operating model."*
#Block#Jack Dorsey#Cash App
**Justin Bachman** — Senior Reporter · **Payments Dive** (groupe Industry Dive). Journaliste sectoriel paiements ; signe ici un **Dive Brief** · format court en deux temps (*Dive Brief* = les faits du jour, *Dive Insight* = le contexte) qui compile une conférence de résultats · une lettre aux actionnaires · un communiqué et trois notes d'analystes.
Tech-watch note by **Didier Girard** dated **August 2, 2026**, prompted by a colleague's question ("what is ACP?") to address a problem that is not terminological but **documentary**. **Three protocols compete for the acronym**, with no technical overlap whatsoever: **Agent Client Protocol** (client ↔ agent — Zed, August 2025, JSON-RPC 2.0 over stdio, Apache-2.0, "what LSP did for languages"), **Agentic Commerce Protocol** (agent ↔ merchant — OpenAI + Stripe, Sept. 29, 2025, competing with Google's **UCP** of Jan. 11, 2026 backed by **AP2**), and **Agent Communication Protocol** (agent ↔ agent — IBM Research / BeeAI, marginal but polluting searches). **The core of the note is not the disentangling but its observed failure**: the author searches "ACP" in their tech-watch knowledge base and gets **twelve results, all about the commerce protocol, zero about Zed's** — *"our watch agents had indexed the acronym without disambiguating it"*. Hence a knowledge-engineering rule: ***"a bare acronym is never indexed"*** — the entity is "Agent Client Protocol", "ACP" is **only an alias**, carried by three distinct entities. A structuring clarification follows (**MCP connects an agent to its tools, ACP connects a client to an agent; the two stack**), then the textbook case: **Buzz**, published by **Block** on July 21, 2026 under Apache-2.0 — a self-hostable workspace built on **Nostr**, where every human or agent participant is a **key pair** and every message, workflow step, or git push is a **signed event** in an append-only log. An entirely protocol-based architecture (`buzz-acp` an ACP harness over stdio, `buzz-agent` an ACP agent calling an LLM, `buzz-dev-mcp` an MCP shell + editing server), hence agent agnosticism: **Goose, Claude Code, and Codex** plug in through the same harness, and **Hermes** (Nous Research) connected to it without Block writing a single line — *"N+M instead of N×M, running in production"*. The note closes on the question of the **Claude subscription** versus third-party agents, with a five-stage 2026 timeline and a **design rule** that holds beyond this case: the line is not legal but **architectural** — ***"who is consuming, and on whose behalf"*** (an `owner-only` agent consumes your subscription on your behalf; an `anyone` agent in a shared channel routes your colleagues' requests through your account). **Verification carried out on this corpus**: the thesis holds, and more starkly than the note claims — not only is "Agent Client Protocol" **completely absent**, but the bare acronym `ACP` **is already typed as an entity** in two fiches, and the KB page `Agentic-Commerce-Protocol` **already attributes the protocol to Google** when it belongs to OpenAI + Stripe. The collision described is not a future risk: it has **already produced an attribution error** in the graph.
**Didier Girard** — auteur de la note. Écrit ici depuis la position de **praticien de la veille outillée** : le déclencheur est une question de collègue · le matériau principal est le comportement observé de sa propre base de connaissances · et la conclusion est une **règle de curation** adoptée en interne. Le texte alterne donc deux voix — l'explicateur de protocoles et l'ingénieur de la connaissance qui constate un défaut chez lui et en tire une norme.
Major investigative op-ed by Jasmine Sun (NYT Opinion, April 30, 2026) on the *San Francisco consensus*: fear of the *permanent underclass* — a viral theory that AI could freeze economic mobility and create a class rendered useless by automation. The article documents the labs' internal dissonance (Amodei on "white-collar blood bath" and 50% of junior white-collar jobs gone by 2030; Altman 2021 → Lehane silence → white paper *Industrial Policy for the Intelligence Age* April 2026; Anthropic Institute March 2026 led by Jack Clark), the benchmarks steering R&D toward human replacement (A.I. Productivity Index, OpenAI's GDPVal: *"over 80% win rate compared to human professionals"* within a few months), corporate actions (Block/Dorsey -50% headcount with Opus 4.6 + Codex 5.3, Anthropic ARR $30B versus $9B end of 2025), and the Shor political strategy (79% of voters worried, jobs guarantee > UBI, *"They work for the bots. We work for you."*). Reference for the *AI labor 2026* dossier.
#Jasmine Sun#NYT Opinion#permanent underclass
Jasmine Sun (Ms. Sun écrit sur l'IA et la culture Silicon Valley sur Substack)