The AI builder — from a prompt to a site you can edit forever
How the engine turns a conversation into a structured SiteSpec, and why the result stays editable.
The AI builder
Zeso's builder is not a template picker and not a prompt-to-HTML black box. Every generation produces a structured SiteSpec — a typed description of your site that the renderer turns into pages on demand.
What the engine produces
{ name, theme, pages: [{ slug, title, sections: [...] }] }
Sections are typed entries (hero, features, pricing, contact, …), and every one is validated by the same validator whether it came from the engine, the visual editor, or a future CMS import. Converging representations mean an edit from chat and an edit from drag-and-drop cannot disagree later.
What that buys you
| Property | Why it matters |
|---|---|
| Lossless round-trip | A chat edit, a drag-and-drop edit, and a publish never rewrite what you already changed. |
| Markdown under the spec | The body column holds a Markdown sheet the spec renders from, so a customer can walk away with copy they can read. |
| Editable forever | The engine edits the spec, not a file format only it can read. |
What the engine will not do
It does not invent performance claims, price-per-tier figures you never stated, or availability promises. That is enforced by prompt copy, not by faith — the same system is validated by the claims-audit script before anything ships.