Skip to main content
Generated and checked

Nothing derived is written by hand

The build writes the navigation, routes, contracts and tool list from the description, then checks them on every change. A file that drifts stops the build.

What the build writes

From the description the build writes the navigation, the route table, the service contracts, the list of data sources, the links between each action and the code that handles it, and the assistant's tool list.

Drift stops the build

Generated files carry a header that says they are never authored. On every change the build regenerates them and compares the result with what is checked in. A hand edit, a missing file or a stale one is a failure with a named reason, not a warning.

Contracts between screens and services

A screen reads its data through a contract: what is listed, what one item holds, and what this person may do. Services implement the contract; screens never learn a service's internals.

Checks that refuse

Named refusals

Every check has a name and a red case that proves it fails before it is trusted. A failure says which rule and where.

Fail closed

A build that warns about a problem ships the problem. Ours refuses, and a refused build publishes nothing.

The same gate everywhere

Code, documents and this site pass through gates of the same shape: run, collect refusals, stop on any.

Evidence, not opinion

A gate writes a result a person or an agent can read. That result is the only evidence that a change is good.

Publishing without leaks

The documents we publish are written for the people building the system, so they are full of things that must not leave the building: internal names, identifiers, placeholders, links to private trees. The publisher checks every string a reader could see and refuses the build if any of them survive. The docs site, the engineering notes and this page reach the web through it.

Next

Design system and data

One set of tokens and components, and one way for every screen to reach its data.

Learn more → about Design system and data

Built with agents

AI agent sessions build from a written plan against checks they cannot change.

Learn more → about Built with agents

Read: Refuse, don't warn