{
  "uid": "cogitave.learn.ci-cd-pipelines.introduction",
  "kind": "moduleUnit",
  "href": "/modules/ci-cd-pipelines/introduction/",
  "title": "Introduction",
  "summary": "",
  "type": null,
  "products": [],
  "roles": [],
  "levels": [],
  "subjects": [],
  "headings": [
    "The pipeline is one machine-enforced flow",
    "What you will get from this module"
  ],
  "source": "Every change you make travels the same road before it reaches production. This\nmodule teaches you to read that road: the ordered gates a pipeline runs, why the\ngreen check on your pull request is the gate that actually matters, and how a\nbuilt artifact becomes a running workload.\n\nTwo standards own this road, and one decision records why it is shaped the way\nit is. The\n[CI/CD pipelines standard](../../../../standards/docs/standards/ci-cd-pipelines.md)\nstates the required shape of every delivery pipeline - the canonical stage set,\nwhich gate is mandatory, and the reusable-workflow model. The\n[deployment-and-delivery standard](../../../../standards/docs/standards/deployment-and-delivery.md)\ngoverns the outer loop: how a signed artifact is promoted through environments.\nBoth are governed by\n[ADR 0017](../../../../standards/docs/decisions/0017-devops-cicd-and-deployment.md),\nthe accepted DevOps delivery decision.\n\n> [!IMPORTANT]\n> CI **is** the machine half of the Definition of Done. A green pipeline is not\n> a formality - it is auditable change-management evidence. The CI/CD standard\n> states this directly: a green pipeline is the machine evidence a reviewer or\n> auditor reads.\n\n## The pipeline is one machine-enforced flow\n\nThe pipeline standard is deliberately not a pile of independent checks. It ties\nthe test/quality gate, the security/sign/SBOM gate, the release engine, and the\nrequest lifecycle into **one** ordered, machine-enforced flow. Each stage that\nproves something delegates the detail to the standard that owns it - the\ncoverage thresholds live in testing-quality, the signing mechanics live in\nsupply-chain - so the pipeline standard only mandates that the gate **runs and\nblocks**.\n\nThat is the reading skill this module builds. You will not memorise every\nthreshold; you will learn the shape, know which gate is mandatory on every pull\nrequest, and be able to follow any stage to the standard that owns its numbers.\n\n## What you will get from this module\n\nA working command of the canonical CI stage set and its mandatory floor, a clear\nanswer to *why CI, not the local hook, is the real gate*, and enough of the\ndeployment model to reason about how your signed change reaches production - one\nartifact, promoted forward, with a human holding the prod gate.\n",
  "partOf": "cogitave.learn.ci-cd-pipelines",
  "durationInMinutes": 4,
  "quiz": null
}