- 9 weeks kickoff to certified go-live
- Zero rollback events post-launch
- Single audit-ledger trace · MGA + UKGC
- Aggregator wallet-of-wallets contract retained
- Settlement reconciliation latency: nightly → streaming
- Sandbox parity asserted on every release
Brief
A tier-one aggregator running their own integration layer needed an RGS spine that would carry every certified title across MGA and UKGC, without disrupting their existing operator-side wallet contracts. The current platform was a multi-RGS patchwork; reconciliation desks were absorbing the cost.
The brief was specific: one signed contract, one audit ledger, no semver breakage on the aggregator's outbound surface.
What we shipped
We slotted the Ludocrash RGS behind the aggregator's existing wallet-of-wallets contract, keeping every operator integration on the existing surface. Cert evidence packs landed for both MGA and UKGC under a single submission, pinned against the audit ledger versions live on the day of filing.
Operators continued to read settlement events from the aggregator. The aggregator started reading from the audit ledger. Reconciliation moved from a nightly batch to a stream.
What we would repeat
Slotting behind an existing wallet contract — instead of replacing it — collapsed the migration risk. The aggregator's operators saw no change. The aggregator stopped maintaining an in-house reconciliation tool because the audit ledger answered every question it was built to answer.
The next engagement of this shape will start the audit-ledger consumer wiring on day one, not at week six.
What we would change
We underweighted the operator-side regression suite during the cutover. We had a deterministic test driver and a replay harness, but operators were running on top of the aggregator's surface and didn't have visibility into our internal sandbox parity asserts.
Next time, sandbox-parity is published as a contract artefact the aggregator can show its operators directly, not as an internal release artefact.