rime validate
rime validate <pipeline.dag.yaml> [--source source_id=path]Parse the DAG, verify the schema, and check graph integrity. No nodes execute.
What it checks
Section titled “What it checks”- YAML parse — file must be valid YAML
- Schema — every node matches its
kind’s Zod schema; unknown fields rejected - Unique ids — no duplicate
id:across the DAG - Input ref resolution — every
inputs:ref points at a known node (nodeIdornodeId.outputName) - Acyclic — no cycles; if one is found, the offending node id is in the error
- Source paths —
kind: sourcepath:must be resolvable from the DAG directory (unless overridden by--source) - Report metadata - node
metadata.reportvalues are checked by the closed DAG schema
| Flag | Description |
|---|---|
--source <id>=<path> | Override a source node’s path: for this validation. Repeatable. |
--project <dir> | Legacy: walk up to a rime.project.yaml marker for project-mode validation |
Output
Section titled “Output”On success:
Root: /path/to/projectSpec: /path/to/project/pipeline.dag.yamlSources resolved: 1Validation OKOn failure, structured errors use stable prefixes:
[V2_DAG_SCHEMA pipeline.dag.yaml:nodes[3].kind] expected one of: source | filter | derive | aggregate | select | sort | ... got: 'transform'
[V2_DAG_GRAPH pipeline.dag.yaml:nodes[7].inputs[0]] references unknown node 'cohorts' — did you mean 'cohort'?Error codes have stable prefixes: V2_DAG_SCHEMA, V2_DAG_GRAPH, V2_REPORT_REF, V2_PARAM.
Related Commands
Section titled “Related Commands”rime check- validate DAG plus optional report wiring.rime run- execute the DAG after validation passes.
Exit codes
Section titled “Exit codes”| Code | Meaning |
|---|---|
| 0 | Validation passed |
| 1 | Validation failed (one or more errors printed to stderr) |
| 2 | Usage / invocation error |