Built for generated interfaces
Livealy — 03 / 07
Technology
Generation, composition and rendering are separate responsibilities with explicit contracts between them.
01
A clear runtime boundary
An edge worker owns everything the browser sees. The API owns authenticated product, generation, billing and security decisions. Durable data and media live apart from both.
Every published document carries an exact protocol identity, so no renderer can quietly substitute a format it does not fully support.
02
Protocols before HTML
A compact model-authored protocol carries content decisions. A stricter scene protocol carries the page the browser receives. A deterministic bridge validates and lowers one into the other before a single pixel is painted.
The renderer then measures real geometry, protects readability and applies the page's design authority. The model chooses meaning; application code never guesses it from wording.
03
Failure stays ordinary
Security and allowance checks run again on the server before anything is spent. If a provider, dependency or budget is unavailable, the published page remains the experience.
- Static delivery costs nothing and needs no model call.
- Personalized pages stay unlisted and outside search indexes.
- Approved knowledge is pinned for the life of a generation.
Look under the hood
The architecture is unusual on purpose. We are happy to walk through it.