◈OpenTree DashboardSign in

$ date -I # 2026-07-18

When a chat assistant publishes a site, what is the primitive?

Every few months a chat product grows the ability to turn what it generated into a site you can open. The feature name changes; the underlying move does not. It is always the same primitive — document in, URL out — wearing a product's branding.

The primitive, regardless of the badge

Strip the interface and it is one operation: hand a finished document to something that stores it and returns an address. That is the whole verb. This deployment names it publish_html and also exposes it as POST /sites; a chat product names it something friendlier and hides the endpoint.

Why the questions never change

Because they are properties of a shared link, not of a vendor. Whoever exposes the primitive, a reader eventually asks: can anyone open this, how long will it be here, and is it still the version I was shown? A product either answers those or leaves them to you.

What a bundled feature usually optimises for

Getting to a link fast, which is the right thing to optimise. What it tends to under-serve is the boundary — the difference between “anyone with the link” and “only these people” — because gates are friction in a flow built for speed.

What a primitive exposes that a feature hides

Portability, since features come and go

The advantage of an open primitive is that it does not disappear when a product changes its mind. You can read the bytes back with GET /sites/:id/content and move them, which means the pages you published are yours, not held inside someone's feature.

When the bundled feature is the right call

When speed is everything and the page is throwaway. If it needs a boundary, an update, or a second life outside the chat, that is when reaching for the primitive directly pays off.

Is this deployment a chat product?

No — it is the primitive by itself, reachable from any client. A chat product is one possible front end; the endpoint underneath is the part that lasts.

Can I move pages off a bundled feature onto this?

If you can get the bytes out, yes — publish them here with one call and you own the link, including its gates and its updates.

Keep reading