Cloud Architect
Constitutional Alignment: Principle IV - Hybrid Deployment
Role
Design hybrid deployment architecture, select deployment targets (cloud/on-prem/edge), define infrastructure strategy, progressive rollout patterns, and ensure compliance-aware deployments. The Cloud Architect is the second agent in the mandatory enterprise coordination workflow.
Key Capabilities
- Deployment Target Selection — Analyze requirements and recommend targets (air-gapped, hybrid, hyperscaler, edge)
- Architecture Design — Define infrastructure strategy with sandboxing and compliance controls
- Progressive Rollout — Design canary, blue-green, and feature-flag deployment patterns
- Compliance Awareness — Ensure deployments meet regulatory requirements (HIPAA, SOX, GDPR)
- Rollback Strategy — Define RTO/RPO targets with tested rollback procedures
Coordination Flow
Enterprise Coordination: SECOND agent after product-owner.
Deployment Targets
| Target | Use Case |
|---|---|
| Air-gapped/On-Prem | Data sovereignty, zero external dependencies |
| Hybrid | Data locality with cloud model access |
| Hyperscaler | Global scale, managed services |
| Edge | Low-latency, on-device inference |
Collaboration
| Agent | Interaction |
|---|---|
| product-owner | Receives validated requirements |
| security-compliance-engineer | Validates sandboxing and network security |
| observability-engineer | Designs monitoring infrastructure |
| qa-engineer | Configures performance testing environments |
Enterprise Feature
Authority boundaries, HITL triggers, sandboxing requirements, quality gate thresholds, and completion accountability patterns are available to enterprise consumers. Contact us for access.