My previous Python config validator was great for local development, but it hit a wall in minimal "distroless" containers and hardened environments where Python isn't much of an option. Sometimes you can't control the environment; you can only control the tool. To ensure our validation logic could run anywhere from a CI runner to a bare-bones production box, I rewrote the tool in Java. This version focuses on portability, zero external dependencies, and "fail-fast" logic. Why a Java version? A few reasons kept coming up: Zero external dependencies: no pip, no venv, no system packages Easy to bundle: one JAR or native image Runs anywhere: CI, containers, internal tooling Teams already familiar with JVM tooling The logic is the same as the Python version: load config, check structure, fail fast. The difference is the runtime assumptions. The CLI structure The tool is intentionally small: ConfigLoader: loads YAML/JSON.…