Decision owner
Logistics coordinator
The named role remains accountable for the consequential decision.
Transportation & Logistics
Designed for Logistics coordinator
Give the logistics coordinator a grounded working surface for in-transit shipment exceptions: detect the milestone miss, explain the root cause from carrier EDI and telemetry evidence, quantify the delivery-promise impact, and draft the carrier and customer response without leaving the exception record.
Contract TRA-01 · primary aggregate ShipmentException · mode loading
Decision brief
This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.
The evidence and control points that shape this recommendation.
Decision owner
Logistics coordinator
The named role remains accountable for the consequential decision.
Governed evidence
6 record types
Structured records and cited text ground the recommendation.
Workflow
5 controlled stages
Each transition records its input, output, status, and audit context.
Human controls
2 approval gates
Approval gates prevent the copilot from making consequential decisions.
A 22-pallet refrigerated LTL shipment tendered under a 48-hour service level posts an EDI 214 AF status with reason code NS at the Memphis cross-dock after a 210-minute dwell.
Give the logistics coordinator a grounded working surface for in-transit shipment exceptions: detect the milestone miss, explain the root cause from carrier EDI and telemetry evidence, quantify the delivery-promise impact, and draft the carrier and customer response without leaving the exception record.
CustomerNotification gives Logistics coordinator with TMS connector the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Step 1 of 5
| Field | Value |
|---|
| Field | Value |
|---|
The output appears here immediately. More technical evidence remains available below.
The demonstration keeps deterministic controls, AI assistance, and approval separate.
Source systems enforce identity, workflow order, policy filters, and record updates.
Retrieval and generation assemble relevant evidence into a cited recommendation or draft.
Logistics coordinator verifies material claims and approves the consequential action.
Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.
Automated stage
What happens: Change-feed exception detector performs milestone deviation detection using TrackingEvent and produces ExceptionCase. The transition is deterministic and does not require autonomous model approval.
Why it matters: ExceptionCase gives Retrieval orchestrator the evidence needed to begin Root-cause evidence assembly, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/milestone-deviation-detection
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Retrieval orchestrator performs root-cause evidence assembly using ExceptionCase and produces evidenceBundle. The transition is deterministic and does not require autonomous model approval.
Why it matters: evidenceBundle gives Shipment exception copilot the evidence needed to begin Recovery option generation, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/root-cause-evidence-assembly
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Shipment exception copilot performs recovery option generation using evidenceBundle and produces RecoveryPlanDraft. The transition is deterministic and does not require autonomous model approval.
Why it matters: RecoveryPlanDraft gives Logistics coordinator the evidence needed to begin Coordinator adjudication of recovery option, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/recovery-option-generation
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Logistics coordinator performs coordinator adjudication of recovery option using RecoveryPlanDraft and produces approvedRecoveryPlan. A named human approver must review the evidence before the transition completes.
Why it matters: approvedRecoveryPlan gives Logistics coordinator with TMS connector the evidence needed to begin Carrier tender and consignee notification, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/coordinator-adjudication-of-recovery-option
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Logistics coordinator with TMS connector performs carrier tender and consignee notification using approvedRecoveryPlan and produces CustomerNotification. A named human approver must review the evidence before the transition completes.
Why it matters: CustomerNotification gives Logistics coordinator with TMS connector the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/carrier-tender-and-consignee-notification
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Run a stage to see its explanation, evidence, full request, and full response.
Ask a question and receive an answer grounded in retrieved ShipmentException evidence.
Select a starter question or enter your own.
Loaded live from /api/config, /api/domain/model, and
/api/domain/sample.
shipmentExceptions/tenantId + /shipmentIdA 22-pallet refrigerated LTL shipment tendered under a 48-hour service level posts an EDI 214 AF status with reason code NS at the Memphis cross-dock after a 210-minute dwell. The copilot assembles the event timeline, cites the carrier's service guide clause that permits a single expedite tender without shipper pre-authorization under 900 USD, and proposes rerouting through the Nashville terminal for a 6-hour slip instead of a 19-hour slip. The coordinator approves the reroute, the revised delivery window is written to the shipment header, and the consignee receives a cited notification naming the new Thursday 06:00-10:00 window.
| Container | Role | Hierarchical partition key | Document types |
|---|---|---|---|
shipmentExceptions |
Primary | /tenantId + /shipmentId |
Shipment, TrackingEvent, ExceptionCase, RecoveryPlanDraft, CustomerNotification |
carrierContractLibrary |
Reference | /tenantId + /carrierScac |
CarrierPolicyChunk |
| Type | Container | Partition key | Identifier pattern | Embedding fields |
|---|---|---|---|---|
Shipment |
shipmentExceptions |
/tenantId + /shipmentId |
shipment::{shipmentId} |
None |
TrackingEvent |
shipmentExceptions |
/tenantId + /shipmentId |
shipment::{shipmentId}::event::{eventTimestampUtc}::{carrierScac} |
None |
ExceptionCase |
shipmentExceptions |
/tenantId + /shipmentId |
shipment::{shipmentId}::exception::{exceptionId} |
None |
CarrierPolicyChunk |
carrierContractLibrary |
/tenantId + /carrierScac |
carrier::{carrierScac}::policy::{policyDocId}::{chunkOrdinal} |
chunkVector |
RecoveryPlanDraft |
shipmentExceptions |
/tenantId + /shipmentId |
shipment::{shipmentId}::plan::{planId} |
rationaleVector |
CustomerNotification |
shipmentExceptions |
/tenantId + /shipmentId |
shipment::{shipmentId}::notification::{notificationId} |
None |
Render the coordinator's morning exception board for a destination region ordered by promise risk. Application-side partition-key fan-out dispatcher board: the tenantId partition-key prefix scopes the scan and the open-exception state plus the destination-stop list bound it to one region's working set.
shipmentExceptions
partition-key-fan-out
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.type = 'Shipment' AND c.exceptionState IN ('open','escalated') AND ARRAY_CONTAINS(@regionStops, c.destinationStopCode) ORDER BY c.promisedDeliveryWindowUtc ASC
Rebuild the full carrier status timeline for one shipment as a partition-aligned single-partition read.
shipmentExceptions
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.shipmentId = @shipmentId AND c.type = 'TrackingEvent' AND c.eventTimestampUtc >= @sinceUtc ORDER BY c.eventTimestampUtc ASC
Retrieve the tariff and SLA clauses that constrain accessorials and reroute authority for the carrier on this lane.
carrierContractLibrary
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.carrierScac = @carrierScac AND c.type = 'CarrierPolicyChunk' AND c.effectiveFromUtc <= @nowUtc ORDER BY RANK RRF(VectorDistance(c.chunkVector, @queryVector), FullTextScore(c.chunkText, @queryTerms))
Queue the copilot recommendations awaiting coordinator adjudication, highest ETA impact first. Application-side partition-key fan-out review queue: bounded by the tenantId prefix, the pending review state and the current shift window.
shipmentExceptions
partition-key-fan-out
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.type = 'RecoveryPlanDraft' AND c.reviewState = 'pending' AND c.generatedAtUtc >= @shiftStartUtc ORDER BY c.confidenceScore DESC