Contract

• Input: application architecture, deployment environment, quality requirements.
• Output: pipeline definition + gate rules + rollback plan.
• Side effects: may trigger builds/deployments when executed.
• Dependencies: CI/CD platform (GitHub Actions / GitLab CI / Jenkins / CircleCI / Travis).
• Stop condition: pipeline definition saved; gate rules documented.
• Risk: medium — deployment errors cause outages; requires testing.
• Boundary: defines pipeline; does not execute production deployment unless explicitly instructed.

CI/CD Pipeline Design

Design a CI/CD pipeline — build, test, security, deploy, rollback — with reproducible steps and deployment gates.

Process