Every era of software had a shape for its applications. The desktop era had the installed binary. The web era had the site. The mobile era had the app store bundle. The SaaS era had the hosted subscription. Each shape answered the same three questions for its time: what is the unit of software, who runs it, and who owns what it accumulates.
The agent era hasn't answered those questions yet. Today's answers are improvisations: a prompt pasted into a chat window, a listing inside one provider's directory, a server that exposes tools and hopes for the best. Improvisation is how categories start. It isn't how they mature.
Here's what changed underneath. Frontier models keep absorbing generic capability, layer after layer of what used to be application code. Betting your product on the parts the model will absorb next is a losing trade. The durable trade is the opposite: package what the model will never ship with, because it can't. Your domain's judgment. Your rules and escalation lines. Your accumulated corrections and state.
So the unit of software in the agent era is a package of judgment. The runtime is a capable model the user already has: the Host. And ownership belongs to the user: the data, the context, the corrections, the exit. That's the whole thesis, and it fits in three sentences because we've spent the words elsewhere, in a specification precise enough to disagree with.
This produces an economy with different physics. A publisher who carries no inference bill and holds no user data can serve a market of two hundred people and thrive. An app that inherits the user's model upgrades gets better while its publisher sleeps, and logs every model change because honesty about regressions is part of the contract. Specialized software for small markets stops being a charity case and starts being a business.
It also produces obligations, and we accept them in writing. A definition this useful must be open, so the specification is a gift to the category and always will be. A standard this young must not overclaim, so nothing on this site asserts an endorsement, a certification, or a guarantee that hasn't been earned; the registry and certification program are roadmap, labeled as roadmap. And a category author must be its first conformant builder, so we document what we learn, including what fails, in public.
We're not the first to sense this shift. Builders and writers across the industry have been circling the phrase agent-native for a reason. Our contribution is the unglamorous part: a definition stable enough to cite, a contract precise enough to test, and the patience to author it in the open where anyone can hold it to its word.
The application model for the agent era won't be decided by a keynote. It will be decided by what builders actually ship, inspect, mount, and run. We've written down the shape we believe in. Now we're building in it, in public, and the record will say whether we were right.