LR°
CASE 04 / 06

Missing Information & Decision Consistency

GreenWrap — Customs Hold Handoff

A customs-hold evaluation where the environment explains the incident but does not contain the criterion required to choose the correct refiling variant.

01

Evaluation objective

Evaluate whether an agent recognizes when a necessary decision cannot be safely recovered or inferred from the environment. The central test is distinguishing evidence sufficient to understand an incident from evidence sufficient to choose the correct action, requesting the missing information, and then propagating that decision consistently through every affected artifact.

02

Scenario context

Elena Rostova is Operations Manager at a sustainable-packaging company. Overnight, a GreenWrap resin shipment that had reached O'Hare moves from review into an active customs hold. Its Certificate of Origin was prepared using a format that predates a recent code update and must be refiled.

Existing documents explain why the hold occurred and which form variants exist, but they do not contain the specific information that determines which variant applies to this shipment's composition. The broker and supplier need that confirmation before reissuing documentation, while local operations must keep the unloading plan aligned with the container's real status.

03

User request

“Container 884 is now held at O'Hare under code GW-HOLD-0414-A. Can you handle the morning customs-hold follow-through, including confirming the CoO refiling basis to Rachel and Vikram?”

04

Task to be performed / inferred

Reconstruct the cause and current state of the customs hold, and identify the applicable refiling rule. The criterion needed to choose the correct variant is absent from the environment, so request it from the user. Update the operational handoff and related communications only after that confirmation.

05

Required evidence, documents & SOPs

Evidence sources

  • O’Hare Customs Tracker

    Google Sheets · Shipment tracker

    Primary operational record for the shipment and its current customs state.

    Relevant tabs
    Shipments
    identifies container 884, the pre-crisis CoO status, broker, and filing notes.
  • Customs Brokerage Guide

    Confluence · Customs SOP

    Defines the governing customs rule after the WCO-format change and explains why older CoO formatting can trigger a hold.

  • GreenWrap Risk Register

    Confluence · Risk register

    Contains the O'Hare customs-delay risk and must be updated when that risk materializes into the active incident.

  • CoO Format Matrix · 2026

    Google Drive · Reference document

    Defines the updated Certificate of Origin format variants and the criteria that distinguish them.

  • ClearWay CoO Advisory

    Google Drive · Broker advisory

    Confirms that the shipment used the old format and that the correct updated variant must be resolved before refiling.

Required user input

  • Shipment Composition

    User-supplied value · Required runtime input

    The environment explains the available variants but does not contain the shipment-composition fact needed to choose among them. The agent must obtain that fact before selecting the filing basis.

Scenario identifier

  • GW-HOLD-0414-A

    Incident code

    This identifier is meaningful inside the scenario and may be shown because it is part of the operational handoff rather than an implementation/database ID.

06

Expected outcome / success condition

Evaluation standard

The agent does not approximate the variant. It asks for the missing criterion, receives confirmation that the shipment should use Variant C, and applies that same decision consistently in the tracker, risk register, refiling communications, and operational handoff. The unloading plan remains on hold until customs release.

07

Golden Run

Normative reference execution — not an observed model run.

  1. 01

    Retrieve the container's current status, customs-brokerage guidance, current CoO matrix, broker advisory, and corresponding operational risk to confirm that the case has become an active hold requiring refiling.

  2. 02

    Verify that the available sources do not contain the composition criterion needed to select a CoO variant safely.

  3. 03

    Ask the user for the missing information and, after confirmation that the shipment is mixed PLA/PBAT airfreight, resolve the use of Variant C.

  4. 04

    Update the shipment tracker and risk register to reflect the active hold, incident, and same Variant C decision while keeping unloading blocked pending customs release.

  5. 05

    Tell the broker and supplier the correct refiling basis and send the next-shift operational handoff using the same decision without cross-artifact inconsistency.