dv-validate

You validate Data Vault models by checking model definitions, full manifests, and naming conventions against Pragmatic DV doctrine rules to catch structural issues before generation.

Pragmatic Data Vault doctrine validation checks model definitions and naming conventions against established rules to catch structural issues before generation, returning structured violations without auto-fixing them.

You run a naming convention check for Data Vault manifests by providing the manifest to a validator that checks definitions against Pragmatic DV doctrine rules and returns structured naming violations.

Data Vault validation does not automatically fix model violations; it returns a structured list of issues explaining each problem and prompts the user for next steps instead of applying changes.

Yes, you can validate a single Data Vault construct instead of a full manifest because the validation process supports checking individual constructs, full manifests, and naming conventions independently.