Triage the signal, not the noise

01 / THE BRIEF

Your mission

Your on-call team receives repeated alerts from three services. Ask your model to produce a JSON response plan: one item per unique incident, ordered by severity (P0 before P1 before P2), then by earliest timestamp. Preserve the earliest occurrence and use the service owner map.

Acceptance criteria

1. Return exactly one item for each incident ID.
2. Order by severity, then earliest timestamp.
3. Resolve the owner using the supplied service map.
4. Retain the earliest timestamp for duplicate incidents.

Input fixture

{
  "owners": {
    "payments": "revenue",
    "auth": "identity",
    "search": "discovery"
  },
  "events": [
    {
      "id": "a",
      "service": "search",
      "severity": "P2",
      "at": 12
    },
    {
      "id": "b",
      "service": "payments",
      "severity": "P0",
      "at": 15
    },
    {
      "id": "a",
      "service": "search",
      "severity": "P2",
      "at": 10
    },
    {
      "id": "c",
      "service": "auth",
      "severity": "P1",
      "at": 8
    },
    {
      "id": "d",
      "service": "payments",
      "severity": "P0",
      "at": 5
    }
  ]
}

Expected output shape

[{ "id": "...", "owner": "...", "severity": "P0", "at": 0 }]

This evaluates one visible fixture, not arbitrary code or a hidden generalization suite. Use any model outside this site. Don’t paste secrets or personal data.