H.5.4 Polyglot Dependencies

One source revision can contain several dependency systems without creating one universal solver.

• Compare repository-wide, ecosystem-local, and deliberate multiple-version policies by compatibility and operating cost.
• State the authority and update cadence for lockfiles, registries, mirrors, overrides, and product-specific dependency sets.
• Preserve ecosystem-native resolution evidence while joining it to repository graph and consumer inventories.
• Test cross-language generated APIs, runtime diamonds, image duplication, and vulnerability response.
• Treat Bazel beside Maven, npm, pip, Go, Cargo, CMake, or other systems as an explicit coexistence state, not an invisible migration phase.