Summary Incident Response

The model receives the prompt (and optional system message). The run uses scorer contains_all with the JSON configuration below. Pass/fail and partial credit are determined entirely by that scorer against the model output; no human grading.

Summarize in exactly 3 short bullet points:
During a high-traffic incident, the team reduced error rates by enabling graceful degradation, shifted read-heavy traffic to replicas, and paused non-critical background jobs. They also assigned an incident commander, updated stakeholders every 15 minutes, and tracked follow-up actions in a postmortem.

{
  "expected_contains": [
    "graceful degradation",
    "replicas",
    "incident commander"
  ]
}