Engineering post from **Spotify** published on **September 3, 2026** on engineering.atspotify.com (~1,600 words, nine sections, two YAML manifests, four command-line examples), authored by **Dimitri Mazmanov**, Principal Product Manager. It describes a personal setup designed to move I/O tasks out of the context of **Claude Code**. The premise stated upfront: *« Most of what an AI coding agent does for me isn't thinking. It's I/O »* — reading five files to answer a question about a single method, producing a test modeled on the other twenty in the directory. **(A) The modes.** **Portal by Spotify** exposes *AiKA Modes*, declarative agents on an ephemeral runtime — instructions, model, temperature, **MCP** tools — compared to *« AWS Lambda, but for agents »*; two public modes, `bulk-reader` and `code-writer`, run here on **Gemini 2.5 Flash**. **(B) The routing.** A Claude Code plugin named `shunt` replaces `CLAUDE.md` rules deemed *« advisory, not enforced »* with three layers: `PreToolUse` hooks that block any read beyond **350 lines** (threshold adjustable via `SHUNT_MIN_LINES`), two bash scripts calling the Portal CLI, two skills that provide the invocation syntax. The corpus goes to the secondary model and **never enters Claude's context**. **(C) Measurements and their limits.** On a Java monorepo, four scenarios, the reported average saving is **~90%** on `bulk-read`; the author notes that the `code-write` scenario is *« harder to measure »*, and lists three limitations — non-delegable editing, non-delegable reasoning, **10 to 30 seconds** of latency per call. Extends the budget questions from [[gupta-token-budget-wars-marginal-token-utility-2026-05-28]] and the delegation examined in [[willison-fable-judgement-delegation-subagents-2026-07-03]].
#Portal by Spotify#AiKA Modes#shunt
Dimitri Mazmanov (Principal Product Manager, Spotify) · sur le blog d'ingénierie engineering.atspotify.com.
Guide signed by **Michael Segner**, published on **August 20, 2026** on the claude.com blog in the *Claude Code* category: a **5-minute** read announced for approximately **31,500 characters** of body text, also offered as a PDF. Stated material: interviews with **more than a dozen** startups, fifteen named — **Artemis Security**, **Cainex**, **Clay**, **ClickHouse**, **Cognition**, **Commure**, **Crosby**, **Emergent**, **Harvey**, **Heidi**, **Higgsfield**, **Omni**, **Parahelp**, **Translucent**, **Zingage**. (A) Five operating rules: *everyone ships*, *automate the tedium*, *trust, but verify*, *build for rebuilding*, *prototype, dogfood, productionize*, each closed with product tips and gathered into a final checklist. (B) A body made of attributed quotes, each rule illustrated by named executives rather than by an aggregated metric. The four figures highlighted are those of the interviewed companies: **+30%** more features shipped (ClickHouse), **2 to 3×** engineering productivity (Omni), **100%** of bug triage automated (Clay), **more than 6,000 PRs per week** (Artemis Security). Two passages depart from the testimonial register: **Cainex**'s self-correction loop on medical coding, described step by step, and the internal use of **Claude Tag** at **Anthropic** as first responder for CI/CD on-call. The question posed at the opening — *"what would it look like if an organization built their product development lifecycle with Claude Code from the ground up?"* — connects with [[claxton-anthropic-ai-native-sdlc-playbook-2026-08-21]], published the next day by the same publisher, and extends [[cherny-wu-reflecting-year-claude-code-2026-07-17]].
#Claude Code#startups#everyone ships
Michael Segner · auteur du guide sur le blog claude.com (fonction non affichée par la page) ; entretiens avec les dirigeants de quinze entreprises nommées.