---
title: Project Charter
seriousness: ""
last_reviewed: {{date}}
---

# Project Charter

<!--
Written once by the establish-charter gate, before real building work begins.
Captures the project's seriousness and the core tech/architecture decisions, with the
plain-language "why" for each — so the decisions are deliberate and a non-technical reader
can understand them. Keep it compact and durable; revisit as the project grows.
-->

## Seriousness

<!-- "demo" (quick / throwaway, optimize for speed) or "serious" (intended to ship & maintain). -->

## What we're building

<!-- One short paragraph: what the project is and who it's for. -->

## Tech decisions

<!--
One row per core choice. Lead with the choice, then the plain-language reason and the trade-off
that was accepted. On the serious path, link the ADR that records the decision in full.
-->

| Area          | Choice | Why (plain language) | Trade-off accepted | ADR |
| ------------- | ------ | -------------------- | ------------------ | --- |
| Architecture  |        |                      |                    |     |
| Datastore     |        |                      |                    |     |
| Auth          |        |                      |                    |     |
| Hosting       |        |                      |                    |     |
| Scale         |        |                      |                    |     |
| Testing       |        |                      |                    |     |

## To revisit later

<!-- Choices deferred or defaulted now (common on the demo path) that should be reconsidered as the project grows. -->