Build a versioned DVC pipeline (dvc.yaml) that chains data prep, featurization, and training stages with cached, reproducible runs
domain: doc.dvc.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Track raw input data with `dvc add`
Create each stage with `dvc stage add -n <name> -p <params> -d <deps> -o <outs> <command>`, chaining outputs of one stage as dependencies of the next
Commit the generated `dvc.yaml` (and `.gitignore` entries) to Git
Run `dvc repro` to execute the pipeline; DVC skips stages whose dependencies/params haven't changed
Commit the resulting `dvc.lock` file, which records hashes of deps, params, and outputs
Known gotchas
`dvc repro` uses a run cache keyed on inputs/params, so re-running with previously-seen parameter values reuses cached results without re-executing the stage
Visualize the stage dependency graph with `dvc dag` before assuming the execution order is correct
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?