Have you tried using a timeseries-database for your timeseries-data? e.g. blog.timescale.com/timescaledb-vs-6a696248104e

There was a detailed blog post by the Nick Craver of Stackoverflow last year: nickcraver.com/blog/2016/05/03/…

It's just a different perspective. The dlang contracts - like Eiffel contracts - exists as distinct language elements and have concrete behavior and that document describes that behavior. I took a more abstract formal verification in general perspective in my answer. But there is no conflict between both, the dlang contracts are LSP-compatible to the formal verification perspective.

If you only need the correct number of items: the binomial distribution can be used to calculate it.

That is a good idea in principle, but it's often surprising what details actually are country-specific. So I wouldn't expect that plan to work out perfectly on the first try.

Simplest possible solution: Serialize your data to formatted XML or JSON and use git to handle the merge. If you want to do something smarter: develop a diff between business objects that makes sense to the users of your application.

HP had the same problem with their printer firmware: itrevolution.com/…