Documentation

How Kozto works, in plain words.

Everything below describes behaviour you can check today: the build flow, the pipeline, the validators, the worlds. Where something is not built yet, it says so.

Start building

Build Now is eleven screens, saved in your browser as you type:

1. Seven questions about the business — name, trade, origin, audience, a recommend quote, the visitor's action, the difference. Skip anything; only the name is required.
2. Photography — have it or not, both are fine; upload opens at launch either way.
3. Six taste sliders — restrained to editorial, airy to dense, muted to vivid, even to dramatic, sharp to soft, still to kinetic. The page shows which design world your positions sit nearest.
4. One design world — take the recommendation or overrule it.
5. The review — every answer verbatim, every skip a labelled gap, and a downloadable build brief carrying facts, taste and world to the first build.

The shorter interview asks the seven questions alone. Answers carry over: anything answered in one flow is already filled in on the other.

How a build works

A build is a deterministic pipeline. Business facts and a category recipe go in; a validated page comes out. Three stages call a model under hard validation; every other stage is deterministic and verifiable without one:

1. 0Intake.

   Existing sites are crawled and screenshotted; facts carry provenance from the first touch.

2. 1Comprehension.

   Facts plus provenance, model-boxed: it may only restate what it was given.

3. 2Assets.

   Image contract, focal crops, grade — photography handled as data, not decoration.

4. 3Category brief.

   Recipe lookup: sixteen categories, each with its own spine, claims rules and copy guidance.

5. 4Direction.

   Worlds ranked, unusable ones excluded; a frontier model scores the page, then you choose.

6. 5–6Architecture and binding.

   Spine to intent slots, then constraint search over components — valid by construction.

7. 7Copy.

   Props filled from facts, model-boxed: nothing the facts cannot support may appear.

8. 8–10Assembly, QA gates, publish.

   Claims, links, contrast, structure and variety checked; immutable builds, pointer-flip publish.

What “validated” means

Before anything ships, the build checks:

• Claims against facts — absolute statements, prices and opening claims must trace to something you said. Volatile details (sold STC, today's menu) ship as labelled live state, never as stale promises baked into copy.
• Links resolve, palettes pass contrast — readability is enforced at build time, including keyboard navigation and reduced-motion support.
• Structure matches the recipe — failures name the exact fact to fix, never a silent downgrade.
• Every validator has a control — each check ships with a test proving it can fail, so a passing suite means the checks fired, not that they slept.

The three design worlds

A world is a complete design direction — type, colour, rhythm and imagery grade decided once by an art director, applied everywhere. Your words reflow into any of them without rework.

Gaps, not guesses

Missing data renders a visible, labelled hole — in place, in your design, with a direct path to fill it. Never a fluent placeholder, never an invented-around sentence, never an empty element. A gap is output, not an error: the page ships around it honestly until you fill it.

The console

Every site gets an owner console: approve every word before it publishes, hear from visitors, see the audit trail of every change. Metered builds, visible before you spend.

Pricing and builds

Every build is static HTML, yours to host anywhere. Cancelling stops future builds; it never takes down words you already paid to generate.