====== 5.7 Classification and Governance ======
[[fxdemo:01-part:start | Go to Top ]]

The classification model supports [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_and_authority|Governance and Authority]] by identifying the business and [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantic]] scope to which architectural decisions apply.

A requirement, [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Model (LM)]], implementation profile, deployment profile, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] claim can identify the [[dido:99_annexes:annex-b-terms-and-definitions:c:classification_path|Classification Path]] it addresses when scope matters. Identifying the applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:classification_path|Classification Path]] helps reviewers distinguish between:

  * A general [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_system|Financial System]] rule
  * A rule that applies to one [[dido:99_annexes:annex-b-terms-and-definitions:e:ecosystem|Ecosystem]]
  * A rule that applies to one [[dido:99_annexes:annex-b-terms-and-definitions:d:domain|Domain]]
  * A rule that applies only to one implementation profile
  * A rule that applies only to one deployment or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] package

The classification model, therefore, helps prevent local implementation decisions from appearing broader than they are.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>