Governed-model level

Goal

Make the model part of change governance and make information quality an observable outcome with assigned accountability.

Requirements

• lifecycle for objects and relationships;
• distinction between current and target states;
• owner and next review date;
• criticality, SLA, and security requirements where applicable;
• statement provenance and freshness assessment;
• automated quality rules;
• registered, time-limited exceptions;
• measurement of coverage and defect resolution.

Exit criterion

An architecture change creates a verifiable model change, stale information is visible to owners, and target state is connected to an executable transition. A model is not governed merely because it has an approval workflow or an expensive tool.