#33 Explain the incident severity levels on the incidents page

Every step from GitLab's own records: the issue, its merge request and their label history.

1. Filed A visitor, on this site

   Screened and filed as a GitLab issue.

   22 Oct, 08:29 UTC

2. Triage accepted Triage agent ai-shipyard-triage-gitlab-ai-hackathon

   Wrote the acceptance criteria. Record

   22 Oct, 08:30 UTC · 1 min 2 s later

3. Build started Dispatcher

   Started the build agent with the criteria.

   22 Oct, 08:30 UTC · 3 s later

4. Merge request opened Build agent

   Explain High and Medium severity on the incidents page Record

   22 Oct, 08:33 UTC · 2 min 21 s later

5. In review Dispatcher

   Every test and scan passed; the review agent started.

   22 Oct, 08:35 UTC · 1 min 55 s later

6. Approved Review agent ai-shipyard-review-gitlab-ai-hackathon

   Checked against the criteria.

   22 Oct, 08:36 UTC · 1 min 3 s later

7. Merged Dispatcher

   Merged at the reviewed commit, with a release decision record. Record

   22 Oct, 08:36 UTC · 9 s later

8. On staging Pipeline

   Merged, deployed to staging and smoke-tested.

   22 Oct, 08:40 UTC · 4 min 24 s later

9. Asked a human Dispatcher

   Automation stopped and asked for help.

   22 Oct, 08:43 UTC · 2 min 23 s later

10. Live Pipeline

    Passed a canary and a 60-second watch in production.

    22 Oct, 08:43 UTC · 0 s later

Why it was safe to merge

What the dispatcher verified before merging, from its release decision record (open it).

• Pipeline ✅ #2975528152 passed at 1f4e7fa1: 12 jobs
• Tests ✅ 442 passed, 0 failed
• Security gate ✅ no blocking findings after SAST, secret detection, dependency audit, image scan, licences and SBOM
• Scope policy ✅ 2 files changed, all inside the agent scope
• Authority boundary ✅ protected policy tests passed
• Review ✅ review::approved added by ai-shipyard-review-gitlab-ai-hackathon (the review flow's own account), verified in GitLab's label history
• GitLab approval ✅ approval rule satisfied at 1f4e7fa1
• Scope of work ✅ closes #33; reviewed against the triage agent's acceptance criteria
• Fix attempts · none needed