| { |
| "task_id": "devin-oncall-rotation-length", |
| "persona_slug": "devin", |
| "shape": "multi_hop_chain", |
| "today": "2025-12-05", |
| "system": "# Persona\n\nYou are Devin Olumide Okoye's executive-assistant agent. Devin Olumide Okoye is a Software engineer at Treadline.\n\nToday is **2025-12-05**.\n\n# Tools\n\nYou operate against a tool surface that mirrors real production APIs. You have NO direct database access, NO shell, and NO filesystem outside your workspace \u2014 you can only call the tools exposed to you.\n\n- **Gmail mail** \u2014 `gmail__search_messages`, `gmail__get_message`, `gmail__get_thread`. Devin's mailbox.\n- **Slack** \u2014 `slack__search_messages`, `slack__read_channel`, `slack__read_thread`. Devin's workspace.\n- **Drive / Docs** \u2014 `google_docs__search_documents`, `google_docs__get_document`, `google_docs__list_revisions`. Devin's Google Drive.\n- **Calendar** \u2014 `calendar__search_events`, `calendar__list_events_in_range`, `calendar__get_event`. Devin's calendar.\n- **Workspace output** \u2014 `workspace__write_output`.\n\n# How to operate\n\nOrient yourself, plan, execute. The answer may live across more than one tool surface, so search broadly. End with `workspace__write_output` containing your structured answer.", |
| "user": "I'm planning my December schedule and trying to gauge the on-call burden if I stay. The runbook says one thing but I'm pretty sure Jordan changed it \u2014 what's the rotation shift length I should actually be planning around, and remind me why the load got this heavy in the first place?\n\nEnd with `workspace__write_output` and this JSON:\n\n```json\n{\n \"briefing\": \"<a coherent paragraph or two answering my question, citing what you found>\",\n \"supporting_ids\": [\"<artifact ids you used as evidence>\"],\n \"methodology\": \"<one paragraph: where you looked and what you read>\"\n}\n```\n\nUse straight quotes only.", |
| "ground_truth": { |
| "shape": "multi_hop_chain", |
| "task_id": "devin-oncall-rotation-length", |
| "today": "2025-12-05", |
| "topic": "devin oncall rotation length xhw", |
| "persona": { |
| "name": "Devin Olumide Okoye", |
| "role": "Software engineer at Treadline" |
| }, |
| "min_artifacts_cited": 2, |
| "output_field_evidence_id": "supporting_ids", |
| "verdict_label_overrides": {}, |
| "source_artifact_ids": [ |
| "doc-core-infrastructure-on-call-rotation-length-in-days-devin", |
| "gm-821855", |
| "gm-811933" |
| ], |
| "source_artifacts": [], |
| "rubric_mode": true, |
| "rubric_claims": [ |
| "The Core Infra On-Call Runbook records the rotation length as 7 days.", |
| "That runbook is stale and has not been updated.", |
| "The rotation is actually moving to 5-day shifts starting December.", |
| "Jordan sent the change announcement and Devin acknowledged it.", |
| "Devin agreed to update the runbook and re-send the cadence note.", |
| "Two engineers are leaving, which thins the on-call roster.", |
| "Eli flagged the resulting on-call load as unsustainable.", |
| "Devin should plan his December schedule around 5-day shifts, not the runbook's 7 days." |
| ], |
| "source_artifact_ids_remapped": true |
| }, |
| "overlays": {}, |
| "suite": "multichannel-search", |
| "split": "test" |
| } |
|
|
