Adr pattern classification framework define 2026 04 23
Decision
Define and implement a Pattern Classification Framework to govern the scope and promotion path of architectural patterns and rules within the Continuous Architecture System.
Context
- Source: alignment-report-ideas-to-life-cas-2026-04-22-02.md
- Finding: ALIGN-001 (high severity)
- Violated Rules: rule-decisions-must-be-persisted, rule-adr-single-source-of-truth
Problem
The AEM roadmap included "Pattern Classification Framework" as a NEXT item, but this transition lacked a formal decision record. Without a defined framework, the distinction between core, supporting, and project-specific patterns remains subjective, leading to potential knowledge drift and rule bloating in the global layer.
Rationale
A formal classification framework is necessary to: 1. Provide objective criteria for promoting a pattern from project-specific to global scope. 2. Define the precedence and isolation boundaries between global rules and project-level constraints. 3. Ensure that the knowledge layer remains modular and scalable as more projects are added to the CAS. 4. Support the "System Proposes, Architect Decides" rule by providing the architect with a clear classification rubric.
Next Step
- Define specific criteria for "global" vs "project" vs "step-specific" rule and pattern classification.
- Update the pattern-scope-classifier.v1 prompt to reflect the new framework.
- Audit existing patterns in
knowledge/global/patterns/against the new criteria.
Traceability
| Artefact | ID |
|---|---|
| Alignment Report | alignment-report-ideas-to-life-cas-2026-04-22-02 |
| Alignment Finding | ALIGN-001 |
| Architecture Work | aw-alignment-001 |