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

> The ten customer-facing planning documents and when each one is relevant.

All documents use the same approved product context. Database Schema is conditional; other content also adapts to the idea and decisions you approve.

| Document                      | Purpose                                                                                                             |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Smart Requirement Summary** | Product, users, problem, outcome, decisions, assumptions, and open questions.                                       |
| **Application Journey**       | End-to-end flows, states, handoffs, guards, failures, and recovery.                                                 |
| **Technical Foundation**      | Architecture, technology, storage, queues, observability, recovery, and deployment direction.                       |
| **Database Schema**           | Entities, relationships, constraints, lifecycles, and data boundaries. Generated only when persistence is relevant. |
| **App Map**                   | Product areas, capabilities, actors, and journey responsibilities—not a screen or route list.                       |
| **Access & Security**         | Authentication, authorisation, roles, scopes, audit, and security controls.                                         |
| **Lean Canvas**               | Problems, solutions, users, value, channels, costs, and revenue assumptions.                                        |
| **MVP Scope**                 | Product requirements, MVP boundary, priorities, exclusions, risks, and acceptance criteria.                         |
| **Requirement Coverage**      | EARS requirements, acceptance criteria, traceability, contradictions, and gaps.                                     |
| **UI/UX Design**              | User experience behaviour, states, accessibility, responsiveness, and quality checks.                               |

<Note>
  The output set follows the product's needs. A **Not Required** result is valid when a document would not add relevant implementation information.
</Note>

## Coming-soon delivery areas

Development Planning, Project Management, and Deployment Assist are currently locked. They are not generated by the active Blueprint package and should not be treated as contracted deliverables.