Automatically check AI-generated model and specs against the schema and rules.
AI output is validated the same way human-authored content is. Because IOModel generation targets the schema, the result can be checked for correctness and consistency before anyone reviews it.
What gets validated
| Check | Catches |
|---|---|
| Schema conformance | Invalid types, fields, or structure |
| Reference resolution | Links to non-existent objects |
| Slug rules | Invalid or duplicate slugs |
| YAML/MDX validity | Syntax errors that break rendering |
These map to the same diagnostics used across the product — see Model Validation.
The validate loop
Generate
AI produces model and spec changes.
Validate
Run validation to get structured diagnostics (code, location, message).
Auto-fix and re-check
AI addresses diagnostics and validates again until clean.
Hand off for review
A clean, validated change is presented for human acceptance.
Dry-run first
Mutating operations support a dry-run preview. Validate the proposed result before writing anything, so invalid changes never reach the working copy.
Why this matters
- AI cannot silently introduce an invalid model.
- Reviewers start from a change that already passes checks.
- The same rules apply to humans and AI, so quality is consistent.
Make “validate until green” part of every AI task. A validated draft is the minimum bar before a human spends time reviewing.
Last updated on