◈OpenTree DashboardSign in

$ date -I # 2026-07-24

Live artifacts, and what the reader actually receives

“Live” means the render tracks the model's edits in real time. From where the author sits, that is the point. From where a reader sits, it raises two questions the author rarely thinks about: is this still the version I was shown, and will it be here tomorrow?

Live is an authoring feature

While you are building, watching the page redraw on every edit is exactly right — it is the tightest possible feedback loop. The liveness serves the person writing, in the moment of writing.

Two questions it hands to the reader

What “published” changes about both

A publish primitive freezes a version at an address. The bytes at the URL are what you sent until you deliberately replace them with update_site — and even then it is the same URL, so the reader's bookmark is never wrong, only newer. Persistence stops being a property of a chat session and becomes a property of a link you can point at.

Replace-in-place, on purpose

This deployment leans into controlled updates rather than continuous liveness. The same token, new bytes, no version history to roll back to — the reader always gets a coherent version, never a half-finished edit.

update_site({ id: "…", html: "<updated document>" })

What the reader receives here

A page with a private-by-default posture: an unguessable token, no-referrer, a strict CSP, and noindex. Nothing about the link tells them it was made by an agent, and nothing changes under them unless the author chose to change it.

When liveness is the right answer

Pair-building with someone who is in the room with you, watching the same panel. The moment the audience leaves the room, freeze a version and send a link.

Can a reader tell which version they have?

On a published link, yes — the bytes only change when the author replaces them, and the URL is the same each time. On a live panel, the render can move without a signal the reader controls.

Does replace-in-place keep old versions?

No. It overwrites the same stored object; there is no rollback. That is a deliberate trade for a stable URL and a coherent reader experience.

Keep reading