Product announcement post from **Block Engineering** signed by **Thomas Petersen** (*Principal Designer & Builder*), published on **August 18, 2026**, ~1,800 words across thirteen short sections, introducing **Buzz Projects** — a **software forge hosted on its own relay**: Git repositories, branches, pull requests, issues, review and merge, multi-repo projects, an activity feed, all linked to conversation channels. The post's standfirst and thesis: *« Coding agents are the terminal for your computer. Buzz is the terminal for your network. »* Three contributions. **(A) A trust doctrine grounded in *ex post* proof rather than *ex ante* authorization**: on one side *« No forced guardrails, no limitations on what your agents are allowed to help you with »*, on the other *« Every push, review, approval, and merge is a signed Nostr event. If an agent authors a patch, you can see which agent produced it and which human authorized that agent to act »*; the section closes on a stated direction — *« we are already exploring ideas around agent trust protocols informed by past behavior »*. **(B) Git interoperability without proprietary tooling**: *« These are standard git repositories… You can fetch, clone, pull, and push over plain Smart HTTP, with no custom tooling or wrapper CLI required »*, with the clé Nostr serving as a single identity — *« The same npub that signs your messages signs your pushes. »* **(C) A distinction between execution surface and network presence**: *« A terminal gives an agent somewhere to execute commands and change files, but it does not give it a persistent place in the network. Buzz does. »* The post produces no figures and contains no outbound links; it qualifies itself as preliminary six times (*« still very basic »*, *« fairly elementary »*, *« still under experiments »*), and Projects lives under the **Experiments** tab of Buzz Desktop.
#Buzz#Buzz Projects#Block
**Thomas Petersen** — *« Principal Designer & Builder »* chez **Block** · auteur unique et signataire du billet ; première apparition dans le corpus. Publié le **18 août 2026** sur le blog **Block Engineering**. Troisième signature Block sur Buzz en un mois · après Tyler Longwell (21 juillet) et Atish Patel (6 août) · et la première non-ingénieur.
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.
SFEIR's decryption (firm voice) of Jason Clinton's (Deputy CISO, Anthropic) debrief published five days earlier — already documented in [[clinton-anthropic-secure-ai-native-sdlc-2026-07-21]]. **The added value lies not in the facts but in the thesis that rereads them**: if Anthropic's controls hold, it is because **a cycle with named stages exists to hang them on** — "the SDLC is the foundation, not a formality." The demonstration proceeds by rereading the mapping (**PSR at Plan, CLAUDE.md + egress allowlist at Code, review agents at Test, continuous DAST at Deploy, triage + SIEM routing at Monitor**), then through a **four-part anaphora**: (1) *without an SDLC, productivity gains do not materialize* — Clinton cites **Amdahl's law**: multiplying code volume by 8 multiplies nothing if review stays sequential and human, and Anthropic gained not by distributing agents but by **identifying the blocking stage (Test) and rebuilding it** — "you don't optimize a bottleneck you haven't mapped" (echoing DORA 2025's **mirror effect**); (2) *without an SDLC, security has no anchor point* — a **gate is by definition a control placed between two stages**, and Clinton's three threats are addressed at distinct moments; (3) *without an SDLC, no **token FinOps** policy can be formulated* — agentic scanning is billed on consumption and grows with code throughput, so **risk-based tiering IS the FinOps policy** (it decides where three agent passes get paid for and where a SAST suffices), otherwise "token spend is not steered, it is discovered at month's end"; (4) *without an SDLC, there is nothing to measure* — the indicators (16% → 54% of PRs commented, one third of past incidents intercepted) exist only because there are stages where a counter can be placed; absent that, one produces only **usage figures** (licenses, tokens) that say nothing about quality or risk. Two strong points beyond the thesis: the reading of the **incident agent-à-agent** ("a security perimeter that rests on an instruction in a prompt is not a perimeter"; **an agent's access to other agents is part of its attack surface**) and an **explicit methodological caveat** — Anthropic's figures about Anthropic, unaudited, published by the vendor of the model described, in the context of a young codebase with no mainframe: **what transposes is the method, not the figures**.
#SDLC#AI-native SDLC#development cycle
SFEIR (voix éditoriale du cabinet, article non signé individuellement) — commentaire de Jason Clinton (Deputy CISO, Anthropic)
Message from **Linus Torvalds** on the **linux-media** mailing list (thread "Linking Patchwork with Sashiko?", about an LLM tool for maintainer assistance), in which the creator and **top-level maintainer** of the Linux kernel **officially settles the project's position on AI**. Responding to Roman Gushchin, who pointed out that an adverse message expressed "a very anti-LLM in general" stance, Torvalds agrees ("Yes") and then **flatly denies that this is the kernel's position** ("And no, that's not the position of the Linux kernel"). He **puts his foot down** as the supreme maintainer: **"Linux is not one of those anti-AI projects"**; those who take issue with that can **"do the open source thing: fork it"** — "or just walk away". **Central thesis**: **"AI is a tool, like the other tools we use, and clearly a useful tool"**; that may not have been "so 'clearly' true a year ago, but it's not in question today". He distinguishes questions **still open** ("what the AI economy will actually look like in the end") from the question that is **settled** ("is it useful?") — "anybody who doubts that clearly hasn't actually tried it". He **concedes** that the tool can be **"painful"** — maintainer burden, and the fact that it "keeps finding embarrassing bugs" — but refuses the ostrich posture ("put your head in the sand going 'La La La, I can't hear you'"). **The right response**: make sure **LLM tools _help_ maintainers** rather than causing them pain. **Non-coercion, deliberately**: "nobody is forced to use it, but **I will very loudly ignore those who try to prevent others from using it**". On imperfection: "AI isn't perfect, but hell, anybody who points at its problems had better also point at the mirror" — "**natural intelligence isn't always all that great either**". **Governance framework**: the kernel project "has always been and will remain about **technology**"; the social angle of open source is a "side benefit, not the _point_"; **"this is *NOT* some kind of 'social warrior' project, never has been, never will be"**; "we do open source because it results in **better technology**, not for religious reasons". Program-conclusion: **"we decide based on technical merit first. Not on fear of new tools."** To be read as a **doctrinal position statement** from one of the most influential figures in software — echoing ESR's pro-LLM counter-testimony (another pillar of open source, [[raymond-llm-coding-empowering-2026-07-08]]).
#Linus Torvalds#Linux#Linux kernel
Linus Torvalds ([email protected]) — ingénieur logiciel finlando-américain · **créateur et mainteneur suprême du noyau Linux** (depuis 1991) et de **Git** (2005). Employé de la **Linux Foundation**. Figure centrale et notoirement franche de l'open source · dont la parole sur les mailing lists du kernel fait autorité et jurisprudence dans la communauté. S'exprime ici en sa qualité de **top-level maintainer** pour fixer la position officielle du projet vis-à-vis des outils d'IA. Autres participants au thread cités : Roman Gushchin (linux.dev) · Laurent Pinchart · Mauro Carvalho Chehab · Konstantin Ryabitsev (Linux Foundation) · Steven Rostedt · Stephen Finucane · Jason Gunthorpe · entre autres. (Message de mailing list linux-media ; date : 2026-07-14 ; date d'ajout à la veille : 2026-07-17.)
An arXiv paper (cs.SE) by Martin Monperrus arguing a radical thesis for the SDLC: coding agents have crossed a threshold of capability such that **human code review is no longer a necessary component** of a quality pipeline. Two claims: (1) autonomous LLM-based systems achieve all the goals of review (defect detection, quality, compliance) at lower cost and higher throughput; (2) the hybrid model "the agent writes, the human reviews" is untenable — it does not ensure real quality and does not scale with AI velocity, creating a "false sense of security". Monperrus contrasts inspection de Fagan (1976) with a **multi-agent adversarial verification pipeline** (generator agent + independent reviewer agents + tests/formal methods + vote-based consensus). The human refocuses on the spec, architectural trade-offs, approval of critical domains, and edge cases. Recommendations: pilot first on low-risk components, measure agent vs. human, make rejection decisions explicit.