memo · ADR 0010

10.The schema is multi-tenant. The product is not.!

The problem: memo ships for one user, with no sign-in, but every table it creates will outlive that.
The options: Single-user tables now and a migration later; a user id on every user-owned table from the first migration, with every query filtered by it.
The move: The user id from day one. The tenant boundary costs a convention when it is written in the first migration and an edit to the retrieval path when it is added afterwards.
What we accepted: A column that is the same value in every row for months, and a filter in every query that nobody needs yet.
When we would revisit: Never, in the sense that removing it is not a move. Real auth arrived in V2 and found the boundary already there.