How it works

One site moves from words to files in three moves, through seven seats, and past one check gate. Going live is a separate step that a person takes.

Three moves

Write the words

Put a short brief in brief.md and your words in the copy folder. A plain file is fine.

Build the draft

The build command turns the words into a site. The offline build costs zero tokens.

Check the result

The check command reads every page and fails the job on the first problem.

Seven seats, no publish

One site moves through seven seats in this order. A seat calls only its own hands. No seat publishes.

Architect

Reads the brief, picks a frame or keeps the copy order, picks one mold, and binds it as a draft.

Content

Reads the copy folder and cites each block file. It does not invent missing facts.

Frontend

Plans the page offline, then renders it.

Graphics

Uses local assets only. A remote photo address stops the run.

Visual critic

Runs the checker with noindex. Any failure stops the run.

SEO

Keeps one mold for this site, not live yet.

Deployer

Writes the crew ticket. It never uploads.

Past the check gate

Nothing moves until the checker has read every page. It compares the words on the page against your copy, follows the links, opens the photos, and reads the title, the description, and the noindex line. A single failure stops the job and names the page.

Token rules

An offline build or a rebuild costs zero tokens. An AI build makes one or two calls on the free chain. Paid models join only with the allow-paid flag. Every run writes a token ledger.

Going live is a person's step

The last seat writes a ticket. There is no publish button. A person runs the bind command for the site and the mold to mark a site live. A mold that is already live on another site is refused.

Start with words.

Build a site like this. One page of writing is enough for a first draft. The draft costs nothing, and the files are yours to keep.