zeroclick. / futures
Act II · institutional lens C · 2027Q3 → 2029Q2

Walled gardens

Platform tokens are exclusive. Chat runtimes block third-party rails almost half the time, take rates run at a tenth or more, and the open protocols cost a merchant three times as much to integrate as the platform's own checkout. Agents still grow — 15% of online GMV by 2029Q2 — but on cards and platform checkout, with wallets stuck below a fifth of buyers and cross-garden purchases a coin flip.

Act I · 2026 → 2027The buyer delegatesSoftware moves from ranking choices to receiving bounded authority.
Act II · 2027 → 2029 · institutions decide who can transact
Lens AOpen railsauthority becomes portableLens BFragmented webtranslation becomes the taxLens CWalled gardensdelegation becomes captive
Acts III–V · 2029 → 2040Commerce becomes persistentSeller agents, policies and physical execution turn purchases into an operating system.
The shared story, through this institution

Delegation becomes a platform privilege.

The buyer can still hand work to an agent, but the identity, instrument and recourse remain attached to a runtime account. Reliability improves inside each garden while authority becomes harder to move.

One constant: the selected everyday mobility need and its human boundary. One variable: who can interpret that authority and where recourse lives.

2029 handoff · the buyer can act

Checkout works. Agency becomes the next contest.

By 2029 the agent can buy, but only inside boundaries chosen by the platform. The long-horizon question becomes whether persistent commerce deepens that convenience or makes exit prohibitively expensive.

Walled gardens · delegated commercesoftware owns 6/8 steps
Purchasing experience · plays as it enters the story

The seller side becomes software too

illustrative emerging mechanism · walled gardens · not the default 2029 purchase · illustrative, not a forecast

your policyintentbuyer agentcommercial handoffruntime seller networkcommercial handoffCycleWorks agentcommercial handoffcommute readyoutcome
policytendernegotiationsettlementfulfillment
agent.local/mandates/activeverified
2029 handoff · selected need preserved

The bounded purchase becomes a negotiable mandate.

Outcome

Find a dependable commuter e-bike under $2,200, delivered this month, with theft coverage and local service.

Ceiling$2,200 delivered
Required termslocal service · theft coverage
Boundaryask before changing model or coverage
Authorityplatform account delegation

Execution is integrated, while exit and portable recourse remain constrained. The human boundary is not a negotiable term.

Open a bounded tender
Scene 1 of 5 · Carry the mandate forward
discoverdecidetransactresolve
After the purchase · 2029Q2 · Walled gardens

The first forecast ends. The mechanism contest begins.

The near-term engine’s settled agent GMV becomes the initial delegated-demand pool. The structural layer then separates demand an agent can influence from the smaller share it can execute under authority, seller coverage and governance.

Surfaceapproval bundle
Authoritysingle-use mandate; approve this purchase
What this unlocks nextFrom this boundary, six mechanisms can compound differently through 2032, 2036 and 2040; none is treated as the inevitable successor to checkout.
Open economics, physical boundary, machine cast and six mechanism precursors512 structural/economic sensitivity draws · 2029 handoff is branch-conditioned · flows overlap where noted
Financial state
agent influenced$234B–$268B
agent executed$76.4B–$118B
merchant-routed$62.7B–$98.1B
base execution conversion40%
Physical-world boundaryThe bike arrives at a neighborhood shop already paired with the fitting appointment, coverage and portable receipt. Control returns at The person inspects the evidence and authorizes this one commitment; the agent cannot substitute the model after approval.where execution and recourse remain
Purchasing surfaceapproval bundlewhat the person encounters
Authority + controlsingle-use mandate; approve this purchasewhat software may commit
Machine cast in this purchase3 modeled role classes active: Buyer agent, Mandate agent, Settlement agent; human remains operatorrole activation threshold 8% · not agent population
Six future mechanisms, seen from this chaptermodel-derived activation support · not adoption probability
Embedded34% support · Assistants learn to carry merchant state
Mandates33% support · One-use authority becomes legible
Open network16% support · Adapters translate fragmented commerce
Metered11% support · Agents buy small pieces of digital work
Trust market16% support · Agents inherit platform reputation
Object initiated17% support · Products expose a persistent identity
How this institution forms · 2027Q3 → 2029Q2
2027Q3

The doors close

The largest agent runtimes ship checkouts that only honour their own token. An x402 or MPP challenge from an outside seller is silently dropped in nearly half of attempts. Success dips this quarter even as volume grows, because the successful orders concentrate inside each garden.810

2027Q4

Cards, not wallets

The runtimes push card tokens — lower friction, higher approval — and wallet adoption stalls near 13% as people face incompatible instruments accepted by different merchant coalitions. Platform checkout and card tokens split roughly half of settled volume.5

2028Q1

Developer attention moves

Merchants integrate whichever proprietary SDK matches where their traffic comes from; x402 and MPP plateau near a tenth of volume each among open-web sellers. 'Runtime blocked' becomes a visible failure class, but missing instruments and missing rails still dominate.8

2028Q2

A stable oligopoly

Success reaches 11% and nearly half of buyers now store a card. The mix stabilizes: platform checkout and card tokens a quarter each, UCP a little more, and the open rails roughly a tenth each.7

2028Q3

One in ten, eventually

Agent GMV share passes 5% and a majority of sellers expose a rail. The volume is real, but agents work inside each garden's silo; a purchase that crosses from one runtime's token to another seller's preferred rail fails as often as it succeeds.7

2028Q4

Scorecards

Processors publish monthly agent-acceptance scorecards for their merchants. New sellers pick one of five fixed options rather than invent a sixth. Page-only sellers now serve 37% of modeled demand because packaged capability is cheap, not because the rails opened.7

2029Q1

Linked, but not free

Only a third of buyers have nothing linked, yet the top failure is still the instrument — often the wrong one for the garden the seller lives in. Wallets sit at 18%. This is what the scenario produces when the buyer's instrument belongs to the platform.9

2029Q2

Reliable inside, a coin flip across

Agents carry 15% of online GMV with a 17% success rate — seven points of GMV below the open ending on the same demand. Cards clear 25% of settled volume, platform checkout 24%, and x402 and MPP about 12% each. Some verticals may see agents drive a quarter of orders; nobody sees agents buy anywhere.678

Continue this institution into the 2040 story →

Open this lens’s model dossier, actors and charts
Narrative dossier · derived before prose

Why this future moves

Runtimes privilege proprietary credentials and checkout, fragmenting buyers and sellers into platform-specific markets. The writer receives this cross-quarter spine, all actor arcs, counterfactual outcomes and open questions before drafting any scene.

2026Q4the market state moves fastest heresettlement +2.5% · agent GMV +0.2% · seller coverage +16.0%shared
2027Q1the market state moves fastest heresettlement +2.2% · agent GMV +0.3% · seller coverage +10.2%shared
2027Q2the market state moves fastest heresettlement +2.0% · agent GMV +0.4% · seller coverage +6.6%shared
2029Q2the market state moves fastest heresettlement +1.3% · agent GMV +4.5% · seller coverage +2.1%post-fork
What could break this scenario

What observed purchase-attempt series would justify replacing exogenous intent growth with an estimated adoption process? Would merchants actually respond to failed agent demand quickly enough to reach 64.5% rail coverage? Which runtime policy, distribution or regulatory events would change third-party rail access? How much cross-instrument reach and seller integration savings can ecosystem-wide coordination cause beyond open protocols alone, and which institutions could supply it? Which reproducible commercial-task evaluation series could anchor capability learning after 2029 instead of treating it as a structural prior? Which observed seller-side deployments could distinguish real pricing and inventory delegation from ordinary merchant automation? Which standards, statutes and dispute outcomes would demonstrate that authority, receipts and liability are becoming portable across runtimes? What comparable loss, dispute, collusion and manipulation datasets could anchor adversarial pressure as machine counterparties grow?

Actor model · decisions exposed by the engine

Who moves this future

Each lane is generated from the same quarterly state as the charts. The action is a deterministic interpretation of pressure in the model, not prose invented after the fact.

Shopperdelegates a purchase and decides which instruments an agent may usedelegates more repeat purchases as settlement becomes routine54% → 72%
Merchantpublishes inventory, integrates rails and absorbs fees or failed demandoptimizes price, terms and routing across supported rails47% → 65%
Buying agentdiscovers sellers, chooses a rail and retries when checkout failsasks the shopper to link a spend instrument8% → 17%
Agent runtimedecides whether an agent can reach third-party payment railsprivileges its own credential and checkout55% → 55%
Payment networksissue credentials and settle card, wallet and protocol paymentscompete on interoperable reach and settlement reliability55% → 52%
Commerce platformbundles checkout for sellers and sets platform takeuses distribution to defend checkout and take12% → 12%
Coordination ecosystemstandards, networks, runtimes, platforms and independent routers that make instruments and seller rails work togethersurvives at the open-web edge of platform-specific markets0% → 0%

The numbers behind walled gardens

Share of agent purchase attempts that settle
0%10%20%30%40%forkCoordinated 24%Fragmented 22%Walled 17%2026Q32027Q12027Q32028Q12028Q32029Q12029Q2
CoordinatedFragmentedWalled
Agent GMV retained by merchants after platform take
0%10%20%30%40%forkCoordinated 22%Fragmented 19%Walled 14%2026Q32027Q12027Q32028Q12028Q32029Q12029Q2
CoordinatedFragmentedWalled
Agent share of online GMV
0%10%20%30%40%forkCoordinated 22%Fragmented 20%Walled 15%2026Q32027Q12027Q32028Q12028Q32029Q12029Q2
CoordinatedFragmentedWalled
How settled purchases execute — walled gardens
browser drives the page 7%merchant protocol 93%2026Q32027Q12027Q32028Q12028Q32029Q12029Q2
browser drives the pagemerchant protocol
Settled volume by rail — walled gardens
x402 14%MPP 13%UCP 25%card tokens 24%platform checkout 24%2026Q32027Q12027Q32028Q12028Q32029Q12029Q2
x402MPPUCPcard tokensplatform checkout
What buyers hold — walled gardens
wallet 20%card token 52%nothing linked 28%2026Q32027Q12027Q32028Q12028Q32029Q12029Q2
walletcard tokennothing linked
Why attempts fail — walled gardens
settled 17%no instrument 30%no rail 24%runtime blocked 10%seller capability gap 14%2026Q32027Q12027Q32028Q12028Q32029Q12029Q2
settledno instrumentno railruntime blockedseller capability gapabandoned

By 2029Q2: 17% of attempts settle, agents carry 15% of online GMV and merchants retain 14% after platform take; 20% of buyers hold a wallet and 65% of sellers answer a rail. Top failure: no instrument at 30%.78