[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.

CONVERSATION
Ana: Ravi, take the blue sensors to Lab B on Tuesday afternoon.
Ravi: Tuesday will not work; I can deliver them Wednesday morning.
Ana: Wednesday morning is approved. One correction: use Lab C, not Lab B.
Mina: I will calibrate the sensors after Ravi delivers them, provided the room temperature is 30 C or lower.
Ana: If it is above 30 C, do not calibrate them there.
Mina: Under that condition I will return the sensors to storage after delivery instead.

HANDOFF


prompt:
Write a concise operational handoff containing every final active commitment, including branches and prerequisites. Exclude replaced owners and environments.

CONVERSATION
Priya: Chen will deploy release 7 to staging at 18:00 after Lee signs off.
Chen: Is staging definitely the target?
Priya: Correction: production is the target. Deployment is allowed only if smoke tests pass and the approver signs by 17:30.
Lee: I cannot own the approval after all.
Omar: I will take the approval. I will sign release 7 for Chen by 17:30 if the security scan passes.
Priya: If smoke tests fail or Omar has not approved by the deadline, Chen must postpone the production deployment until the next business day.

HANDOFF


prompt:
Summarize the final logistics plan and both bridge-status branches. Preserve the corrected crate number and all responsible owners.

CONVERSATION
Sara: Jo, send crate 12 by truck to North Dock on Friday.
Jo: The bridge may be closed Friday morning.
Sara: If the bridge is open, keep the Friday truck delivery. If it is closed, cancel the truck booking Friday morning.
Amira: In the closed-bridge case I will ship it by rail to East Terminal on Saturday.
Sara: Important correction: this is crate 21, not crate 12. Every part of the plan applies to crate 21.

HANDOFF


prompt:
Produce the final venue handoff. Include the fallback actions and the notification dependency; do not retain the old room or time.

CONVERSATION
Noor: Eli, reserve Cedar Room for Thursday's design review at 14:00.
Eli: Cedar's projector is unavailable.
Noor: Move the review to Maple Room and make it 15:30, not 14:00.
Noor: We need a decision on Maple by Wednesday noon.
Eli: 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.
Kay: I will notify the speakers after the venue decision is final, whether it is Maple or remote.

HANDOFF


prompt:
Write the final invoice-processing handoff. Capture approval thresholds, verification prerequisites, and the unresolved-mismatch branch.

CONVERSATION
Morgan: I can approve invoice 442 alone because it is below 10,000.
Dana: The corrected total is 12,400, so I must co-approve it.
Inez: The vendor bank details do not match our record. I will verify them with the vendor before anyone approves.
Morgan: Once Inez verifies a match, I will approve the invoice for Accounts Payable.
Dana: I will co-approve after the same verification because the amount exceeds 10,000.
Inez: If the mismatch is not resolved by Friday at 17:00, I will reject invoice 442 and notify the vendor then.

HANDOFF


prompt:
Summarize the active migration runbook as commitments. Preserve ordering, the checksum branches, and the final owners.

CONVERSATION
Mika: Freeze writes to the orders service Sunday at 01:00.
Tuan: I will snapshot the customer table to backup storage at 01:05.
Sal: Then I will migrate the customer table to the new cluster.
Mika: Stop. This run is for the orders table, not customers; both of those references should be orders.
Tuan: Understood. I will snapshot the orders table to backup storage at 01:05 after writes are frozen.
Sal: I will migrate it to the new cluster after Tuan's snapshot.
Mika: If the migrated checksum matches, I will reopen writes at 03:00. If it does not match, Sal will restore Tuan's snapshot instead.

HANDOFF


prompt:
Create a handoff for both alarm types. Resolve the corrected blue-alarm procedure and attach each action to the right alarm condition.

CONVERSATION
Eva: For a red alarm I will evacuate Floor 2 to Assembly Area A.
Sam: For either red or blue I will call the fire desk.
Rina: I will perform the headcount after Eva's red-alarm evacuation.
Eva: Blue is not an evacuation. Everyone shelters in Lab 4 during a blue alarm.
Sam: Correction to my earlier statement: for blue I shut down ventilation; I call the fire desk only for red.
Rina: For blue, instead of a headcount, I will verify the Lab 4 doors after everyone is inside.

HANDOFF


prompt:
Write the final catering handoff, including the supplier fallback. Use corrected quantities and preserve the allergen prerequisite.

CONVERSATION
Luis: I will order 48 lunches, including six vegan meals, from CaterCo by Monday at 16:00.
Mae: Updated attendance makes that 52 lunches and seven vegan meals.
Luis: I will use those corrected quantities.
Mae: Before the order is placed, I will ask CaterCo to confirm separate preparation for the sesame allergy by Monday at 15:00.
Luis: 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.

HANDOFF


prompt:
Summarize the final quality-control handoff. Retain the corrected batch, all inspection branches, and the gauge prerequisite.

CONVERSATION
Pilar: I will inspect batch K9 at the QA station at 11:00.
Niko: I will run the gauge calibration check on Line 2 before that.
Supervisor: The batch identifier was transposed; inspect K8, not K9.
Niko: If the calibration check fails, I will recalibrate the gauge on Line 2 before Pilar inspects K8.
Omar: After inspection, I will quarantine K8 in the hold area if Pilar finds more than two surface defects.
Omar: If she finds two or fewer, I will package K8 for the dispatch area instead.

HANDOFF


prompt:
Produce the final sample-chain handoff. Include custody transfers, the corrected laboratory, and both temperature outcomes.

CONVERSATION
Leila: I will collect sample set S1-S4 at the field site at 08:00 and hand it to Quang.
Quang: I will courier it to Central Lab by 10:00 while keeping it between 2 C and 8 C.
Nara: The destination changed to East Lab; Central Lab must not receive it.
Quang: I will deliver S1-S4 to East Lab by 10:00.
Nara: After accession, I will assay the set if the temperature logger never exceeds 8 C.
Quang: 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.

HANDOFF


prompt:
Write a launch handoff for all language pages. Include dependencies and the delayed German fallback without inventing a French fallback.

CONVERSATION
Ivo: I will publish the English landing page Monday at 09:00.
Sara: I will publish both French and German at the same time after legal approval.
Leon: German has been reassigned to me; Sara owns only French.
Sara: I will publish French Monday at 09:00 only if legal approves it by Friday at 16:00.
Leon: I will publish German Monday at 09:00 if its translation is ready by Friday at 16:00.
Leon: If the German translation misses that cutoff, I will publish it Tuesday at 09:00 instead.

HANDOFF


prompt:
Summarize the corrected maintenance runbook, including abort and recovery paths. Every action must retain its trigger or prerequisite.

CONVERSATION
Rhea: I will drain traffic from Node 4 at 00:50.
Dev: I will apply the patch at 01:00 after traffic is drained.
Mia: Correction: Node 5 is the maintenance target; Node 4 remains untouched.
Rhea: 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.
Dev: 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.
Mia: If Node 5 passes health checks after patching, I will reopen it to traffic at 02:00.

HANDOFF


prompt:
Write the final application-review handoff. Resolve the conflict reassignment and distinguish the normal and high-similarity essay paths.

CONVERSATION
Ava: I will review application L17 by Tuesday at 17:00.
Ava: I have discovered that the applicant is my advisee, so I must withdraw.
Chair: Diego replaces Ava and will score the technical section for the committee by Tuesday at 17:00.
Mei: I will handle the essay after the plagiarism report arrives.
Chair: If similarity is 20 percent or lower, Mei scores the essay for the committee.
Mei: If it is above 20 percent, I will refer application L17 to the integrity panel instead of scoring the essay.

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.

CONVERSATION
Director: Saturday's rooftop scene has a 06:00 call. Jules owns camera and Priya owns lighting.
Producer: Call time is now 05:30, not 06:00.
Director: If forecast wind is 25 km/h or lower, keep the rooftop setup at 05:30.
Director: If it is above 25 km/h, move the scene to Studio 3 at 08:00; Jules and Priya keep their respective duties there.
Leon: In the high-wind case I will notify the cast about Studio 3 by Saturday at 05:00.

HANDOFF


prompt:
Summarize the replenishment plan, including the corrected threshold, supplier fallback, quantities, and receiving dependency.

CONVERSATION
Kim: I will count M8 bolts in the warehouse Monday by noon. If stock is below 120, I will order 300 from AlloyCo.
Planner: Raise the reorder threshold to 150; the old threshold no longer applies.
Kim: 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.
Kim: If the count is below 150 but AlloyCo's lead time exceeds three days, I will order 200 from RapidParts at 13:00 instead.
Mo: Whenever either order is placed, I will receive the M8 bolts at Dock 2 after delivery.

HANDOFF


prompt:
Write the final crash-triage handoff. Preserve the reproduction step and route each outcome to the correct owner or team.

CONVERSATION
Priya: Niko will reproduce crash ticket C31 by 10:00, then send every reproducible case to Core.
Niko: I am gathering logs, but Priya owns reproduction, not me.
Priya: Correct. I will reproduce C31 in the test environment by 10:00.
Lead: If it reproduces with data loss, Priya assigns C31 to Core. If it reproduces without data loss, she assigns it to Runtime.
Niko: If Priya cannot reproduce it, I will request diagnostic logs from the customer after her attempt.

HANDOFF


prompt:
Create the final workshop handoff for both attendance branches. Resolve the room, time, and workbook-count corrections.

CONVERSATION
Duy: I will lead Wednesday's workshop in Room A at 09:00.
Coordinator: It has moved to Room C at 10:00.
Lina: I will print 30 workbooks.
Coordinator: Six attendees are remote, so print 24, not 30.
Duy: 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.
Duy: If fewer than 20 remain, I will host the workshop by video at 10:00.
Lina: 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.

HANDOFF


prompt:
Summarize the final observation plan. Preserve the corrected sector and distinguish battery, cloud, calibration, and rescheduling conditions.

CONVERSATION
Rao: I will calibrate the infrared sensor before the 03:00 observation.
Mei: I will uplink the observation command for Sector Q at 03:00 after calibration.
Mission lead: Correction: observe Sector R, not Q.
Mission lead: If battery is below 40 percent, cancel the observation and calibration.
Rao: If battery is at least 40 percent, I will calibrate the sensor before 03:00.
Mei: With sufficient battery and cloud at 60 percent or lower, I will uplink the Sector R command at 03:00 after calibration.
Mei: 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.

HANDOFF


prompt:
Write the final site-access handoff. Exclude the withdrawn drone plan and retain approval, rejection, and wind-related branches.

CONVERSATION
Rowan: I will submit the drone access request to the Site Office Thursday at 10:00.
Tessa: I will send the safety plan Wednesday at 16:00 so the request can follow.
Site manager: We no longer need a drone. Replace that request with crane access.
Rowan: I will submit the crane access request Thursday at 10:00 after the safety plan is approved.
Tessa: If the initial safety plan is rejected, I will revise it for the Site Office by Friday at 12:00.
Site manager: If Thursday's wind class is orange, crane work is prohibited.
Rowan: In that case I will withdraw the crane access request at 09:00 Thursday.

HANDOFF


prompt:
Produce the final robot-mission handoff for all battery and communications branches. Use the corrected robot and omit Orion entirely.

CONVERSATION
Ema: Orion will inspect the beacon in Zone 3, collect a soil sample, and return it to Base A by 18:00.
Controller: Orion is unavailable. Vega owns the whole mission.
Controller: 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.
Controller: Below 60 percent, Vega must skip both inspection and sampling and return without a sample to Base B immediately for recharge.
Ema: After Vega returns, I will upload mission telemetry to the mission server if the communications link is available.
Ema: If the link is unavailable after return, I will store the telemetry in the local archive instead.

HANDOFF