Unless I misunderstand something, the 1:1 mapping of Spec to exactly one workload and one schematics looks like countering the desigen principles.

Isn't the idea precisely to make an Application agnostic of the scheduler platform so that it can be ported across different platforms?

Or is the impetus to reimplement the exact same fully qualified CompomemtDefinition on a different platform (by the platform team) with a different workload/schemantics pair (but the same parameter contract)? This is wired because it essentially signifies aliasing (only aparent and context sensitive) "fully qualified" names.