{
  "uid": "cogitave.learn.work-the-request-lifecycle.introduction",
  "kind": "moduleUnit",
  "href": "/modules/work-the-request-lifecycle/introduction/",
  "title": "Introduction",
  "summary": "",
  "type": null,
  "products": [],
  "roles": [],
  "levels": [],
  "subjects": [],
  "headings": [
    "The one rule to carry in",
    "What you will get from this module"
  ],
  "source": "An AI-native org routes **every** change - a feature, a fix, a doc, an infra\ntweak, a dependency bump - through **one** process. That process is not a habit\nor a team convention; it is written down, and it is the authority the automation\nimplements. Cogitave's own estate works this way, and this module uses its\nlifecycle as the worked example you can copy for your own org.\n\nA unit of change is a **Request**: a first-class node in the org's canonical\nmodel, addressed by a stable id, just like an `Agent` or a `Doc`. (In Cogitave's\nCore that node reads `cogitave://request/{id}`.) Humans and agents drive the\n*same* Request through the *same* stages over MCP, so \"what state is this change\nin, and why\" is a single query an auditor can answer. Cogitave records the\ncanonical description of those stages in\n[`LIFECYCLE.md`](../../../../agents/lifecycle/LIFECYCLE.md) - this module teaches\nyou to read and use a lifecycle document like it, not to memorise a paraphrase of\nit.\n\n## The one rule to carry in\n\nThe lifecycle does not invent policy; it **sequences** the floor you already\nlearned into auditable stages. The rule that shapes everything else is\n**propose-only**:\n\n> [!IMPORTANT]\n> Agents draft, classify, comment, and open issues and PRs. They **never** merge,\n> apply, release, or write a protected branch. The consequential action is held\n> for a human. Propose is not approve; approve is not deploy.\n\nThat is why the whole process has exactly **two write tools**, and why neither of\nthem can change the world on its own. You will see what they do - and do not do -\nin the next unit.\n\n## What you will get from this module\n\nNot a checklist to obey blindly - a working model of how a change travels from an\nidea to `done`: the seven stages and what advances each, why the write tools only\npropose, and how to read the **Definition of Done** so you can tell when a Request\nis genuinely finished versus merely worked on.\n",
  "partOf": "cogitave.learn.work-the-request-lifecycle",
  "durationInMinutes": 4,
  "quiz": null
}