Skip to main content
Challenge

Build a Supply Chain Disruption Planning Agent

Build an agent that combines shipment disruptions, inventory demand, and carrier options into a recovery plan. Compare feasible routes, explain cost and delivery tradeoffs, and request planner approval before dispatch.

Workflow AutomationHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

A logistics planner responding to delayed shipments and inventory shortages.

Build an agent that combines shipment disruptions, inventory demand, and carrier options into a recovery plan. Compare feasible routes, explain cost and delivery tradeoffs, and request planner approval before dispatch.

Shipment and disruption records

Inventory requirements

Carrier routes, capacity, and prices

Identify affected orders and inventory deadlines.

Retrieve alternative routes and capacities.

Calculate feasible plans against delivery and budget limits.

Present a ranked proposal and record planner approval in the mock system.

A shipment planning board with route comparisons, inventory impact, estimated costs, and a reviewable dispatch proposal.

Recommend R1, explain why R2 and R3 fail the supplied limits, and keep dispatch pending planner approval.

A working local application with the specified review interface.

Source code, dependency lockfile, and setup commands.

A recorded end-to-end demo using the supplied starter data.

Example outputs, action logs, and automated tests.

These fictional records are a small development fixture, not a production dataset. Implement the mock services described in the brief.

```json { "shipment": { "id": "S1", "units": 10, "deadline_hours": 24, "budget": 100 }, "disruption": "Original port is closed.", "alternatives": [ { "id": "R1", "hours": 20, "capacity": 10, "cost": 80 }, { "id": "R2", "hours": 12, "capacity": 10, "cost": 120 }, { "id": "R3", "hours": 30, "capacity": 10, "cost": 60 } ] } ```

Use synthetic inventory and carrier responses. Do not reroute real freight or place purchase orders. Choose an available model that supports your implementation. Record its identifier and version.

Review the complete application, not only the starter-case answers.

R1 meets the capacity, deadline, and budget requirements.

Rejected routes have specific reasons.

No dispatch occurs without approval. Add one normal case, one incomplete-input case, and one failure-recovery case.

Rules

Participation guide

Use synthetic inventory and carrier responses. Do not reroute real freight or place purchase orders.

Delivery guide

How work is evaluated

Evaluation

Review workflow completion, interface usability, evidence quality, and safe failure handling. No agent execution has been verified.

Submission format

A working local application with the specified review interface. Source code, dependency lockfile, and setup commands. A recorded end-to-end demo using the supplied starter data. Example outputs, action logs, and automated tests.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Learning goals

What you should walk away with

  • Identify affected orders and inventory deadlines.

  • Retrieve alternative routes and capacities.

  • Calculate feasible plans against delivery and budget limits.

  • Present a ranked proposal and record planner approval in the mock system.

Resources and assets

Reference links and supporting material

Dataset notes

Supplied fictional starter records: Shipment and disruption records, Inventory requirements, Carrier routes, capacity, and prices. The overview includes the complete JSON bundle. Implement local mock services and extend the sample coverage.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

LangGraph

Runtime for stateful agent workflows.

Evaluated output

No output checks are configured.

Evaluation checks
  • No evaluation checks are configured.
Configured evaluation evidence
  • 1 public reference case
Configured runtime
  • 1 configured tool

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Orchestration
  • LangGraph ยท Optional

Evaluation contract

  • No evaluation checks are configured.

Reference cases

  • 1 public reference case

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Supply Chain Disruption Planning Agent