Module 11 · Platform Operations · 11D
Change & Environment Control
How do config changes reach production safely?
Try this
- 1Push CR-21 to Test
- 2Approve for Prod
- 3Roll back
- Expected: Lane diagram shows version per environment before/after each step.
Dev → Test → Prod · versioned config
Environment lanes
dev
rules-v14
author workspace
data & credentials isolated per env
test
rules-v13
staged release, sample data
data & credentials isolated per env
prod
rules-v13
blue/green · maintenance Fri 01:00–03:00 GST
data & credentials isolated per env
Change request
CR-21 · tighten beauty size tolerance ±8% → ±6%
draft
diff (git-like)
match_rules.yaml - size_tolerance_pct: 8 + size_tolerance_pct: 6 auto_accept: 0.90 review: 0.60
Unit tests (rule engine)
Sample regression (900 pairs)
Schema contract
Secrets separated from config
Approver ≠ author
Before / after
Deployment history
No promotions yet. Prod is on rules-v13.