# [PROJECT_NAME] Tech Stack

> **See also**: [Constitution](constitution.md) for project principles and governance.

<!--
Heading structure is parsed by downstream docs generators:
- Keep `### Languages`, `### Frameworks`, `### Libraries` under `## Tech Stack`.
- Keep `### Hosting`, `### Cloud Provider`, `### Database` under `## Infrastructure`.
- Keep `### CI/CD Pipeline`, `### Deployment Strategy`, `### Environments` under `## Deployment`.
Empty sections are fine — leave the heading so consumers see a stable shape.
-->

## Tech Stack

### Languages

[PRIMARY_LANGUAGE]
<!-- Example: Python 3.11+ (primary), TypeScript (frontend) -->

### Frameworks

[FRAMEWORKS]
<!-- Example: FastAPI (API), React (frontend), pytest (testing) -->

### Libraries

[KEY_LIBRARIES]
<!-- Example: Pydantic (validation), SQLAlchemy (ORM), Rich (CLI) -->

## Infrastructure

### Hosting

[HOSTING_PLATFORM]
<!-- Example: AWS ECS, Google Cloud Run, Azure Container Apps, Self-hosted -->

### Cloud Provider

[CLOUD_PROVIDER]
<!-- Example: AWS, GCP, Azure, Multi-cloud, On-premises, None (local CLI tool) -->

### Database

[DATABASE]
<!-- Example: PostgreSQL (primary), Redis (cache), None (file-based storage) -->

## Deployment

### CI/CD Pipeline

[CICD_PIPELINE]
<!-- Example: GitHub Actions, GitLab CI, Jenkins, CircleCI -->

### Deployment Strategy

[DEPLOYMENT_STRATEGY]
<!-- Example: Blue-green, Rolling, Canary, Manual release to package registry -->

### Environments

[ENVIRONMENTS]
<!-- Example: Development (local), Staging, Production -->
