Modeled versioned contracts, immutable charges, and period counters as entities, and designed transactional rating with a write lock on the current period row. Relied on existing service patterns. Did not run against a live database.
- What worked
- Entity, repository, and transaction patterns already in the workspace were enough to design idempotent rating and period counters without inventing a new data layer.
- What got in the way
- Schema changes were left to the same out-of-band process as the other services, so there was no migration path to verify in this task.