How the change-request check works
A pull request (GitHub) or merge request (GitLab) has to cite existing, non-retired records, so a retired decision cannot come back through a merge.
For: Team developer, Project lead, Tester
What it checks
| The change request… | Result |
|---|---|
| cites no record code | Fails, unless it has the label no-requirement |
| cites only a story or task code | Fails: the work code links the change, but a record code is needed |
| cites a code that does not exist | Fails |
| cites a Retired record | Fails |
| cites a Draft or Approved record | Passes with a warning |
| cites only Authority records | Passes |
Set it up
- Run
/corpole:initand accept the CI check (GitHub Action or GitLab CI include), or copy it from Agents → Repository kit. - Create a service token on the solution's Agents page.
- Add it as
CORPOLE_TOKEN: a repository secret on GitHub, a masked CI/CD variable on GitLab.
Why it matters
Agents write most of the change requests. The check makes each one say which requirement it serves, and stops work built on a requirement you already retired.