# HLA Anti-patterns

Failure modes to avoid when generating the F1 high-level architecture.

- **No stack at all.** Producing an architecture with no technology stack. The doc requires a proposed, justified stack. Propose one; mark unconfirmed choices `NEEDS INPUT: confirm with architect/TL`.
- **Fabricated certainty.** Presenting an unevidenced stack or cloud provider as a final decision. Propose with justification, never invent client-specific facts (existing systems, credentials, contracts).
- **Prose-only components.** Listing components as text without the Mermaid component diagram. The diagram is mandatory.
- **Missing deployment model.** Omitting infrastructure, environments, and deployment strategy.
- **Flat risk list.** Listing risks without impact level and mitigation. Every risk needs both.
- **Untraceable claims.** Capabilities or constraints that do not cite the RF/RNF they derive from.
- **Running ahead.** Auto-chaining into `planning` or PRD generation. Only suggest the next command.
- **Hand-written Markdown.** Writing `hla.md` directly instead of assembling it from `.blocks` + template via `assemble-doc.sh`.