Runtime dependencies

The concept of runtime dependencies seems to be missing from the current spec.
By runtime files I mean anything that a program may load dynamically at runtime but isn't necessarily required at build time. Examples of such things could be dynamically loaded libraries for a plugin eco-system or locale files or configuration files.

I think an end user of a cps file should be able to extract from a linux system all the files required to actually execute something that uses the package that a cps package describes and repackage it (and potentially relocate?) onto another system that doesn't have a system level package installed on it. I'm not suggesting that's a standard workflow but this is what would be required to e.g. build a OCI container containing just a single binary from a derived program that uses the CPS package.