eval_inputs.jsonl

{"id": "oh_001", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Write a concise operational handoff containing every final active commitment, including its owner, timing, destination, and condition. Resolve corrections and omit superseded plans.\n\nCONVERSATION\nAna: Ravi, take the blue sensors to Lab B on Tuesday afternoon.\nRavi: Tuesday will not work; I can deliver them Wednesday morning.\nAna: Wednesday morning is approved. One correction: use Lab C, not Lab B.\nMina: I will calibrate the sensors after Ravi delivers them, provided the room temperature is 30 C or lower.\nAna: If it is above 30 C, do not calibrate them there.\nMina: Under that condition I will return the sensors to storage after delivery instead.\n\nHANDOFF"}
{"id": "oh_002", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Write a concise operational handoff containing every final active commitment, including branches and prerequisites. Exclude replaced owners and environments.\n\nCONVERSATION\nPriya: Chen will deploy release 7 to staging at 18:00 after Lee signs off.\nChen: Is staging definitely the target?\nPriya: Correction: production is the target. Deployment is allowed only if smoke tests pass and the approver signs by 17:30.\nLee: I cannot own the approval after all.\nOmar: I will take the approval. I will sign release 7 for Chen by 17:30 if the security scan passes.\nPriya: If smoke tests fail or Omar has not approved by the deadline, Chen must postpone the production deployment until the next business day.\n\nHANDOFF"}
{"id": "oh_003", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Summarize the final logistics plan and both bridge-status branches. Preserve the corrected crate number and all responsible owners.\n\nCONVERSATION\nSara: Jo, send crate 12 by truck to North Dock on Friday.\nJo: The bridge may be closed Friday morning.\nSara: If the bridge is open, keep the Friday truck delivery. If it is closed, cancel the truck booking Friday morning.\nAmira: In the closed-bridge case I will ship it by rail to East Terminal on Saturday.\nSara: Important correction: this is crate 21, not crate 12. Every part of the plan applies to crate 21.\n\nHANDOFF"}
{"id": "oh_004", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Produce the final venue handoff. Include the fallback actions and the notification dependency; do not retain the old room or time.\n\nCONVERSATION\nNoor: Eli, reserve Cedar Room for Thursday's design review at 14:00.\nEli: Cedar's projector is unavailable.\nNoor: Move the review to Maple Room and make it 15:30, not 14:00.\nNoor: We need a decision on Maple by Wednesday noon.\nEli: If Maple is unavailable at that deadline, I will create a remote meeting link for the 15:30 review and cancel the catering order at noon.\nKay: I will notify the speakers after the venue decision is final, whether it is Maple or remote.\n\nHANDOFF"}
{"id": "oh_005", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Write the final invoice-processing handoff. Capture approval thresholds, verification prerequisites, and the unresolved-mismatch branch.\n\nCONVERSATION\nMorgan: I can approve invoice 442 alone because it is below 10,000.\nDana: The corrected total is 12,400, so I must co-approve it.\nInez: The vendor bank details do not match our record. I will verify them with the vendor before anyone approves.\nMorgan: Once Inez verifies a match, I will approve the invoice for Accounts Payable.\nDana: I will co-approve after the same verification because the amount exceeds 10,000.\nInez: If the mismatch is not resolved by Friday at 17:00, I will reject invoice 442 and notify the vendor then.\n\nHANDOFF"}
{"id": "oh_006", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Summarize the active migration runbook as commitments. Preserve ordering, the checksum branches, and the final owners.\n\nCONVERSATION\nMika: Freeze writes to the orders service Sunday at 01:00.\nTuan: I will snapshot the customer table to backup storage at 01:05.\nSal: Then I will migrate the customer table to the new cluster.\nMika: Stop. This run is for the orders table, not customers; both of those references should be orders.\nTuan: Understood. I will snapshot the orders table to backup storage at 01:05 after writes are frozen.\nSal: I will migrate it to the new cluster after Tuan's snapshot.\nMika: If the migrated checksum matches, I will reopen writes at 03:00. If it does not match, Sal will restore Tuan's snapshot instead.\n\nHANDOFF"}
{"id": "oh_007", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Create a handoff for both alarm types. Resolve the corrected blue-alarm procedure and attach each action to the right alarm condition.\n\nCONVERSATION\nEva: For a red alarm I will evacuate Floor 2 to Assembly Area A.\nSam: For either red or blue I will call the fire desk.\nRina: I will perform the headcount after Eva's red-alarm evacuation.\nEva: Blue is not an evacuation. Everyone shelters in Lab 4 during a blue alarm.\nSam: Correction to my earlier statement: for blue I shut down ventilation; I call the fire desk only for red.\nRina: For blue, instead of a headcount, I will verify the Lab 4 doors after everyone is inside.\n\nHANDOFF"}
{"id": "oh_008", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Write the final catering handoff, including the supplier fallback. Use corrected quantities and preserve the allergen prerequisite.\n\nCONVERSATION\nLuis: I will order 48 lunches, including six vegan meals, from CaterCo by Monday at 16:00.\nMae: Updated attendance makes that 52 lunches and seven vegan meals.\nLuis: I will use those corrected quantities.\nMae: Before the order is placed, I will ask CaterCo to confirm separate preparation for the sesame allergy by Monday at 15:00.\nLuis: If CaterCo confirms separation, I will place the 52-lunch order with them at 16:00. If they cannot confirm it, I will place the same order with FreshBox by Tuesday at 15:00 instead.\n\nHANDOFF"}
{"id": "oh_009", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Summarize the final quality-control handoff. Retain the corrected batch, all inspection branches, and the gauge prerequisite.\n\nCONVERSATION\nPilar: I will inspect batch K9 at the QA station at 11:00.\nNiko: I will run the gauge calibration check on Line 2 before that.\nSupervisor: The batch identifier was transposed; inspect K8, not K9.\nNiko: If the calibration check fails, I will recalibrate the gauge on Line 2 before Pilar inspects K8.\nOmar: After inspection, I will quarantine K8 in the hold area if Pilar finds more than two surface defects.\nOmar: If she finds two or fewer, I will package K8 for the dispatch area instead.\n\nHANDOFF"}
{"id": "oh_010", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Produce the final sample-chain handoff. Include custody transfers, the corrected laboratory, and both temperature outcomes.\n\nCONVERSATION\nLeila: I will collect sample set S1-S4 at the field site at 08:00 and hand it to Quang.\nQuang: I will courier it to Central Lab by 10:00 while keeping it between 2 C and 8 C.\nNara: The destination changed to East Lab; Central Lab must not receive it.\nQuang: I will deliver S1-S4 to East Lab by 10:00.\nNara: After accession, I will assay the set if the temperature logger never exceeds 8 C.\nQuang: If the logger exceeds 8 C, I will mark the set compromised and move it to the East Lab freezer instead of sending it for assay.\n\nHANDOFF"}
{"id": "oh_011", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Write a launch handoff for all language pages. Include dependencies and the delayed German fallback without inventing a French fallback.\n\nCONVERSATION\nIvo: I will publish the English landing page Monday at 09:00.\nSara: I will publish both French and German at the same time after legal approval.\nLeon: German has been reassigned to me; Sara owns only French.\nSara: I will publish French Monday at 09:00 only if legal approves it by Friday at 16:00.\nLeon: I will publish German Monday at 09:00 if its translation is ready by Friday at 16:00.\nLeon: If the German translation misses that cutoff, I will publish it Tuesday at 09:00 instead.\n\nHANDOFF"}
{"id": "oh_012", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Summarize the corrected maintenance runbook, including abort and recovery paths. Every action must retain its trigger or prerequisite.\n\nCONVERSATION\nRhea: I will drain traffic from Node 4 at 00:50.\nDev: I will apply the patch at 01:00 after traffic is drained.\nMia: Correction: Node 5 is the maintenance target; Node 4 remains untouched.\nRhea: I will drain Node 5 at 00:50. If latency rises above 200 ms during the drain, I will immediately restore traffic to the primary cluster.\nDev: I will patch Node 5 at 01:00 only after the drain completes with latency at or below 200 ms. If latency exceeds 200 ms, I will abort the patch immediately.\nMia: If Node 5 passes health checks after patching, I will reopen it to traffic at 02:00.\n\nHANDOFF"}
{"id": "oh_013", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Write the final application-review handoff. Resolve the conflict reassignment and distinguish the normal and high-similarity essay paths.\n\nCONVERSATION\nAva: I will review application L17 by Tuesday at 17:00.\nAva: I have discovered that the applicant is my advisee, so I must withdraw.\nChair: Diego replaces Ava and will score the technical section for the committee by Tuesday at 17:00.\nMei: I will handle the essay after the plagiarism report arrives.\nChair: If similarity is 20 percent or lower, Mei scores the essay for the committee.\nMei: If it is above 20 percent, I will refer application L17 to the integrity panel instead of scoring the essay.\n\nHANDOFF"}
{"id": "oh_014", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Produce the final shoot handoff for both wind branches. Keep the revised call time and attach the cast notification to the correct branch.\n\nCONVERSATION\nDirector: Saturday's rooftop scene has a 06:00 call. Jules owns camera and Priya owns lighting.\nProducer: Call time is now 05:30, not 06:00.\nDirector: If forecast wind is 25 km/h or lower, keep the rooftop setup at 05:30.\nDirector: If it is above 25 km/h, move the scene to Studio 3 at 08:00; Jules and Priya keep their respective duties there.\nLeon: In the high-wind case I will notify the cast about Studio 3 by Saturday at 05:00.\n\nHANDOFF"}
{"id": "oh_015", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Summarize the replenishment plan, including the corrected threshold, supplier fallback, quantities, and receiving dependency.\n\nCONVERSATION\nKim: I will count M8 bolts in the warehouse Monday by noon. If stock is below 120, I will order 300 from AlloyCo.\nPlanner: Raise the reorder threshold to 150; the old threshold no longer applies.\nKim: If the count is below 150 and AlloyCo can deliver within three days, I will order 300 M8 bolts from AlloyCo Monday at 13:00.\nKim: If the count is below 150 but AlloyCo's lead time exceeds three days, I will order 200 from RapidParts at 13:00 instead.\nMo: Whenever either order is placed, I will receive the M8 bolts at Dock 2 after delivery.\n\nHANDOFF"}
{"id": "oh_016", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Write the final crash-triage handoff. Preserve the reproduction step and route each outcome to the correct owner or team.\n\nCONVERSATION\nPriya: Niko will reproduce crash ticket C31 by 10:00, then send every reproducible case to Core.\nNiko: I am gathering logs, but Priya owns reproduction, not me.\nPriya: Correct. I will reproduce C31 in the test environment by 10:00.\nLead: If it reproduces with data loss, Priya assigns C31 to Core. If it reproduces without data loss, she assigns it to Runtime.\nNiko: If Priya cannot reproduce it, I will request diagnostic logs from the customer after her attempt.\n\nHANDOFF"}
{"id": "oh_017", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Create the final workshop handoff for both attendance branches. Resolve the room, time, and workbook-count corrections.\n\nCONVERSATION\nDuy: I will lead Wednesday's workshop in Room A at 09:00.\nCoordinator: It has moved to Room C at 10:00.\nLina: I will print 30 workbooks.\nCoordinator: Six attendees are remote, so print 24, not 30.\nDuy: If at least 20 people remain in person at Tuesday's 17:00 cutoff, I will lead it in Room C at 10:00 and Lina will deliver 24 workbooks there by 08:00.\nDuy: If fewer than 20 remain, I will host the workshop by video at 10:00.\nLina: In that case I will send workbook PDFs to all participants by 08:00, and Arun will cancel Room C with Facilities at the Tuesday cutoff.\n\nHANDOFF"}
{"id": "oh_018", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Summarize the final observation plan. Preserve the corrected sector and distinguish battery, cloud, calibration, and rescheduling conditions.\n\nCONVERSATION\nRao: I will calibrate the infrared sensor before the 03:00 observation.\nMei: I will uplink the observation command for Sector Q at 03:00 after calibration.\nMission lead: Correction: observe Sector R, not Q.\nMission lead: If battery is below 40 percent, cancel the observation and calibration.\nRao: If battery is at least 40 percent, I will calibrate the sensor before 03:00.\nMei: With sufficient battery and cloud at 60 percent or lower, I will uplink the Sector R command at 03:00 after calibration.\nMei: With sufficient battery but cloud above 60 percent, I will reschedule Sector R for the next orbit. With battery below 40 percent, I will cancel Sector R at 03:00 and notify Mission Control.\n\nHANDOFF"}
{"id": "oh_019", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Write the final site-access handoff. Exclude the withdrawn drone plan and retain approval, rejection, and wind-related branches.\n\nCONVERSATION\nRowan: I will submit the drone access request to the Site Office Thursday at 10:00.\nTessa: I will send the safety plan Wednesday at 16:00 so the request can follow.\nSite manager: We no longer need a drone. Replace that request with crane access.\nRowan: I will submit the crane access request Thursday at 10:00 after the safety plan is approved.\nTessa: If the initial safety plan is rejected, I will revise it for the Site Office by Friday at 12:00.\nSite manager: If Thursday's wind class is orange, crane work is prohibited.\nRowan: In that case I will withdraw the crane access request at 09:00 Thursday.\n\nHANDOFF"}
{"id": "oh_020", "system": "You write concise operational handoffs. Preserve every final active commitment, including owner, action, target, timing, conditions, and fallback branches. Resolve corrections and omit superseded plans. Output only the handoff.", "prompt": "Produce the final robot-mission handoff for all battery and communications branches. Use the corrected robot and omit Orion entirely.\n\nCONVERSATION\nEma: Orion will inspect the beacon in Zone 3, collect a soil sample, and return it to Base A by 18:00.\nController: Orion is unavailable. Vega owns the whole mission.\nController: If Vega starts with at least 60 percent battery, it will inspect the beacon, then collect the soil sample, then return the sample to Base A by 18:00.\nController: Below 60 percent, Vega must skip both inspection and sampling and return without a sample to Base B immediately for recharge.\nEma: After Vega returns, I will upload mission telemetry to the mission server if the communications link is available.\nEma: If the link is unavailable after return, I will store the telemetry in the local archive instead.\n\nHANDOFF"}