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

# Glossary

> Definitions for the product, document, revision, payment, and implementation terms used in AI Blueprint.

| Term                                        | Meaning                                                                                                                                                                          |
| ------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **AI credit**                               | A product usage unit consumed by eligible AI actions. It is not money and is not the same as a payment-provider fee.                                                             |
| **App Map / App Structure**                 | A structured map of application areas and capabilities. It is not source code or a site map by default.                                                                          |
| **Blueprint**                               | The connected planning package for one product idea. It is more than a single document or chat answer.                                                                           |
| **Blueprint Assistant**                     | The project-aware assistant used for questions, proposals, and supported revisions. A chat answer alone does not change a document.                                              |
| **Blueprint Summary**                       | The workspace overview for document readiness, review progress, project health, versions, downloads, and next actions.                                                           |
| **Current version**                         | The document or whole-Blueprint state currently active in the workspace. Previous versions remain in history.                                                                    |
| **Direct edit**                             | A narrow, approved literal change inside one eligible leaf document without rewriting unrelated documents.                                                                       |
| **Document**                                | One planning perspective inside a Blueprint, such as Application Journey or Access & Security.                                                                                   |
| **Generation / regeneration**               | Creation of a document set, or rewriting affected approved scope after a reviewed proposal.                                                                                      |
| **Idea Review / Smart Requirement Summary** | The structured understanding of the idea that is reviewed before initial generation.                                                                                             |
| **Manifest**                                | The machine-readable Project ZIP index for included files, versions, paths, language, and workflow order.                                                                        |
| **Not Required**                            | A valid current-document stub saying that an artifact does not need implementation content for this product. It must still be reviewed.                                          |
| **Payment history**                         | The application record of checkout and provider-confirmed payment outcomes. It is not proof that a browser redirect completed the payment.                                       |
| **Proposal**                                | A staged change plan for review. Nothing changes until the proposal is applied.                                                                                                  |
| **Project health**                          | A summary that distinguishes notes, risks, repair states, before-go-live work, and blockers.                                                                                     |
| **Project ZIP**                             | The approved implementation handoff containing product documents, PRDs, manifest, configuration placeholders, and coding-agent workflow files. It is not a finished application. |
| **Review / Reviewed**                       | Evidence that the current document was opened for human inspection. It is not Blueprint approval.                                                                                |
| **Restore**                                 | Moving the entire Blueprint back to an earlier snapshot while retaining history. The restored current set may need review and approval again.                                    |
| **Revision history**                        | Document-level history for changes to an individual document. It differs from whole-Blueprint version history.                                                                   |
| **Sign Approve Blueprint**                  | Approval of the complete current version set after review; it unlocks eligible Project ZIP export.                                                                               |
| **VPC / Validated Product Context**         | The approved product context that becomes the basis for connected document generation.                                                                                           |
| **Version**                                 | A recoverable whole-Blueprint snapshot. A version is not the same as a review state or approval.                                                                                 |

When a label in your workspace differs from this glossary, use the meaning shown in the current interface and contact Support if the difference changes an approval or payment decision.