Rules you define, at the severity you choose
Rules are defined per workspace and carry a severity. Warning-level rules report; error-level rules block. Because the approval workflow runs the validator before submission, an error-level rule is genuinely load-bearing rather than advisory.
Health report over the whole model
Validate Model checks the current model and lists findings by severity. The Health Report takes the wider view — what proportion of the model conforms, and where the concentrations of problems are.
The same rules in CI
The Standards Manager generates a GitHub Actions workflow that runs your rule set against the model in your pipeline, annotating warnings and failing the build on error-severity violations. The rules that govern review and the rules that govern the pipeline are the same rules.
What this covers in the product
Every capability below is part of this area of Yantra Studio.
- Naming Standards
- Validate Model
- Health Report
Questions
Can standards block a merge?
Yes. The generated GitHub Actions workflow fails the build on error-severity violations.
Are warnings and errors distinguished?
Yes. Warning-severity findings report without blocking; error-severity findings block submission and fail CI.
Do the rules apply to imported models too?
Yes — validation runs against the model, whatever route it arrived by.
Related capabilities
-
Diagrams that go through review, not around it
Put architecture diagrams through a real approval workflow: draft, review, approved, with reviewers, an audit log and validation gates that block submission.
-
The diagram and the data model are one artefact
Model entities, attributes and relationships once: the diagram and the data model are one artefact, with subject areas, a metadata repository and normal-form checks.
-
Non-functional requirements attached to the architecture
Track non-functional requirements against the architecture, report technical debt, view the model through stakeholder viewpoints and check principle compliance.