> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aiblueprint.web.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Blueprint lifecycle

> How an idea becomes a connected document set, and what can continue in the background.

## Lifecycle at a glance

<Steps>
  <Step title="Idea and enrichment">
    AI Blueprint turns the raw idea into a structured product context and surfaces missing decisions.
  </Step>

  <Step title="Product-context approval">
    **Idea Review / VPC Sign Approve** locks the Smart Requirement Summary and validated context. This action automatically starts document generation.
  </Step>

  <Step title="Structure generation">
    Application Journey, Technical Foundation, conditional Database Schema, and App Map are generated from the approved context.
  </Step>

  <Step title="Complete Blueprint generation">
    The remaining documents are generated and published to **Blueprint Summary**. Work continues in the background if you close the browser.
  </Step>

  <Step title="Review, revise, and approve each document">
    Read statuses and open items, stage revision proposals, regenerate affected documents, and use per-document **Sign Approve** for each current version. The Summary reaches **10/10 Approved** when every applicable current document is signed.
  </Step>
</Steps>

<Note>
  The lifecycle has two approval moments: one product-context approval before generation, then individual approvals for generated documents. There is no second global Structure Review Package gate.
</Note>

## 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 preparing documents, ready, or stopped.

<Tip>
  If a run is paused, reopen the same Blueprint. Do not create a duplicate project. Completed stages remain saved.
</Tip>

## 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.

## Conditional outputs

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