Blueprint · What a Blueprint is

Blueprint

What a Blueprint is

A Blueprint is the decided stack plus the generated codebase, a MANUAL.md, and a zip verified in a sandbox.

A Blueprint is the decided stack plus the generated codebase. It is not a mood board. It is a zip you can run, with a MANUAL.md that explains why this stack and how to operate it.

  1. 01

    Scenario + Architect

  2. 02

    Preview

  3. 03

    Unlock

  4. 04

    Writers + sandbox

  5. 05

    Zip + MANUAL

Version one, in about five minutes

The first run merges the scenario agent and the Architect in one call. You get a ScenarioSpec (no technology) and a BlueprintCore (the stack). An estimate prices the monthly cost of running it. A lock checks the hard rules. Version one may list known issues instead of blocking.

Then you see a preview: the tree, the decisions, the cost to run. The zip is locked.

After you pay

Writers (one model per domain) generate files in waves. A Docker sandbox runs install, typecheck, build, and lint. A repair agent fixes what fails. Assemble merges the outputs into package.json, README, MANUAL, and the zip. Status becomes ready.

Preview

What you can see before you pay.

Unlock

Token-based price, then the zip.

MANUAL.md

The document that ships with the code.

Build now