Validation and governance
In this section
| Page | What it covers | Code | Cowork | Desktop chat | VS Code |
|---|---|---|---|---|---|
| ea-validation | Check a model or a package against a conformance ruleset, and interpret and fix the findings. | Yes | Yes | With you | With you |
| ea-ruleset-author | Build a complete validation ruleset for a modeling language, and prove each rule against known-good and known-bad content. | Yes | Yes | Yes | Yes |
| ArchiMate 3.1 ruleset | Check a model built with EA's ArchiMate technology against the structural rules of the ArchiMate 3.1 specification, with a ruleset that ships ready to run. | Yes | Yes | Yes | Yes |
Where it runs: Yes = runs fully · With you = runs, and you do the steps in EA’s window · Partly = one part needs a capability the client lacks · No = not available · TBC = to be confirmed
Validation in AI Power Tools means running a ruleset against a model: a YAML file of conformance rules that each select elements or connectors by stereotype and apply one condition to them. AI Power Tools reports every element or connector that breaks a rule. It never changes the model.
| Item | What it is | Logic |
|---|---|---|
ea-validation |
The skill that writes and runs rules through the ea_validate tool, and interprets the results |
AI + AI Power Tools checks (the validator is deterministic) |
ea-ruleset-author |
The workflow for building a complete ruleset for one modeling language | AI + AI Power Tools checks |
| ArchiMate 3.1 ruleset | A shipped ruleset: 27 rules for models built with EA's built-in ArchiMate technology | Deterministic (a data file; no AI at run time) |
set_active_mdg records a preference and enforces nothing. A ruleset is the only enforcement mechanism AI Power Tools has, so it is also the check that sits behind the MDG skills in Modeling languages: for every mandatory tag a technology declares, a matching rule confirms the repository complies.