Corporate blog post from **Block** (`block.xyz/inside`), unsigned — the displayed author is **"Block"** —, published on **August 18, 2026**, ~930 words, announcing **the open-sourcing of Berd**, Block's internal desktop application for working with agents, and laying out the design thesis that guided it: giving agents character *"not only through roles, instructions, skills, and tools, but through distinctive visual identities"* — hence the in-house animated characters, the *"Gloopies"*. The post starts from an observation of fragmentation (*"The technology was powerful, but the experience around it was fragmented"*) and a precisely named interface problem: *"the product gives people little sense of how the agent is configured, which context and tools are available to it, and how it differs from another agent"*. Two structuring contributions. **(A) A three-tier articulation**: **goose** remains the framework and *runtime* that holds the agent loop; **Berd** is the desktop client (projects, context, sessions, agents, configuration); the two communicate via the **Agent Client Protocol**. **Buzz** is designated as the follow-up, for when solo work becomes collaborative (*"Start alone, then go multiplayer"*). **(B) Six requirements handed off to Buzz**, stated as a takeaway: *"private space, durable context, recognizable agent identities, reusable skills, visible configuration, and clearer visibility into an agent's configured context, tools, and capabilities"* — a grid directly reusable for evaluating an agent client. The text itself distinguishes identity from capability: *"The avatars make the agent recognizable. Its role, skills, and tools make it useful."* No usage figures are produced and no license is named for the open-sourcing.
#Berd#Block#open source
**Aucun auteur nommé** : le billet est signé **« Block »** — le champ *Author* de la page porte le nom de l'entreprise. Publié le **18 août 2026** sur `block.xyz/inside` · le blog **corporate** · et non sur `engineering.block.xyz`.
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/`.
Analysis by Janakiram MSV (The New Stack, July 20, 2026) of the **architectural convergence** of the three hyperscalers' enterprise agent platforms: in nine months, **Amazon Bedrock AgentCore**, **Microsoft Foundry**, and **Gemini Enterprise Agent Platform** have converged on the **same six primitives** — runtime, memory, tool gateway, identity, observability, governance — under different brand names. What was a fragmented collection of libraries 18 months ago is becoming a distinct **platform layer**. The thesis: this convergence replays the **2011-2016 PaaS inflection**, where **Cloud Foundry** and **Heroku** unified VMs, load balancers, queues, and secret stores around a portable **application contract** — except that here **no equivalent contract yet exists**, and **no open source project has claimed it**. Consequence: an enterprise cannot **move an agent from one cloud to another** (session state, traces, and identity all end up with a single provider; migrating means rebuilding everything). The author proposes a **line-by-line mapping** of the Cloud Foundry contract onto agents, sets out three design principles (package the agent as **one deployable unit**, **attach** capabilities rather than embedding providers, integrate the **operational** layer into the abstraction), points to what open protocols (MCP, A2A, OpenTelemetry) leave out of scope — the **lifecycle** — and delivers three due diligence questions: **governance** (neutral foundation vs. vendor), **packaging** (the same artifact on two clouds without rewriting), **state** (exportable memory). Verdict: whoever ends up owning the **agent control plane** will define *what an agent is*.
Analysis by **Olivier Rafal** for **WeNvision** (French consulting firm), published on **June 4, 2026** (~4 min read), commenting on the launch of the **Tokenomics Foundation** by the **Linux Foundation** (announced June 3, in partnership with the **FinOps Foundation**), which he sees as the official opening of **the era of "FinOps for AI."** **Pivot thesis**: AI has transformed the economics of software development; the **token** has become *"the new unit of measurement for technology spending,"* mirroring the cloud of the 2010s (**recurring and variable** costs requiring active management), hence the shift by providers from flat-rate pricing to **token-based billing**. **Scale (urgency)**: *"According to Goldman Sachs, global token usage is expected to increase 24-fold by 2030, reaching 120 quadrillion tokens per month"* — an order of magnitude that moves token efficiency from a *"technical detail"* to a **boardroom** topic. Quote from **J.R. Storment** (founder of the FinOps Foundation): *"Token costs and efficiency have become a CEO-level concern, not a technical footnote."* **Transparency/standardization problem**: current AI pricing is not comparable (input tokens / caching systems / output differ from one model to another) → the Tokenomics Foundation aims to **extend the open-source FOCUS specification** to provide a **common language** for purchasing and comparison. **Rafal's central message (beyond cost)**: *"The point of FinOps is not so much to cut costs as to optimize efficiency"* — the real metric is **AI cost relative to business impact** (*time to market, quality, features, eco-design*). **Limits of standards alone**: technical norms are not enough; the **Target Operating Model must be rethought** (teams, processes, data culture, business alignment); Americans are already announcing *"the end of double-pizza teams in favor of sandwich teams."* **Warning marker**: *"an AI-boosted SDLC will merely […] amplify the problems and just help you go faster… into the wall"* (absent organizational foundations). **Foundation sponsors cited**: Accenture, Booking.com, Google Cloud, Microsoft, IBM, Salesforce. **WeNvision's offer**: *"co-build a roadmap, rethink the operating model for the agentic era, and establish the financial governance that has become indispensable."* **French-language reading, aimed at executives/transformation leaders**, of the fiche [[tokenomics-foundation-linux-finops-token-economics-about-2026-06-03]]; converges with the agentic FinOps cluster [[finops-foundation-finops-for-ai-overview-2026-02-17]], finout-finops-ai-agents-four-step-allocation-framework-2026-04-27, gupta-token-budget-wars-marginal-token-utility-2026-05-28 (token→outcome, value > volume).
#Tokenomics Foundation#FinOps for AI#FinOps for AI
**Olivier Rafal** · pour **WeNvision** (cabinet de conseil français — bureaux à Paris, Lille, Strasbourg, Bordeaux, Nantes, Toulouse, Belgique, Luxembourg). Olivier Rafal écrit en analyste/conseil familier des préoccupations de comité de direction (ancien analyste IT, profil conseil-transformation). Publié le **4 juin 2026**.
**About** page of the **tokeneconomics.com** website, presenting the **Tokenomics Foundation** — a **Linux Foundation** project announced on **June 3, 2026**, operated in **close partnership with the FinOps Foundation**. **Stated mission**: *"establish open industry standards, benchmarks, and best practices for the economics of AI infrastructure"* — linking **production, consumption, and monetization** of tokens to **business value**. **Framing definition of tokenomics**: *"Tokenomics is not just about the cost of tokens, it's about the entire layer of AI that they drive from production, to consumption to monetization"* — that is, **the entire economic layer of AI**, from infrastructure cost to model selection to value optimization. **Phase thesis**: early AI adoption prioritized **capability**; the current phase is shifting toward **efficiency and value**, which requires systematic cost management and **visibility**. **5 founding principles**: (1) ***"Efficiency is a design choice. AI cost is shaped by architecture, not just usage"***; (2) ***"Bigger is not always better. The best AI system is not always the one using the most expensive model"*** (right-tool / routing); (3) ***"Visibility comes before optimisation. Teams cannot manage what they cannot see"***; (4) ***"Value matters more than volume. More tokens, more calls, and more automation do not automatically mean better outcomes"***; (5) ***"Open knowledge benefits everyone"*** (shared standards, community learning, transparency). **Governance**: a **Governing Board** (industry direction + fund deployment) and a **Technical Committee** (open specifications + benchmarks). **Deliverables**: extension of the **FOCUS specification** (FinOps), open specs, benchmarks, shared frameworks and metrics. **Target audience**: CAIO, CTO, CIO, CFO, engineers, product teams, FinOps practitioners, researchers, startups, enterprises, public sector. **Stated goal**: moving organizations *"from experimental AI adoption to sustainable AI operations"* by extending the discipline of **variable technology spend** into the token era. **Relevance to this watch**: institutionalization/standardization of **agentic FinOps** at an industry-foundation level — directly converges with the fiches [[finops-foundation-finops-for-ai-overview-2026-02-17]], [[finout-finops-ai-agents-four-step-allocation-framework-2026-04-27]], orq-ai-finops-ai-agents-cost-per-outcome-hosseini-2026-04-15, gupta-token-budget-wars-marginal-token-utility-2026-05-28 (allocation layer, token-to-outcome) and with the **token → outcome** shift (Salesforce/Tallapragada, Sierra/Greenwald). The 5 principles map exactly onto levers already captured: architecture > usage, **Haiku/Sonnet/Opus routing**, observability before optimization, value ≠ volume.
#Tokenomics Foundation#tokenomics#token economics
**Tokenomics Foundation** (entité collective, projet de **The Linux Foundation**, en partenariat avec la **FinOps Foundation**). Page institutionnelle *About* — **aucun auteur individuel nommé**. Annonce datée du **3 juin 2026**.