UI Is Just Another Type of Agent

Ronald Reynolds · 2026-09-24 · 8 min read

Say you sell helmet liners to motorcycle racers. Your web designer built you a nice store two years ago. Now it's June, it's hot, and you want the cooling liners at the top of the page instead of buried under the winter baselayers. You know exactly what you want. You could say it in one breath at the paddock: liners first, they're the cheapest way in, everybody tries those before they buy a full baselayer. Then you open the store builder, and the sentence turns into a Tuesday afternoon of dragging tiles.

I'll start with what's on the page at https://comos-federation.com/shop/vnm-sport, because it looks like any store. Nineteen products with the owner's photos. Seven shelves: helmet liners, then men's baselayers and tech tees, then ladies', then the winter thermals, the compression pant, a shelf of pre-orders under their own heading so nobody mistakes a pre-order for stock, and the Racer411 sticker last, the ten-dollar one that funds kid racers. A price under each thing and a Buy button. It reads fine with JavaScript turned off. There is no script on the page at all.

Nobody laid that page out. The store's own agent did, and the whole instruction it worked from is one paragraph the owner wrote. Here it is, exactly as stored:

That is the paddock sentence, written down. Read the shelves on the page against it and you'll find them in that order, with the pre-orders fenced off and the sticker at the end, because that is what the owner asked for. Change one word of that paragraph, "signal" to "ink" say, and the next hourly pass redraws the whole page dark. Nobody deploys anything. The page's footer prints the fingerprint of the layout it was drawn from and the minute it was drawn, so you can check that yourself.

Here is what the agent has to work with, and it matters that it's so little. It reads the catalog through the same public catalog search any stranger's agent gets when it walks in the door. It gets no back room. Then it gets the owner's paragraph as its instruction, and one more instruction from us, which is the closest thing ComOS has to a store builder. This is it, in full:

Notice what the agent is allowed to produce. Headings, a tagline, which products go on which shelf, one line of copy per product, a theme name from a list of four. Data. It never writes a line of HTML. A fixed renderer on our side takes that data and draws the page, the same way every time, and the browser is told to refuse any script that shows up. If the agent names a product the store doesn't carry, or slips a link into a heading, the whole page is refused and the last good page stays up. The agent decides what the store says. It never decides what the store sells, or what anything costs, or how you pay. Those live on the other side of a line it can't cross.

So when I say a UI is just another type of agent, I mean it plainly. An agent takes an instruction in the owner's own words and produces something. Most of the agents on ComOS produce actions: a settled order, a refund, a reply to a customer. This one produces a page. It runs on the same schedule as the others, it writes to the same journal, and it's held to the same rule that its output is data the system checks before anything happens. The only difference is that its output is something you can look at.

That's why there's no store builder and no admin dashboard behind this page. The owner's control surface is the paragraph. Want the tech tees on their own shelf? Say so in the paragraph. Want it to stop sounding like a catalog? It already doesn't, because the paragraph said riders talking to riders, and the agent wrote "keeps your head cooler and your helmet lining cleaner" under the black liner instead of a spec sheet.

Buying is deliberately dumber than the page. Each Buy button goes to one pay page for one product at the catalog price, where you put in a card. No cart, no account, no checkout wizard. The agent authored the shelves; it was never handed the register.

And because everything on the page came from a catalog any agent can read, your agent can shop it too, without the page. The same catalog is served as a plain file of data beside every store, so an agent that can only fetch a web page can still read it; one with the ComOS connector can walk in the front door instead. Every storefront ends with the same block, filled in for that store: a paragraph you paste into whatever agent you already use. For VnM Sport it reads:

Your agent reads the same nineteen products the store's agent read. It just draws you a different thing: an answer instead of a page.

The three prompts on this page are published on https://comos-federation.com/prompts, where the owner's paragraph carries the same fingerprint the storefront was authored from. Further reading The Dashboard Was Always a Prompt — the screen was a sentence the vendor wrote; this piece is what happens when the owner writes the sentence. Prompts Are the Agentic Language — who may speak instructions to your agent is the security model; here, only the owner's paragraph instructs the page's agent, and a visitor's agent gets data.