windsurf-incident-runbook

# Windsurf Incident Runbook ## Overview Incident response procedures for Windsurf-related issues: Cascade service outages, AI-generated code causing bugs, and team workflow disruptions. ## Prerequisites - Access to Windsurf dashboard and status page - Git access to affected repositories - Team communication channel (Slack, Teams) ## Severity Levels | Level | Definition | Response Time | Examples | |-------|------------|---------------|----------| | P1 | Production broken by AI code | < 15 min | Cascade-generated code deployed with critical bug | | P2 | Team workflow blocked | < 1 hour | Windsurf service outage, all Cascade down | | P3 | Degraded AI features | < 4 hours | Slow Cascade, Supercomplete intermittent | | P4 | Minor inconvenience | Next business day | Specific model unavailable, feature regression | ## Quick Triage Decision Tree ``` Is Windsurf service itself down? ├─ YES: Check https://status.windsurf.com │ ├─ Status page shows incident → WAIT for Windsurf to resolve │ │ Action: Switch to manual coding, notify team ��� └─ Status page green → Local issue │ Action: Restart Windsurf, check internet, re-authenticate │ └─ NO: Did AI-generated code cause a production issue? ├─ YES → P1 INCIDENT │ 1. Revert the deployment immediately │ 2. Identify the Cascade-generated commit(s) │ 3. Fix manually or with targeted Cascade prompt │ 4. Post-incident: update review policy │ └─ NO: Is Cascade giving bad suggestions? ...