Meridian · Logistics

A supply-chain control tower where governed agents watch a live network, raise incidents, argue with each other, and ask permission before they act.

7 agents com.meridian.logistics

Stacked freight containers beneath gantry cranes at a port

A control tower for a fictional European third-party logistics operator. Agents watch a simulated network (raising incidents, requesting approvals, debating each other, and acting) with every action bounded by a written policy and recorded in an audit trail. The central claim is that the agents are not clever scripts with database access; they are actors operating under written authority, and nothing mutates operational state except through that gate.

Agent roster

All 7 agents in this demo.

Cold Chain Dynamic Routing Fleet Asset Carrier Management Supply Chain Risk Sustainability Customs Compliance

What this demo shows

The moments worth walking a prospect through.

Governance

Every action passes a policy gate

Agent conclusions funnel through one procedure that checks the proposed action against that agent's written policy (confidence floors, cost ceilings, permission tiers, written prohibitions) and routes it to auto-execution, a human approval, or advisory-only.

Arbitration

Multi-agent arbitration with quantified dissent

When cold chain, sustainability and routing want incompatible things, precedence rules resolve it. Losing positions are stored with the cost, carbon and hours they would have saved. One case records that rail would have saved 127 kg CO₂e, and why it was overruled anyway.

Governance

Winning a debate grants no extra authority

The arbitrated action goes back through the ordinary decision path and faces the same policy gate as any other. An agent that wins an argument still cannot act beyond what its policy permits.

Forecasting

Predictive ETA with confidence bands

Every movement writes a P10/P50/P90 window with the named reasons for its spread, and the median is honest about its source: extrapolated pace once under way, route plan before that. Mandatory driver rest goes into the median rather than the band, because a legally required stop is arithmetic, not uncertainty.

Compliance

Customs holds judged against the cargo, not the clock

For perishable freight the question is never how long a hold lasts but whether it outlasts the stability budget left. The same four-hour paperwork hold is critical for frozen vaccine and routine for fresh produce, and demurrage prices on escalating tiers per started day.

Detection

A sweep that catches what emits no event

A hold can go from tolerable to terminal without anything about the hold changing, because the crossing is the absence of change. A time-driven sweep re-checks open holds against eroding budgets and escalates when one quietly crosses the line.

Observability

Agent communication reconstructed, not instrumented

The comms graph draws only edges that really exist (a decision published to the bus, an arbitration position that lost, evidence joining another agent's incident, a decision escalated to a human), rebuilt from stored events, positions and the audit trail rather than from invented chatter.

Integration

Live external signals and emissions accounting

Facility weather comes from a live external source and is mapped to operational risk, so freezing rain outranks a thunderstorm because black ice stops a truck. Emissions are priced per mode against real route distance, so a modal-shift proposal carries a real number.

Simulation

A deterministic world you can reset mid-demo

Reset rebuilds the identical network every time from a seeded baseline, so a scenario behaves the same in front of every customer, and approvals expire and stale tasks escalate on the simulation clock, not wall-clock time, so a paused demo doesn't drift.