The brief is the only place your intent enters the system. Everything after it is the agent's reading of your words, so the words are worth a minute. A vague brief does not fail loudly; it produces a confident build of the wrong thing, and the gate still passes because the page does work.
Four things a buildable brief contains
- What the page is for, in one sentence. A landing page for a coffee shop. A booking form for a barber. An internal dashboard for orders.
- The concrete nouns. Which sections, which fields, how many items, what the prices are. Names of things beat adjectives about things.
- The constraint that actually matters. No images. No frameworks. Must work on a phone. Must not touch the checkout. One real constraint is worth ten stylistic wishes.
- What must not change, if you are editing something that already exists. This becomes a guard: sensitive paths are named in the prompt and kept out of edit scope.
Two briefs, same product
Weak: “Make a nice page for my coffee shop.” There is nothing to measure. The plan will be generic, the gate will pass on a page with no content, and you will rewrite the brief anyway.
Buildable: “One HTML page for a coffee shop. Show the shop name, a menu of exactly three drinks with prices, opening hours, and an address. Inline CSS only, no images, no frameworks.”
The second brief produces a plan the gate can verify item by item, and it is the brief that was actually used for the reference build in these docs.
What the Lead does with it
The Lead seat reads the brief and answers with a numbered list of four to six steps. It is explicitly told not to write code, and each step must be checkable in a browser: pages, forms, states, not vibes. That list is what you approve in the approval stage.
If the plan reads wrong, reject it. That costs nothing and touches no files. Approving a plan you did not read is the most expensive mistake in this product, because it is the last moment before writing starts.
Editing an existing project
Point the Connector at a folder you already have and ask for the specific change. Before anything is edited, the Connector maps the repo (branch, dirty state, detected stack, sensitive paths) and takes a git checkpoint. Files that look like configuration or secrets are kept out of edit scope unless the brief names them.
The diff reported back is measured against that checkpoint, so “what the agent actually changed” is a file list with counts, not a claim.
What is not supported yet
Builds are static pages: HTML, CSS and client-side JavaScript in a workspace that is packed into a zip and served as files. A brief that asks for a database, server-side rendering, or a background worker describes something the artifact cannot carry, and the honest answer is that it will not work yet.

