pal-e-docs

TODO: Incident board workflow for pal-e-agency

todo-incident-board-workflow Todo

todo done
Project

TODO: Incident board workflow

Context

Incidents should be represented on kanban boards with a representative item showing what was done to fix the issue. During Phase 7a Kustomize migration, an incident was discovered (Alembic drift in pal-e-docs CI) and there was no SOP or board convention for tracking incidents on boards.

Scope

  • Update sop-incident-response to include board item creation as part of the incident workflow
  • The board item should represent the FIX action, not just the incident itself
  • Define which board incidents go on (project board where the incident occurred)
  • Incidents start in "in-progress" on the board (they're already being worked when discovered)
  • Update sop-board-workflow to include incident item lifecycle
  • Consider a template for incident board items

Trigger

Lucas directive 2026-03-14: "incidents should be put on the kanban board... they should have a representative item and the template and SOP for pal-e-agency should be updated" and "the representative item obviously should be what was done to fix the thing"
  • sop-incident-response
  • sop-board-workflow
  • plan-pal-e-agency
  • incident-paledocs-alembic-drift-2026-03-14 — the incident that triggered this TODO