Rules & Constraints
Active architectural constraints and governance rules.
| Rule | Category | Status | Compliance | Summary |
|---|---|---|---|---|
| Workflow Execution Model Compliance | execution | active | Disabled | All runtime-native workflows must conform to the CAS Workflow Execution Model and its separation-of-concerns principles. |
| ADR as Single Source of Truth | governance | active | Enabled | Architecture decisions must be recorded and updated only in decision records (ADR); all other representations must be derived from ADR. |
| AEM Consistency with Decisions | governance | active | Disabled | Ensure AEM reflects and does not contradict ADR decisions. |
| Core Patterns Must Be Foundational | governance | active | Disabled | Core patterns must represent foundational architectural primitives, not specific strategies or implementations. |
| Language & Semantics Contract | governance | active | Disabled | Defines the semantic contract for language used in architecture artefacts to ensure clarity, consistency, and alignment across the system design lifecycle. |
| Pattern and Decision Lifecycle Alignment | governance | active | Enabled | Ensure consistent interpretation between pattern maturity and decision lifecycle. |
| Promotion Requires Evidence | governance | active | Disabled | Pattern promotion to core must be supported by strong evidence, preferably from multiple sources or systems. |
| Rule Precedence Hierarchy | governance | active | Disabled | Defines the precedence model for resolving conflicts between global, project, and prompt-level rules. |
| System Proposes, Architect Decides | governance | active | Disabled | All architectural decisions must be proposed by the system and explicitly accepted, rejected, or deferred by an architect. |
| rule-architecture-work-authority | governance | N/A | Disabled | No summary provided. |
| rule-generated-artifacts-not-authoritative | governance | N/A | Disabled | No summary provided. |
| rule-signal-promotion-criteria | governance | N/A | Disabled | No summary provided. |
| Decision Status Drives Stage | lifecycle | active | Disabled | The lifecycle stage of any architecture item must be derived from its decision status; items with decision.status != 'accepted' must not be marked as DONE. |
| Decisions Must Be Persisted | lifecycle | active | Disabled | All architectural decisions must be persisted as structured decision records (ADR) before being reflected in AEM or other artefacts. |
| Patterns Must Be Created as Supporting | lifecycle | active | Disabled | All patterns must be created as supporting by default and never directly as core. |
| Decision Schema Must Be Structured | quality | active | Enabled | All decisions must be expressed using a structured YAML decision schema and not as unstructured narrative text. |
| Heuristic-Derived Patterns Require Signals | quality | active | Disabled | All heuristic-derived patterns must include at least one linked signal as evidence. |
| Do Not Merge Across Architectural Layers | structural | active | Disabled | Patterns must not be merged or consolidated across different architectural layers. |
| rule-shared-knowledge-workspace | structural | N/A | Disabled | No summary provided. |