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.
Guide from the media outlet **Every** (every.to/guides) published on **June 2, 2026**, co-signed by **Mike Taylor, Laura Entis and Claude**, proposing an **8-level maturity scale for AI adoption**. **Pivot thesis**: AI adoption **is not a race toward maximum sophistication** — ***« a higher level isn't necessarily better »*** ; one must identify the level that **matches one's own workflow and level of trust**, then regularly reassess whether moving up a notch adds **real value**. ***« The best way to find value in AI is to use it in a way that fits your work. »*** **Structuring axis**: at each level, *« you delegate more of your work to—and place more trust in—the AI »* (increasing delegation + trust). **The 8 levels**: **(1) Chatbot** — conversational interface with no embedded context (ChatGPT, Claude, Gemini); **(2) Copilot** — AI embedded in the workspace with access to the current file (Cursor, Claude in Excel, Gemini in Docs); **(3) Agent** — reactive system that executes step-by-step while requesting approval (Cowork, Codex); **(4) Autopilot** — one describes the **outcome** and the agent executes autonomously, review of the **final result** only (Lovable, Codex, Claude Code; tied to *vibe coding*); **(5) Workflows** — engineers building **harnesses** around agents (planning, review, confidence checks, guardrails; Compound engineering, Claude Workflows, Copilot AI Studio; shift from one-shot vibe coding → **agentic engineering**); **(6) Assistant** — **proactive, always-on** agents that monitor a domain and surface information without being prompted (OpenClaw, Hermes Agent, Claude Managed Agents; e.g. `heartbeat.md` every 30 minutes); **(7) Multi-agent** — simultaneous management of **several long-running agents** with distinct roles (Claude Managed Agents, OpenClaw, Codex Goals; *« firmly in senior engineering territory »*); **(8) Orchestrator** — an **agent manager** directs a team of sub-agents (planning, delegation, monitoring, consolidation; Gas Town, Paperclip, Symphony/OpenAI; *« highly experimental »* — even frontier engineers themselves hold this role). **Sweet spots by role**: **knowledge workers** typically operate between levels **1-4**, **engineers** between **5-8**. **Canonical parallel of intern onboarding**: *« Expect to put in a similar amount of effort with your agents before you can trust them… at the next level of autonomy »* ; and the marker phrase ***« You wouldn't brag that you had eight interns working overnight on a key project, and you hadn't checked their output. »*** The right level depends on **4 criteria**: output quality, cost, reliability (trustworthiness), stakes of failure; and **model capability** progressively shifts the "safe" level of autonomy. A framework directly usable to structure an **adoption doctrine** on the consulting side. Convergence with *systems around the model* (Dropbox/Okumura), *harness engineering* (Böckeler, Lattice, Wescale), Karpathy (vibe coding → agentic engineering), Cherny (/loop + Routines), and the *agent manager* doctrine (BFM/Girard).
#AI adoption#maturity scale#eight levels
**Mike Taylor** · **Laura Entis** et **Claude** (co-auteurs déclarés) · pour **Every** (every.to) · rubrique *Guides*. Mike Taylor est un auteur connu sur les sujets prompt/AI (co-auteur de *Prompt Engineering for Generative AI*) ; Laura Entis est journaliste/éditrice. La co-signature explicite de **Claude** comme auteur fait partie du positionnement éditorial d'Every (entreprise AI-native). Publié le **2 juin 2026**.
Product announcement published on the **Stripe** blog on **April 29, 2026** by **Dan Hill** (Product Manager, Link Consumer Product), following on from the **Stripe Sessions 2026** keynote: the launch of **Link's wallet for agents**, built on a new building block, **Issuing for agents**. **The diagnosis fits in one sentence, and it is the most important one in the text**: *"While machine payments protocols are still gaining adoption, agents need to work with the payment options sellers and consumers use today."* → **Stripe acknowledges that machine-native payment protocols are not ready, and delivers a workaround for existing rails rather than a bet on new ones.** **The mechanism**: a consumer grants an agent access to their Link wallet via a **standard OAuth flow**; the agent then issues a *spend request* and receives either a **single-use card**, or a **Shared Payment Token** — backed by the cards and bank accounts already present in the wallet. Cardinal point: *"The agent never gets access to your raw payment credentials."* The credential is **scoped** (amount, currency, merchant) and the agent must supply the **transaction context** so the human understands what they are approving — the example given in the CLI is explicit: `amount 3500`, `merchant-name "Powdur"`, `context "Purchasing the Powdur Glow Renewal Vitamin C Serum as a gift for $35."`. **The structuring constraint is temporal, and it is owned as such**: *"Today, each request requires the person's review before the credential is shared with your agent"* — **human** approval, **transaction by transaction**, on the web or in the **new Link iOS and Android apps**. Spending limits and cases where the agent would act **without additional approval** are announced, not delivered. **The second layer is the real infrastructure product**: **Issuing for agents** opens the full set of Issuing APIs to anyone building their own agentic wallet — single-use virtual cards, fund storage, spend controls, card-level permissions, **at-authorization** antifraud controls, real-time visibility. Four use cases are cited: internal spend automation, agentic cards embedded at **fintechs**, **vertical SaaS** platforms issuing cards to SMBs under their own brand, **marketplaces** whose selling agents pay suppliers and logistics. **Distribution argument**: Link claims **more than 200 million consumers**, and the article cites **OpenClaw** as an example of a personal agent that benefits. **Two reservations worth flagging up front**: per-transaction approval is presented as a design convenience when it is actually **an admission that delegated agent authorization is not solved**; and stablecoin, *agentic tokens*, and "other payment methods" are all in the **future tense** (*"coming soon"*).
#Stripe#Link#wallet for agents
**Dan Hill** — Product Manager · **Link Consumer Product** chez Stripe. Auteur de l'annonce sur le blog Stripe · rubrique *Product*. Le rattachement au produit *Link Consumer* est significatif : l'annonce est écrite depuis le **portefeuille grand public** · pas depuis l'équipe protocole ni depuis Issuing — ce qui explique que le consentement de l'utilisateur final structure tout le texte.