What a Blueprint is

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

   Research

2. 02

   Scenario + Architect + lock

3. 03

   Writers + sandbox

4. 04

   Preview + design QA

5. 05

   Unlock

6. 06

   Zip + MANUAL

#Version one, complete

The first version starts when you confirm the discovery summary. A research swarm reads your references again in depth (product, design scout, design critic, library scout), then the scenario agent and the Architect run in one call: a ScenarioSpec (no technology) and a BlueprintCore (the stack). A lock checks the hard rules against the facts you confirmed; a violation sends the Architect back to repair, never through. The security baseline (auth, security, ratelimit, observability) cannot be skipped on a web project or an exposed API.

Writers (one model per domain) then generate the files in dependency waves; the frontend is written one call per screen, against your references' screenshots and measured type, colours and grid. A sandbox runs install, npm audit, typecheck, build and lint after each wave, and a repair agent fixes what fails. The preview boots and a design QA scores every planned screen against the design brief; below the threshold the frontend is regenerated once before the card renders.

Then you see the preview: the running screens, the decisions, the cost to run, the known issues. The zip is locked; the price is the tokens this run used, times five.

#After you pay

The build is verified once more in the sandbox, Assemble merges the outputs into package.json, README, MANUAL, and the zip. Status becomes ready.