How it works

What happens after you type your idea.

Every build takes the same path from your first sentence to a live app. Nothing ships unchecked.

The sequence

Ten steps, in a fixed order.

  1. You describe it

    One sentence, the way you'd say it to a person. "A portal where each client sees only their own files" is enough to start.

  2. A short interview fills the gaps

    It asks what your sentence left out: who uses the app, what data it holds, which parts are sensitive. Your answers set what gets checked later.

  3. Your answers become a spec

    Everything you said is written into spec.json, a plain record of what the app is and what it protects. Later checks refer back to it. You can draft one free on the homepage, before you have an account.

  4. The spec becomes a plan

    Before any code exists, two documents are drafted from it: PRD.md, which says what will be built in words you can read, and architecture.json, which says how.

  5. The code is written

    The app is built against that plan, piece by piece. At this point it exists, and nothing about it has been checked yet.

  6. Twelve gates inspect it

    They run in a fixed order: the code is scanned for exploitable patterns and committed secrets, migrations are executed on a real database, tenant isolation is attacked live, the plan's acceptance criteria run as tests, and every promised feature is checked off in code. A gate that fails, or crashes mid-run, blocks the build. Every gate, shown.

  7. Findings get fixed and re-checked

    When a gate blocks, the system rewrites the flagged code and runs the gates again, up to a fixed number of rounds. It is never allowed to weaken a check to get past one; tampering with a test is itself a blocking finding.

  8. A build that can't pass is held

    You see every finding in plain English, and you can run the loop again or change the request. A held build never ships, and there is no switch to make it.

  9. The Sentinel signs the build

    When all twelve gates pass, the Sentinel signs it. That signature is the only door to deploy; a build without one cannot go live.

  10. Your app is live

    It deploys to its own URL with its own database, ready for the people you built it for. When you ask for a change later, the same twelve gates run again before it ships.

That's the whole sequence.

Describe the app you need. The sequence takes it from there.

Start a build