# <Project name>: one-page spec

> Fill every section in a few lines. If it doesn't fit on one page, the first version is too big.

## Problem
Who has it (one real person), how they solve it today, what that costs (time, steps, money).

## Hard limits
File sizes, formats, what the tools can and can't do, hardware the users have.

## Key idea
One sentence. Then the data flow in one line, with sizes:

```
<input> (<size>) ──► <what the AI gets> (<size>) ──► <AI> ──► <contract> ──► <output>
```

## Inputs and outputs
- In: …
- Out: …

## Architecture and stack
| Part | Choice | Why |
|---|---|---|
| | | |

## Contract between the parts
The exact format (JSON, API) the parts agree on, with a minimal example. Say what happens when it's invalid.

```json
{ }
```

## First version
- In: …
- **Not** in the first version: …

## The demo
What you want to show, step by step, in under two minutes.

## Risks and open questions
- …