As discussed with @btutzer currently there isn't a case, but at some point it could be beneficial to be able to adapt the the abstractions during run time.

I already changed it to shared pointers to hold the lib consistent. Or did I misunderstand something and abstractions are meant to be shared ?

I'm normally against using shared pointers when the resources aren't explicitly meant to be shared
, but I don't mind.

The only static asserts in RelibilityConfidenceCombinator.h are at lines 193 195 197 and in CrossCombinator.h at lines 80 82 besides them I can't find any.

Moved it to std::unique_ptr .
Internally it still uses the raw pointers by using std::unique_ptr::release() to get the pointer and removing it from the unique_ptr .

I changed this inside the functionality_Reliability branch