# HLA Quality Checklist

Score `docs/discovery/<project-slug>/hla/hla.md` against these 7 items before handoff.
**Pass criterion: 7/7.** Any failed item MUST be fixed and re-rendered.

1. **Component diagram.** The component-diagram section contains a Mermaid graph showing the main components and their relations (not prose only).
2. **Technology stack defined.** Languages, frameworks, datastores, and tooling are proposed, each with a one-line justification; unconfirmed choices are marked `NEEDS INPUT: confirm with architect/TL`.
3. **Integrations documented.** External systems, APIs, and services the solution integrates with are listed.
4. **Deployment model.** Target infrastructure, environments (dev/staging/prod), and deployment strategy are described.
5. **Technical risks.** Each technical risk states an impact level (`Alta|Media|Baja` / `High|Medium|Low`) and a proposed mitigation.
6. **Based on consolidated RF/NRF.** Every capability and constraint cites the RF/RNF IDs it derives from; the HLA was generated from a complete `requirements/index.json`.
7. **Architect/TL validation.** The stack and architecture carry an explicit confirmation note or `NEEDS INPUT` for architect/TL sign-off (the doc requires expert validation).