Work the request lifecycle
Move a change through the seven-stage request lifecycle, understand why the write tools only propose, and read the Definition of Done that decides when a request is actually done rather than merely worked on.
Units5
Duration23 min
Levelbeginner
By the end of this module, you'll be able to:
- Name the seven stages a Request moves through and say what advances each one.
- Explain why the two write tools are propose-only, and what propose-only rules out.
- Read the Definition of Done and tell when a Request is actually done, not just worked on.
- Identify the human gate - the consequential transition an agent proposes but never enacts.
Prerequisites
- Familiarity with the org's non-negotiable rules (the AGENTS floor) and the propose-only way of working.
- Basic familiarity with Git, issues, and pull requests.
Units
- 01Introduction4 min
- 02The seven lifecycle stages6 min
- 03The Definition of Done6 min
- 04Knowledge check4 min
- 05Summary3 min
Related
- Inherit the project baseline How a new repository is born on the paved road with its whole ruleset already inherited, how to tell always-on standards from the ones a product type pulls in, and how to find an existing pattern before writing anything new.
- Open your first pull request Apply an AI-native org's floor, its inherited baseline, and the request lifecycle in one hands-on contribution - a signed, Conventional-Commit, docs-complete pull request that passes the gates and stops for human review.
- Apply a non-negotiable floor An AI-native org runs on a small floor every human and agent obeys. Study Cogitave's floor - its seven non-negotiable rules and what enforces each, from a commit-msg hook to policy-as-code - then apply a floor like it to your own first change.