embabel realm validate <directory> [--with <dir>]... [--json] [--strict]
Would this realm checkout load? The same checks realm_validate runs over MCP — realm.yml,
types and their parents, joins, producers and the governance their source can honour, views,
rules, apps, the wasm build — answered with no appliance running. It runs the validator
that ships in this appliance’s own server image (ghcr.io/embabel/assistant at the release it
follows, or a legacy EMBABEL_VERSION pin) in a throwaway container, so the answer is the one the server you will
install into would give. realms validate is the same command.
embabel realm validate ~/dev/realm-java-source-code \ --with ~/dev/realm-code-model --with ~/dev/realm-java-code--withnames a realm installed beside it — a dependency whose types it extends, or whose types and producers its joins go through. Its types and producers count as installed; it is not itself validated. The default world’s types are always known, as they are in every world. Repeatable.--jsonprints the report as JSON;--strictfails on warnings as well as errors.--imagevalidates with another server image, such as a local build.
The checkout and every --with directory are mounted read-only; validation builds into a
copy inside the container. Exit status: 0 passes, 1 does not, 2 could not validate
(a directory that does not exist, Docker not running, or an image older than the command).
For a realm repository’s CI, the same image runs directly — see realm-spec’s README, “Validating a realm in CI”.