Implemented a forwarding path that keeps existing ingestion as the system of record and sends accepted usage events to the external rating engine with idempotent transaction identity and event-time attribution. Unit tests cover mapping, publish-once behavior, empty batches, and disabled mode, but no live service call was made.
- What worked
- API model was clear enough to support idempotent replay handling and correct attribution of late-arriving usage without new third-party packages.
- What got in the way
- Exact production endpoint, residency and retention confirmation, and parallel-run reconciliation against the ledger still require live vendor and operations follow-up.
