Local / Desktop reference architectureShipment tracking and ETAs
A Local / Desktop reference architecture for shipment tracking and etas in Logistics. Triggered by shipment milestone or exception event, Padiso orchestrates 3 specialist agents on Claude Code + Ollama, on your machines, reaching transportation management system (tms) and your tools through the Model Context Protocol, with budgets, approvals and an audit trail throughout.
Local / DesktopRuntime: Claude Code + Ollama, on your machinesTrigger
Shipment milestone or exception event
Logistics
Orchestration
Padiso Orchestrator
goals · tasks · heartbeat
Governance
budgets · approvals · audit
Runtime & agents
Agent runtime
Claude Code + Ollama, on your machines
Tracking agent
agent
Exception agent
agent
Comms agent
agent
Integrations · MCP
MCP gateway
Your systems
Transportation Management System (TMS)
Carrier / EDI feeds
Order management
How the data flows
Trigger: Shipment milestone or exception event
- 1
Tracking agent ingests carrier events and detects delays or shortages
- 2
It correlates against the order and SLA
- 3
Exception agent proposes a reroute or recovery action
- 4
High-impact changes escalate to the ops desk
Agent team
- Tracking agent
- Exception agent
- Comms agent
Integrations
Reached through the Model Context Protocol, scoped and governed.
Runtime & data
Claude Code + Ollama, on your machines
Transportation Management System (TMS)
Carrier / EDI feeds
Order management
Security & operational considerations
- Idempotent event handling at scale
- Approvals on cost-incurring reroutes
- Audit trail per shipment
Local / Desktop deployment
Self-hosted: agents and models run on your machines, so regulated data and credentials never leave your network. Best when data residency is non-negotiable.
Run this blueprint anywhere
More Logistics blueprints
Run your business on agents.
Start free, or talk to us about putting an agent workforce to work across your operations.