Much like #300, and as a prerequisite to #354, we would like to define high-level capabilities the AVM requires but does not implements, itself, as a way to make this into a responsibility of the embedding application.
Specifically, this applies to things like hashing/signing/crypto libraries which are already present within any embedding kernel and shouldn't be duplicated by the AVM.
This effectively converts reachy dependencies into injected cases.
Much like #300, and as a prerequisite to #354, we would like to define high-level capabilities the AVM requires but does not implements, itself, as a way to make this into a responsibility of the embedding application. Specifically, this applies to things like hashing/signing/crypto libraries which are already present within any embedding kernel and shouldn't be duplicated by the AVM. This effectively converts reachy dependencies into injected cases.