
Choose a unique constraint for email identities
Compute a tenant-scoped email key, test concurrent uniqueness and compare retired-key reservation with an active-only index and its restoration conflict.
Foundation
The journal / Ideas in progress
Engineering & everyday learningSoftware, systems, and the things I’m learning along the way. From first principles to AI in production.
Find something to readA little theory. A lot of practice.

Compute a tenant-scoped email key, test concurrent uniqueness and compare retired-key reservation with an active-only index and its restoration conflict.

Protect tenant-scoped membership identity, preserve roles during repeated adds, and reproduce an insert-or-fetch query that returns nothing after a conflict.

Model order identity, reject orphan references, inspect cascades and separate database relationships from the policy for deleting a paid order.