orun validate
orun validate is the verify step: it checks the intent file, the component manifests it discovers, the reserved ORUN_ environment prefix, the profile and dependency rules, and the live preview declarations, without loading compositions or generating a plan. Checking each component's parameters against its composition's schema happens in orun plan; run both in CI. See standards for what each command enforces.
validate always operates on the full intent regardless of your current directory. CWD-based component scoping does not apply — you need to know the whole graph is valid, not just your component. The --all flag has no effect on this command.
Usage
orun validate
When --intent is not specified, orun auto-discovers intent.yaml by walking up the directory tree.
When to use it
- pre-commit validation
- fast CI checks before full plan rendering
- debugging schema failures independently from execution planning
Examples
Validate the repository example:
orun validate -i examples/intent.yaml
Enable debug output while validating:
orun validate -i examples/intent.yaml --debug
Flags
| Flag | Meaning |
|---|---|
--intent, -i | Intent file path (auto-discovered if not set) |
--debug | Enable debug logging |
Use validate first when you want a fast failure signal before compiling or executing a plan. --config-dir remains available as a global legacy fallback for folder-shaped compositions.