Essay by **Bill Staples**, CEO of **GitLab**, published on **August 24, 2026** on the about.gitlab.com blog: an announced **31-minute** read, roughly **39,000 characters**, presented as the sequel to a memo written to the board of directors in January 2026 and partially published in May under the title *GitLab Act 2*. The text presents itself as a response to **Anthropic**'s AI-native SDLC playbook, published three days earlier, from which it borrows the opening line — "Code is no longer the bottleneck" — to pose the question that drives it: what becomes scarce when code becomes abundant. (A) The economic diagnosis: the useful unit is not cost per line but **cost per accepted change**, which aggregates generation, environment, context, verification, review, remediation, and governance; AI collapses the generation term alone, which makes the others proportionally heavier — an organization ten times faster at generating "will simply move the queue." (B) The architectural response: four capabilities — agent platform, machine-scale execution, durable context, governance — forming an enterprise layer that outlives the model, "The model should be replaceable. The agent should belong to the customer." (1) Three modes coexist durably, from human-driven legacy to autonomous development, against the idea of a single maturity curve. (2) The CI/CD pipeline becomes the place where the inner loop runs, instead of being an end-of-line gate. The figures cited are Stripe's, Spotify's, and Amplitude's; GitLab produces only one, about its own source control. The corpus already holds [[claxton-anthropic-ai-native-sdlc-playbook-2026-08-21]], the source this text responds to, and [[sfeir-sdlc-pdlc-articulation-2026-07-22]] on the SDLC/PDLC articulation that Staples adopts as his own.
#code abundance#cost per accepted change#theory of constraints
Bill Staples · directeur général de GitLab (fonction non affichée par la page) · sur le blog about.gitlab.com.
Experience report published on **LinkedIn Pulse** on **August 12, 2026** by **Guillaume Dumortier**, in his newsletter *Growth Marketing Fit*, subtitled *« Four layers, a lot of rebuilding, and the failure modes nobody warns you about »*, ~2,500 words. The subject: an internal AI system built **in Claude** for a marketing team of about sixty people — roughly thirty content and sales **skills**, a dozen **source-of-truth modules**, **seven agents, six of which exist only to check work rather than produce it**, a **plugin** for those who live in a terminal, a **browser application** carrying the same knowledge for everyone else, and an orchestration that chains three or four assets into a *campaign bundle*. The thesis is set out early: the quality of an AI output is not determined at the moment of generation, but by what the system knows before it starts and by what happens to the draft afterward — *« The generation step in the middle is the easy part. It's also the only part most teams have built. »* Hence four layers: **Truth** (almost nobody builds it), **Production** (everybody), **Verification** (almost nobody), **Internal distribution** (*« where good systems die of neglect »*). Two failure mechanisms carry the article. **(A) The verifier's bare closed-world « pass »**: a fact-checker backed by product documentation receives a draft containing a claim about another product, one its sources did not cover — it returns a *« pass »*, not because the claim was true but because nothing contradicted it. *« It didn't just miss the error, it certified it. »* Fix: forbid a bare verdict and require every report to declare its **own coverage** — how many claims were checked, how many matched to sources, which fell outside its jurisdiction, which were owned by no source. *« "I can't verify this" became a first-class result. »* **(B) The cross-asset contradiction**: two assets can each be individually correct, each traceable to a real source, and still contradict each other — the press release states one date, the blog post another, both pass, the bundle can't ship. *« Per-asset verification can't catch that, by construction. »* Article's closing clause: *« The generation is free. The trust is the product. »*
**Guillaume Dumortier** — auteur de la newsletter LinkedIn **Growth Marketing Fit** (~1 300 abonnés à la publication). Il écrit en **praticien-constructeur** : il a passé *« une longue partie de cette année »* à bâtir et exploiter le système décrit. La légende de l'illustration précise le socle technique — *« A custom-built Marketing AI OS within Claude »*. Publié le **12 août 2026**.
**Skill** entry: **hyperresearch** by **Jordan Gibbs** is a **deep research harness** that turns Claude Code into a documentary research agent, shipped as a PyPI package (MIT, Python 3.11-3.13) installing **20 Claude Code skills**, a CLI, an MCP server, and a local web UI. Observed on **August 3, 2026**: 1,568 stars, 170 forks, repo created on April 9, 2026, last push on August 1. **The core is a 16-step pipeline adaptive by tiers** — `light` (~30-40 min), `full` (~1.5-2.5 h), `dissertation` (4-8 h, 25,000-80,000 words across 300-450 sources) — which takes a prompt and returns an adversarially audited report with full provenance. **The central architecture decision is documented alongside its failure mode**: the entry skill is a **thin router** with no procedure, each step living in its own skill loaded **fresh at the moment it is invoked**, because the previous version was *« one 1200-line skill that got compacted away by the time Layer 4 needed its triple-draft procedure. The orchestrator forgot the procedure, wrote a single draft, and produced a flat-scoring report. »* **Two load-bearing principles.** *« Patch, never regenerate »*: after synthesis, only surgical `Edit` touch-ups are possible, with the patcher and the polish auditor tool-locked to `[Read, Edit]` at the Claude Code allowlist level, so that they *« physically cannot Write a new draft »*. *« Canonical research query is gospel »*: the verbatim prompt is persisted once in `query.md` and re-read by every step and every subagent. **Sixteen subagents** with configurable role and model (fetchers and cite-checker on Sonnet, critics, synthesizer, and patcher on Opus). **The vault** is a persistent markdown store indexed in SQLite — *« Markdown is truth, SQLite is cache »* — with a note lifecycle (`draft → review → evergreen`, `stale → deprecated → archive`), traceable provenance, a composite quality score (source type, citation authority via OpenAlex and Semantic Scholar with retraction flags, internal PageRank), and an **independence audit** that groups syndicated copies together — *« five reprints of one press release argue with the weight of one source »*. **Three mechanical gates before shipping**: citation integrity (every quoted citation must exist **verbatim** in a vault note), a retraction sweep refreshed on every cited DOI, and a citation-to-sentence link check by a skeptical LLM. **Reservation to flag**: the opening claim — *« currently leads the DeepResearch-Bench RACE leaderboard »* — is contradicted by its own footnote, *« forward-looking projection from a stratified pilot… Third party validation is pending »*. A projection is not a ranking, yet the chart places it ahead of Gemini and OpenAI Deep Research.
#skill#deep research#research harness
**Jordan Gibbs** — auteur et mainteneur du dépôt `jordan-gibbs/hyperresearch`. Le projet est distribué sous **licence MIT** et publié sur **PyPI** (`pip install hyperresearch`). Signaux d'adoption au 3 août 2026 : **1 568 étoiles** · **170 forks** · 13 issues ouvertes · dépôt créé le **9 avril 2026** et poussé le **1er août 2026** — soit une traction rapide sur moins de quatre mois. Topics déclarés : `agents` · `agentskills` · `claude-code` · `deep-research` · `deep-research-agent`.