Skip to content
Yard & transport

Yard & transport

Agents: the twins orchestrator (twins), the route twin (route_twin) and the common operational picture (cop), with the yard, border, custody and disruption cards.

What it does

It reads yard snapshots, border and port events and transport records, flags the trailer, crossing or container that is costing money now, and drafts the action for the supervisor. Its jobs:

  • Yard capacity. Finds when the yard is over capacity and which arrivals were never recorded.
  • Border waits. Works out detention from dwell time and the stated cost per hour, and proposes “transmit corrected documents” when the recorded cause is a document problem.
  • Demurrage and detention. Separates days caused by documents from days caused by congestion.
  • Service disruption. Records a disruption and its effect on open orders.
  • Routes. Ranks the routes your routing provider returns on the criteria you name, with emissions per mode where a factor is stated.
  • One picture. Ranks events from several sources by priority, life safety first, and flags events seen by only one source.
  • Orchestration. The twins orchestrator maps each event to the right action card and hands work to the other agents on these cards.

What it reads

Yard snapshots and appointments, border crossing and port events, container free time and gate events, custody events, carrier and lane records, routes from your routing provider, sensor and camera findings, and the twin graph. It can run read-only queries against the connection a run was started with.

What it produces

  • Action cards on Actionable Twins, each with a priority and one proposed action. Route proposals also show on its Map view. See Action cards & money.
  • Evidence documents such as CHAIN_OF_CUSTODY_AUDIT and SERVICE_DISRUPTION.
  • A ranked list of routes and carriers, and a prioritised list of current events.

Human oversight

  • A supervisor approves every action on a card, through TwinsService.ExecuteAction. Rejection needs a reason.
  • The agents never dispatch a vehicle, book a carrier or send anything to a transport system on their own.
  • Every action an orchestrator’s final answer proposes passes the judging ladder before it reaches the queue. An action the judge still disagrees with after one revision is removed.

Model

The deployment’s general reasoning tier.

Distances and travel times come from your routing provider, not from the model. The cards’ figures are fixed arithmetic over your records.

Where it runs and data handling

On the deployment’s own model plane: Runink’s shared machines on a Trial, your own cloud on Cloud and your own servers on On-premises. No outside AI service is called on any plan. See Facts shared by every card.

Guardrails

  • Never makes up a distance or a time. A route the provider couldn’t compute is “unavailable”, never zero.
  • A missing cause, capacity or cost figure is reported as missing.
  • Doesn’t deprioritise neighbourhoods or regions on socioeconomic or demographic grounds, and doesn’t recommend hoarding capacity or price gouging.
  • Refuses to de-anonymise people from aggregate trends, and refuses to fabricate sustainability figures.

How to read its results

  • An unrecorded handoff is not a break in custody.
  • A ranked route is only as good as the provider’s answer and the criteria you named.
  • An event flagged as single-source hasn’t been confirmed by a second source.
  • It doesn’t establish who caused a delay beyond what the records state.