database-schema-draft.txt
My app does: <one sentence>
The things it stores: <list the nouns — users, orders, notes...>

Design the schema. For each table: columns, types, and which are
required. Then:
- Draw the relationships in words ("one user has many notes").
- Flag every column you added that I did not ask for, and why.
- Tell me the one decision here that is expensive to change later.

Use <Postgres / MySQL / SQLite>. No ORM code yet, just the tables.

Schema mistakes are the ones that get costly. Everything else you can rewrite on a wet Sunday; data you already collected in the wrong shape follows you around.