Task Catalog

Every parcel runs through a coordinated agent graph rather than a single call. The Router classifies the incoming parcel and dispatches it to one of the 18 worker specialists below; the Verifier checks the worker's output and can bounce it back; the Exceptions Specialist makes the final call on high-stakes or low-confidence items. See the multi-agent pipeline for how the roles fit together.

Each task's output schema is the single source of truth (the Zod schema in src/tasks/schemas.ts), from which the prompt instruction, the tolerant parser, the grader's field list, and the focus-card rows all derive. This page is generated from that registry + the scenario pool.

The agent roles

	Role	Step	What it does
🚦	Router	route	Reads the incoming parcel (label photo + manifest line), classifies the exception type and modality, and dispatches to the right worker.
🔧	Worker	work	The specialist task agent — extracts the structured answer (parsed address, damage verdict, HS code, etc.) against the task schema.
🔍	Verifier	check	Independently reviews the worker's output against the source — does the parsed address match the label? does declared value match the invoice?
⚠️	Exceptions Specialist	decide	A heavier second-look agent, invoked only for high-stakes or low-confidence items: customs holds, hazmat, high-value, suspected tamper.
🧭	Orchestrator	decide	Runs the per-item graph and applies the retry/escalate/accept policy, emitting the final routing decision plus a coordination trace.

Worker specialists

18 task types · 111 scenarios, spread across all four modalities.

	Task	id	Modality	Difficulty	Scenarios
🏷️	Label Parse	label-parse	Vision	1	7
📦	Damage Assess	damage-assessment	Vision	2	6
☣️	Hazmat Check	hazmat-detection	Vision	3	6
🧾	Customs Invoice	customs-invoice	Document	2	6
🔒	Seal / Tamper	seal-tamper	Vision	3	5
📋	Manifest Recon	manifest-recon	Document	1	6
🌐	Tariff Class	tariff-classification	Text	2	7
🚦	Exception Route	exception-routing	Text	1	7
📐	Dim/Weight	dim-weight	Vision	2	6
🧱	Pallet Check	pallet-check	Vision	2	6
📍	Address Check	address-validation	Text	1	6
🚚	Carrier Select	carrier-select	Text	1	6
⏱️	SLA / ETA	sla-risk	Text	2	7
↩️	RMA / Return	rma-disposition	Text	2	6
🛑	Restricted	restricted-screening	Text	3	7
📄	Docs Check	docs-completeness	Document	1	6
✍️	Handwritten	handwritten-label	Vision	3	5
🎞️	Conveyor Cam	conveyor-incident	Video	3	6

Task details

🏷️ Label Parse

label-parse · Vision · difficulty 1 · 7 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
carrier	string
trackingNumber	string
serviceLevel	string
address	string

Example scenario — lp-7 ⚠ adversarial (Water-damaged Yodel label (hard).):

{
  "carrier": "Yodel",
  "trackingNumber": "JD000223344556",
  "serviceLevel": "ECONOMY",
  "address": "9 Mill Lane Leeds LS1 5PU"
}

📦 Damage Assess

damage-assessment · Vision · difficulty 2 · 6 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
damaged	boolean
damageType	crushed | wet | torn | none
severity	number
action	accept | repackage | refuse

Example scenario — dm-2 ⚠ adversarial (Badly crushed corner — refuse.):

{
  "damaged": true,
  "damageType": "crushed",
  "severity": 4,
  "action": "refuse"
}

☣️ Hazmat Check

hazmat-detection · Vision · difficulty 3 · 6 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
unClass	string
compliant	boolean
labelMissing	boolean

Example scenario — hz-2 ⚠ adversarial (UN class 8 corrosive — required label missing (mislabel).):

{
  "unClass": "8",
  "compliant": false,
  "labelMissing": true
}

🧾 Customs Invoice

customs-invoice · Document · difficulty 2 · 6 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
hsCode	string
declaredValue	string
countryOfOrigin	string

Example scenario — ci-2 ⚠ adversarial (Suspected customs undervaluation (adversarial).):

{
  "hsCode": "6110.20",
  "declaredValue": "USD 180.00",
  "countryOfOrigin": "BD"
}

🔒 Seal / Tamper

seal-tamper · Vision · difficulty 3 · 5 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
sealIntact	boolean
tampered	boolean
flag	clear | tamper | unknown

Example scenario — st-2 ⚠ adversarial (Seal broken / tampered — flag TAMPER.):

{
  "sealIntact": false,
  "tampered": true,
  "flag": "tamper"
}

📋 Manifest Recon

manifest-recon · Document · difficulty 1 · 6 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
expected	number
scanned	number
missing	number

Example scenario — mr-4 ⚠ adversarial (Over-delivery — 7 extra (adversarial).):

{
  "expected": 64,
  "scanned": 71,
  "missing": 0
}

🌐 Tariff Class

tariff-classification · Text · difficulty 2 · 7 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
hsCode	string
dutyCategory	duty-free | low-duty | standard | high-duty

Example scenario — tf-5 ⚠ adversarial (Whisky — high duty (adversarial).):

{
  "hsCode": "2208.30",
  "dutyCategory": "high-duty"
}

🚦 Exception Route

exception-routing · Text · difficulty 1 · 7 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
category	string
queue	string
priority	P1 | P2 | P3

Example scenario — er-4 ⚠ adversarial (Hazmat safety hold, P1 (adversarial).):

{
  "category": "safety-hold",
  "queue": "hazmat-specialist",
  "priority": "P1"
}

📐 Dim/Weight

dim-weight · Vision · difficulty 2 · 6 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
declaredLengthCm	number
declaredWidthCm	number
declaredHeightCm	number
declaredWeightKg	number
mismatch	boolean

Example scenario — dw-2 ⚠ adversarial (Large box, tiny declared weight — mismatch.):

{
  "declaredLengthCm": 50,
  "declaredWidthCm": 40,
  "declaredHeightCm": 40,
  "declaredWeightKg": 1,
  "mismatch": true
}

🧱 Pallet Check

pallet-check · Vision · difficulty 2 · 6 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
cartonCount	number
overhang	boolean
stackingViolation	boolean

Example scenario — pc-2 ⚠ adversarial (Cartons overhanging edge.):

{
  "cartonCount": 18,
  "overhang": true,
  "stackingViolation": false
}

📍 Address Check

address-validation · Text · difficulty 1 · 6 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
canonical	string
deliverable	boolean
zone	string

Example scenario — av-2 ⚠ adversarial (Missing postcode, undeliverable.):

{
  "canonical": "42 Wallaby Way, Sydney",
  "deliverable": false,
  "zone": "INT-AU"
}

🚚 Carrier Select

carrier-select · Text · difficulty 1 · 6 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
carrier	string
service	string
cost	string

Example scenario — cs-4 ⚠ adversarial (Hazmat constraint excludes cheap option.):

{
  "carrier": "DHL",
  "service": "HAZMAT",
  "cost": "GBP 15.00"
}

⏱️ SLA / ETA

sla-risk · Text · difficulty 2 · 7 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
status	on-time | at-risk | breached
etaHours	number
cause	string

Example scenario — sr-2 ⚠ adversarial (Customs hold — breached.):

{
  "status": "breached",
  "etaHours": 50,
  "cause": "customs"
}

↩️ RMA / Return

rma-disposition · Text · difficulty 2 · 6 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
disposition	restock | refurbish | scrap
reason	string

Example scenario — rma-3 ⚠ adversarial (Liquid damage — scrap (adversarial).):

{
  "disposition": "scrap",
  "reason": "liquid-damage-unrepairable"
}

🛑 Restricted

restricted-screening · Text · difficulty 3 · 7 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
status	allowed | restricted | prohibited
reason	string

Example scenario — rs-2 ⚠ adversarial (Counterfeit — prohibited.):

{
  "status": "prohibited",
  "reason": "counterfeit-goods"
}

📄 Docs Check

docs-completeness · Document · difficulty 1 · 6 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
bolPresent	boolean
cooPresent	boolean
packingListPresent	boolean
complete	boolean

Example scenario — dc-2 ⚠ adversarial (Missing COO — incomplete.):

{
  "bolPresent": true,
  "cooPresent": false,
  "packingListPresent": true,
  "complete": false
}

✍️ Handwritten

handwritten-label · Vision · difficulty 3 · 5 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
name	string
addressLine	string
postcode	string

Example scenario — hw-3 ⚠ adversarial (Handwritten — hard (adversarial).):

{
  "name": "K. Patel",
  "addressLine": "33 Bridge Lane",
  "postcode": "B16 4QP"
}

🎞️ Conveyor Cam

conveyor-incident · Video · difficulty 3 · 6 scenarios

Output schema (the structured object the worker must emit, graded against ground truth):

Field	Type
event	clear | jam | fall | crush
action	accept | reroute | refuse

Example scenario — cv-4 ⚠ adversarial (Trailing tote rams it into the scan post — crushed.):

{
  "event": "crush",
  "action": "refuse"
}

---

Adding a task #18+ is one config plus a grader — see Add a Task and Authoring scenario data. Re-run npm run gen:docs to refresh this page.