Bill Staples, CEO of GitLab, publishes an essay on August 24, 2026 that extends a memo written to his board in January and a first publication in May, GitLab Act 2. The explicit trigger is Anthropic's AI-native SDLC playbook, published on August 21, from which he borrows the opening claim: code is no longer the bottleneck. His question goes a step further: if producing code stops being the constraint, what becomes scarce, and what architecture must a company have when humans, agents, and multiple models act simultaneously at machine speed.
His answer fits in one sentence: when implementation becomes abundant, trust becomes scarce. For sixty years, software engineering has organized itself around one fact — code is precious — from which descend legacy preservation, developer-productivity optimization, and the ceremony of reviews, approvals, and release gates. This constraint is shifting, and the system built around it will follow.
The economic unit he proposes 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 and makes the others proportionally decisive: an organization ten times faster at generating without touching the rest simply moves the queue. This is the theory of constraints, cited by name.
Stripe, Spotify, and Amplitude's experiences serve as material. They mainly show where the next constraints reappear: environment, CI, review, and governance. A thirty-minute pipeline, he writes, defeats any model. An architecture follows: three coexisting development modes rather than a single maturity curve; the inner loop migrating from the workstation to the pipeline, closer to the repository and producing evidence; autonomy that is governed rather than granted, through deterministic gates, isolation, policy, and evidence.
The vendor's thesis is then laid out: the model is a replaceable execution component, not the durable architecture. Context, identity, policy, provenance, and organizational memory must persist across models and agents, which pushes toward a model- and cloud-neutral control plane. The text distinguishes the Markdown file from the governable record, argues that the agent should belong to the customer, describes a PDLC where business signal becomes verified software, and sees the population of Builders growing. Human judgment, meanwhile, does not become abundant: it moves up toward intent, architecture, and exceptions.