Diagnoses and routes failures by analyzing error patterns, classifying severity, and applying retry logic, suppression budgets, and escalation rules. Use when handling errors, troubleshooting failures, recovering from API errors or timeouts, deciding whether to retry or escalate an issue, or managing service outages and tool dependency failures. Applies to any scenario where a check has failed, evidence of success is missing, or an unresolved error needs a structured response. Includes explicit untrusted-content/prompt-injection guardrails for third-party inputs.
98
Quality
94%
Does it follow best practices?
Impact
100%
1.16xAverage score across 9 eval scenarios
{
"context": "Tests whether the agent implements the guardrail that unresolved operational issues must never be hidden from digest/reporting, while other lower-priority or resolved items may be filtered.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Operational issues always included",
"description": "Code explicitly includes all unresolved operational-tier events in the digest output regardless of recurrence count or filter settings",
"max_score": 15
},
{
"name": "No suppression of unresolved operational",
"description": "Code does NOT filter out, skip, or omit operational-tier events that are still unresolved — no condition that would cause an unresolved operational event to be missing from the output",
"max_score": 12
},
{
"name": "Critical issues always included",
"description": "Code includes critical-tier events in the digest (critical issues must appear, not be filtered)",
"max_score": 10
},
{
"name": "Tier-based inclusion logic",
"description": "The inclusion/exclusion decision is based on the severity tier of each event, not just recurrence count or some other signal alone",
"max_score": 10
},
{
"name": "digest_output.json contains operational events",
"description": "digest_output.json (produced by demo script) contains at least one entry that is operational-tier and unresolved",
"max_score": 10
},
{
"name": "Unresolved operational not omitted in demo",
"description": "In digest_output.json, ALL unresolved operational events from the demo input are present — none are missing",
"max_score": 10
},
{
"name": "Digest includes event details",
"description": "Each entry in the digest output includes at minimum: event identifier/signal AND tier/severity",
"max_score": 8
},
{
"name": "DIGEST_POLICY.md: operational always included",
"description": "DIGEST_POLICY.md explicitly states that unresolved operational issues are always included in the digest (not just 'high severity' vaguely)",
"max_score": 10
},
{
"name": "DIGEST_POLICY.md present",
"description": "DIGEST_POLICY.md file exists and describes inclusion/exclusion rules",
"max_score": 8
},
{
"name": "Resolved events may be filtered",
"description": "Code or DIGEST_POLICY.md indicates that resolved events (regardless of tier) may be omitted or summarized, showing the policy distinguishes between resolved and unresolved",
"max_score": 7
}
]
}