Seed data where the same three people own connected records in every table — and three independent layers standing between a fixture and your production database.
Every route declares what it accepts, who may call it and what it returns, on the route line. Three gates make that structural rather than a habit, and the second one had to resort to a probe.
Row-level security is load-bearing when the browser holds a database key, and a column when it doesn't. Cloudflare is the better platform and almost nobody starts there, because nothing comes assembled — so I assembled it.
One schema, two consumers, and why a strict enum is correct for the Worker that wrote it and wrong for the client that reads it.
Boards whose window is a CRON expression, closed windows that stay in your own D1 in plain SQL, and routes that deny by default when auth is absent.
A queryable audit trail in your own D1, written by capabilities that never import it — and by the CLI, attributed to the actual person holding the token.
Two seams in core, built the same way and defaulting opposite ways — because one of them is a gate and the other is a record.
A skill rating that moves both ways and an experience total that only rises — plus three algorithms, and a deploy that fails if you wire a 1v1 rating to a four-player game.