How it works
One page at a time, from a governed object to a reader's screen
This tour explains how the platform stores, edits, publishes and serves content. Each chapter is built from the section types it describes, so the page is its own example.
Status words are used honestly: verified live, built, not yet proven live, or planned.
The journey
Five steps from idea to reader
- 1
1. Object
Every page and article is a governed object in a per-tenant store, with an id, a version and a content revision.
- 2
2. Verb
Changes happen only through object verbs: check out, patch, validate, check in. Each one is recorded.
- 3
3. Export
Publishing writes a JSON export to git with a skip-build marker. Nothing is deployed yet.
- 4
4. Release
A separate, deliberate release starts one production build that ships every accumulated export.
- 5
5. CDN
Readers receive static HTML from the CDN. A deploy check confirms what production serves.
The chapters
Questions
- Is everything on these pages live and proven?
No. Each chapter labels its claims. Static rendering is verified live. The campaign path is built but not yet proven live, and no winner is claimed from any experiment.
- Who is this tour for?
Owners and prospective clients who want to understand the system without reading code.
- Are these pages in search engines?
No. They are marked noindex and follow, so they are reachable by link but not listed.