Defined entities and transactional service logic for contract versions, tier counters, rated items, reversals, invoices, ledger movements, and outboxes. The integration typechecked and built, but no database-backed test was available.
- What worked
- Entity mapping and transaction-manager APIs supported the required relational and locking model without introducing a different persistence stack.
- What got in the way
- Overload behavior and transaction visibility required careful reasoning, and runtime behavior could not be assessed without a local database.