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

# Quickstart

> Create, review, and approve your first AI Blueprint.

## Before you begin

You need a verified AI Blueprint account and enough AI credits for the action you start. You can register with email and password or continue with Google.

<Steps>
  <Step title="Describe the product idea">
    On **Dashboard**, explain the product, target users, problem, and desired outcome. Add important constraints such as platform, region, compliance, integrations, or offline use.

    Write in Indonesian or English. AI Blueprint detects the idea language and uses it for generated documents.
  </Step>

  <Step title="Review the enriched idea">
    Read the Smart Requirement Summary. Confirm that the product definition matches what you intend to build.

    Do not approve a vague or incorrect assumption. Correct it while the context is still being formed.
  </Step>

  <Step title="Answer critical questions">
    Resolve decisions that materially change scope, actors, data, security, or delivery. A question may include a suggested answer, but the final decision is yours.
  </Step>

  <Step title="Approve the Idea Review / VPC">
    Sign only when the product context is accurate. This approval automatically starts document generation in the background, and you may safely close the tab.
  </Step>

  <Step title="Review generated documents">
    Check Application Journey, Technical Foundation, Database Schema when relevant, App Map, and every other generated document. There is no second global structure approval.
  </Step>

  <Step title="Approve each current document">
    Use **Blueprint Summary** to inspect open items, project health, and version history. Open each applicable document and use its **Sign Approve** action. The Summary reaches **10/10 Approved** when every current document is signed.
  </Step>
</Steps>

<Frame caption="Sanitized example of the idea-to-review path.">
  <img src="https://mintcdn.com/ia-blueprint/xvYlFUH0B2wc9dt4/images/idea-to-review.svg?fit=max&auto=format&n=xvYlFUH0B2wc9dt4&q=85&s=bbafe32d0d62bb43daa3a2ef68ed7ac3" alt="Idea input followed by review, decisions, and Blueprint" width="1200" height="650" data-path="images/idea-to-review.svg" />
</Frame>

## A useful idea brief

Include enough information to distinguish your product from a generic app:

* who uses it and what each actor needs;
* the problem and measurable outcome;
* the main journey or transaction;
* data, payment, file, notification, or external-system needs;
* constraints such as mobile-only, offline-first, multi-tenant, or a launch deadline;
* what is explicitly outside the first release.

<Warning>
  Approval records your decision against the current version. If regeneration changes a signed document, read the changes and approve the new version again.
</Warning>