Zerya .NET Persistence Evolution

Implement an explicit domain and ownership decision without letting an EF graph, migration convenience, or query shape redefine it. If aggregate or Bounded Context ownership is unclear, use zerya-dotnet-ddd-architecture first.

Establish the persistence contract

1. Read repository instructions, supported database providers, deployment topology, and accepted ownership decisions.
2. Trace affected writes, reads, mappings, constraints, migrations, jobs, imports, and repair paths.
3. Record the authoritative representation, transaction boundary, concurrency token, retention rules, and rollout constraints.
4. Separate domain-model changes from storage changes and query optimizations.
5. Define verification and forward-repair before moving material data.

Read aggregate-persistence.md for EF Core mappings and transactions-and-concurrency.md when correctness depends on atomicity, retries, or conflicting writes.

Evolve data safely

Prefer an observable expand-migrate-contract sequence: