⚡ Workflows
Canary Rollout (progressive deployment)
Minimize risk by deploying changes to a small subset first, validating metrics, and progressively expanding — or rolling back — based on observed health.
Bundle files
📄ORCHESTRATION.md— Orchestration
1# ORCHESTRATION.md
2
3## Diagram
4
5 ┌──────────────────────────────────────────┐
6 │ Change / Deployment │
7 └────────────────────┬─────────────────────┘
8 ▼
9 ┌──────────────────────────────────────────┐
10 │ Canary Agent │
11 │ (execute on reduced scope: 5-10%) │
12 └────────────────────┬─────────────────────┘
13 ▼
14 ┌──────────────────────────────────────────┐
15 │ Observer Agent │
16 │ (monitor metrics + error rates) │
17 └────────────────────┬─────────────────────┘
18 ▼
19 ┌────────────┐
20 │ Metrics │
21 │ healthy? │
22 └─────┬──────┘
23 yes │ no
24 ┌──────────────┴──────────────┐
25 ▼ ▼
26 ┌──────────────┐ ┌──────────────────┐
27 │ Expand to │ │ Rollback Agent │
28 │ next tier │ │ (revert canary) │
29 │ 25%→50%→100%│ └────────┬─────────┘
30 └──────┬───────┘ ▼
31 │ ┌──────────────────┐
32 ▼ │ Incident Report │
33 ┌──────────────┐ └──────────────────┘
34 │ Full Rollout│
35 │ Complete │
36 └──────────────┘
37
38
39## Workflow
40Canary Rollout (progressive deployment)
41
42## Objective
43Minimize risk by deploying changes to a small subset first, validating metrics, and progressively expanding — or rolling back — based on observed health.
44
45## Roles
46- **Canary Agent:** executes the change on the canary scope (limited blast radius).
47- **Observer Agent:** monitors health metrics, error rates, latency, and business KPIs during each tier.
48- **Rollback Agent:** reverts the canary if metrics breach thresholds.
49- **Promotion Controller:** decides tier progression based on Observer data.
50
51## When to use
52- Deployments to production or shared environments.
53- Configuration changes with uncertain impact.
54- Any change where "test in prod safely" is the strategy.
55- Multi-agent task rollouts where you want to validate the approach on a subset.
56
57## Protocol
581. Define canary tiers: 5% → 25% → 50% → 100% (configurable).
592. Canary Agent executes change on tier 1 scope.
603. Observer Agent monitors for observation window (e.g., 10 min per tier).
614. Promotion Controller evaluates:
62 - Error rate < threshold → promote to next tier.
63 - Error rate ≥ threshold → trigger Rollback Agent.
645. Repeat for each tier until 100% or rollback.
656. On full rollout: Observer continues monitoring for bake period.
66
67## Health thresholds
68- **Error rate:** < 1% increase from baseline
69- **Latency p99:** < 20% increase from baseline
70- **Business KPIs:** no degradation beyond tolerance
71
72## Tier schedule (default)
73| Tier | Scope | Observation window |
74|------|-------|--------------------|
75| 1 | 5% | 10 min |
76| 2 | 25% | 15 min |
77| 3 | 50% | 15 min |
78| 4 | 100% | 30 min (bake) |
79
80## Rules
81- Never skip tiers (no 5% → 100%).
82- Rollback is automatic if thresholds are breached — no manual approval needed.
83- Observer must compare against pre-deployment baseline, not absolute values.
84- All tier transitions logged with metrics snapshot.
85
86## Deliverables
87- Deployment progression log (tier, timestamp, metrics)
88- Health dashboard per tier
89- Final status: fully-rolled-out | rolled-back-at-tier-N
90- Post-deployment bake report
91
Lines: 91 | Words: 431
Install
Copy bundle to your OpenClaw workspace.
curl -fsSL https://raw.githubusercontent.com/cerealskill/openclaw-agents/main/install.sh | bash -s workflow canary-rollout ENRate this agent
Loading...
Sign in to rate this agent
Includes
- ✓ ORCHESTRATION.md
Info
- Slug
- canary-rollout
- Lines
- 91
- Words
- 431