Data ownership

← Back to concept

Models belong to behavior

A domain owns its models and persistence invariants. The authenticated owner is derived from the server session; a client cannot assign another owner through a submitted identifier. Scope reads and writes by ownership.

Use database constraints and transactions for guarantees that must survive concurrency. Represent revision conflicts explicitly instead of silently overwriting data. Preserve stable identifiers when a profile attribute changes.

Generate migrations from the model source, inspect them and verify migration state. Back up data before destructive changes. A migration baseline for a new database must not be faked over a populated production database.

Runtime files, media and backups live in external volumes. Their retention and access rules belong to explicit service contracts.