# CDMS — CONTAINERIZATION & DEPLOYMENT MASTER SPEC
version: v1.0
status: ACTIVE
parent: master_architecture_index.md
phase: 02
phase_name: Architecture & Engineering Canon
document_role: containerization_and_deployment_master_for_phase_02

---

## 1. OBJECTIVE

Define canonical containerization and deployment structure for Devon modules.

---

## 2. CONTAINERIZATION PRINCIPLE

Containerization follows responsibility isolation.

Preferred rule:
- one operational responsibility per container

No ornamental container split.
No authority mixing inside a single container where separation is required.

---

## 3. REQUIRED ISOLATIONS

Expected isolated responsibilities:
- gateway_api
- llm_interpreter
- fsm_policy
- validator
- executor
- memory_service
- retrieval_service
- observability_stack

---

## 4. DEPLOYMENT PRINCIPLE

Deployment must follow:
- deployment_order_canonical.json
- security baseline
- observable readiness checks
- rollback readiness

---

## 5. HEALTHCHECK RULE

Every deployable unit must expose:
- identity
- health signal
- dependency awareness
- status output

---

## 6. ACCEPTANCE CRITERIA

CDMS is valid only if:
- isolation rule is explicit
- deployment order alignment is explicit
- healthcheck rule is explicit
- rollback expectation is explicit