Skip to main content

​
Lifecycle at a glance

1

Idea and enrichment

AI Blueprint turns the raw idea into a structured product context and surfaces missing decisions.
2

Product-context approval

Idea Review / VPC Sign Approve locks the Smart Requirement Summary and validated context. This action automatically starts document generation.
3

Structure generation

Application Journey, Technical Foundation, conditional Database Schema, and App Map are generated from the approved context.
4

Complete Blueprint generation

The remaining documents are generated and published to Blueprint Summary. Each active document card shows a spinner, and Project Health shows Generating. While Blueprint Summary is open, polling updates completed cards and Project Health without a full-page refresh. Work continues if you close the browser.
5

Review the current document set

Read statuses and open items, then open all 10 current document cards. Open a Not Required stub once as well; it has no content to remediate, but its current version still needs review. Stage revision proposals and regenerate affected documents when needed.
6

Approve and export the complete Blueprint

When generation has finished, all 10 current documents are Reviewed, and no repair or blocker remains, select Sign Approve Blueprint in Blueprint Documents. This unlocks Project ZIP for the approved current set.
The lifecycle has two approval moments: product-context approval before generation, then one global approval of the complete current document set. Opening a document records review, not approval.

​
Background work

Generation state is stored on the server. Closing the tab does not cancel an active run. Reopen My Blueprints to see whether the project is still generating, ready for review, or stopped. When Blueprint Summary stays open, it periodically reads that server state. A completed document changes from its spinner to the published status automatically; you do not need to refresh the whole page to discover that generation has finished.
If a run is paused, reopen the same Blueprint. Do not create a duplicate project. Completed stages remain saved.

​
What “development-ready” means

A development-ready Blueprint gives a developer connected context, scope, behaviour, acceptance criteria, and engineering direction. It does not mean every vendor, credential, legal decision, or go-live operation is already complete. Project-health items labelled Before go-live can be resolved during implementation. A Blocked or Needs Repair document requires attention before a team relies on that subject. Regeneration, restore, or a new current version can return documents to Not yet reviewed and invalidate the previous global approval. Review the changed set and select Sign Approve Blueprint again before exporting a new Project ZIP.

​
Conditional outputs

Database Schema is generated only when persistence is relevant. A document marked Not Required is an intentional result, not a generation failure.