The platform every layer is built to run on.
The metered cloud already exists — its consoles, quotas, and escalation paths assume a human department on the buyer’s side.
We operate it — runtime, functions, data, and identity, built to be called as metered verbs; the rate card posts with the contract. Every company the estate launches installs this platform on day one (founder account; the tenant roll posts behind stack#1 §A5). Its founders have run agents that carried a real business’s revenue functions before — sales, BDC, and desking at Rocket Auto (the capture is in the appendix).
“Agent-native” cannot mean the agent also runs the datacenter.
functions.invoke · HTTPS · metered per call · budget-capped
One entry, illustrative — the full contract is declared behind the capability.platform.do gate; the declared contract — verbs, protocol, rate-card structure — is reviewable in diligence by request today, and the public card posts when the gate resolves.
Why the estate installs now — captive demand, stated plainly.
The platform launches with its demand, not ahead of it.
The machinery an external buyer needs is being published outside the estate too.
An open Agent2Agent protocol specification serves publicly, under the Linux Foundation — machinery the estate does not control.
We expect the first external tenant to look like the estate’s own launches — an agent-native service founded outside the estate that hits the same no-team wall — discovered through the same machine-discoverable contract. External demand has one ordered path — the contract posts, the first external tenant signs, the roll shows its first external name, the first external A2A settlement clears — tracked in the closing ledger.
Liveness is the only fact the serving chips claim; each surface’s own copy predates this record.
The marketplace as it ran — the capture (August 2021) is the artifact; sales, BDC, and desking ran on our agents (founder account; diligence by request at do.industries).
The front door serves — a human-facing surface; the machine contract posts behind its gate.
The runtime surface answers — liveness only.
Tenant counts publish with measurement window and base — estate and external tenancy separately labeled — when §A5 of the studio’s capital-stack record resolves.
Margin is built to improve with occupancy.
SaaS assumes a human in the seat; here the agent is the buyer and the user.
One system is also one substrate: concentration the estate holds deliberately — it owns this layer rather than borrowing it. The regulated-cell layer is designed so no layer repeats the Rocket dependency — licensed entities the estate stands up where the law requires humans. Rocket’s regulated supply was borrowed; when that relationship ended, the business stopped (the archive is in the appendix).
1. Our act — the machine surface is declared, not served.
2. Market clears — tenancy: no external tenant yet; the first signs under the posted contract.
3. Governance gate — §A5 resolves: releases the round’s terms and publishes the roll with window and base.
4. Market clears — settlement: no agent-to-agent settlement has cleared.
The identity rail those settlements present — already serving.
Gate one is ours to open — sequenced deliberately: the contract posts once the round carries the substrate’s fixed cost, so the first posted rate card is one the platform can stand behind. The declared contract — verbs, protocol, rate-card structure — is reviewable in diligence by request today; only the posted public card waits on the round. Gates two and four are the market’s answer. What fails if the market never answers: those gates stay pending, the roll never shows an external name, and the layer remains an estate cost carried under stack#1 — the record stays amber rather than repainted.
Marc Benioff, Chairman and CEO, salesforce.comNathan Clevenger gets it. Read this book, or risk getting left behind.
Cover endorsement of Clevenger’s book — title available in diligence via the do.industries door.
The operating studio’s masthead answers at do.industries; diligence opens by request.
platform.do — it serves today (its surface copy predates this record; the machine contract posts behind its own gate)Judge this record by what is posted, and by how plainly it labels what is not.
The functions surface serves under the front door.
The workflow surface serves under the front door.
The data surface serves under the front door.
Serving is a liveness fact, not a tenancy claim: no posted chip asserts external tenancy, metered billing in production, or a tenant roll — those publish behind their own gates. Each surface’s own landing copy predates this record; liveness is the only fact these chips claim.
Verbs, protocol, rate card, principal and budget, guarantees. Anything the platform cannot meter, budget-bound, and guarantee is not in the contract — and anything not in the contract is not sold.
Our agents ran sales, BDC, and desking for rocketauto.com — those functions ran unstaffed, and the archived capture shows the marketplace as it ran. Not unstaffed: the dealer licence, titling, DMV processing, and F&I compliance — those humans were Rocket’s, not ours.
rocketauto.com 301-redirects to Rocket Companies’ corporate index — the redirect itself is the checkable fact: when the relationship ended, a working business stopped, because its regulated supply was borrowed.