AEM Consistency with Decisions
Description
The Architecture Evolution Map (AEM) must remain consistent with Architecture Decision Records (ADR).
AEM is not limited to decisions, but must never contradict them.
Rules
- Must follow knowledge/global/rules/rule-decision-status-drives-stage
⸻
Scope Clarification
AEM may include:
- vision and roadmap items
- system evolution changes
- architectural direction
However:
These must not contradict existing decisions.
⸻
Rationale
AEM acts as a control and synthesis layer, combining:
- decisions (ADR)
- system evolution
- intent / vision
Consistency with ADR ensures governance integrity.
Applies To
- architecture_evolution_map
Example
If an ADR decision is accepted to adopt a new pattern, the AEM must be updated to reflect this change and not contradict it.
Consequences
Benefits:
- reliable architecture state representation
- alignment between decisions and roadmap
- clear governance traceability
Risks if not followed:
- AEM contradicts ADR
- misleading architecture state
- loss of trust in system outputs