Apps and sites
Apps and sites host every Site and App at the edge, with a preview for each Change and a one-step rollback.
Both render records from db.sb, so every screen agrees with the API.
Contract
A Site is public: its Pages, navigation and Brand on one or more Domains. An App sits behind sign-in and shows a Product's Nouns as lists and records, and its Verbs as buttons and forms. A Page is data: its type picks a Template, which fills from the graph.
| Guarantee | Detail |
|---|---|
| Preview | Every Change renders at its own address against test data before it merges |
| Deploy | Deploy moves live to a Version in one step |
| Rollback | Deploying the previous Version; records are untouched |
| Rendering | Server-rendered at the edge, with Markdown for every Page and llms.txt for Agents |
| Speed | At p75, the largest element paints within 1.5 s, layout shift stays under 0.05 and input responds within 150 ms, checked on every Change |
| Variants | A Flag picks a Page's variant before render, so no visitor sees a flash |
| Certificates | Issued and renewed on every serving Domain; a failed renewal marks the Domain degraded and names the fix |
| Guards | Run on every publish |
SiteBuilder authors the Sites; this capability serves them.
Verbs
| Verb | Object | Event |
|---|---|---|
| Version.deploy | Version | Version.deployed |
| Site.publish | Site | Site.published |
| App.publish | App | App.published |
Interfaces
Example
gridmarket.co sells spreadsheet templates. An Agent drafts a new pricing Page as a Change, reviews it at the preview address and deploys it. Checkout conversion falls by a third, so the Agent deploys the previous Version, and the old Page is back in one step.