AI Agent Orchestration Platform  ·  View 24 of 32  ·  5 · Operations

CI/CD and Environment Promotion

How a change reaches production, and what stops a bad one at each hop.

Editable source SVG draw.io All views
Source GitHub Repository platform + agents Pull Request two reviewers Bicep Modules infrastructure Build Container Build reproducible SBOM and Scan Defender · Trivy Image Signing Notation · KV key Verify Unit and Contract schema fixtures Policy Simulation Rego unit tests Golden Evaluation regression gate Red Team Suite injection probes Gate Development auto on merge Test eval score gate Staging load and soak Change Approval owner + security Deploy What-If Plan drift check Blue/Green Revision Container Apps Canary Weight 5 to 50 to 100 Watch SLO Watch 24 h window Online Quality success · escalation Auto Rollback prior revision score gate burn rate breach quality regression each step CI/CD and Environment Promotion Data store Decision point Application we own Security / platform synchronous failure / alternate Agent definitions travel the same pipeline as code. A prompt change is a versioned deployment, not a console edit. v 1.0 · owner Platform Engineering · date 2026-08

Decisions

  • Agent definitions, prompts, policies and infrastructure all travel the same pipeline as application code
  • Images and bundles are signed; the runtime refuses an unsigned or unknown-signer artifact
  • Rollback is automated on SLO burn rate and on quality regression, and does not wait for a human to notice

The gates

  • Development is automatic on merge; test requires a passing golden-evaluation score; staging requires load and soak
  • Production requires owner and security approval and enters at a 5 percent canary for 24 hours
  • Configuration is separated per environment and secrets are environment-scoped; no secret is ever in a definition

Risks

  • Golden evaluations are only as good as the dataset; a stale dataset gates nothing while appearing to
  • Blue/green on Container Apps revisions does not cover the durable state schema; state migrations are forward-compatible only and reviewed separately