Atlas: connected impact and scenario — 26-second product walkthrough

00:00–00:02 — Open the North American lane network Twin in Meridian Logistics. The full default Pascal sidebar remains available beside the native Atlas workspace.

00:02–00:05 — Search for and select Horizon Freight. Its carrier card shows 42 related shipments and 17 high-risk shipments. The native Relations panel identifies 42 carried shipments and three served lanes.

00:05–00:07 — Expand one hop through the native Search Around controls. The bounded graph contains 48 loaded objects and 87 relationships: the original carriers, connected shipment records and their lanes.

00:07–00:10 — Apply the Shipment scope and a risk-above-80-percent rule. The native graph and table contain the same 17 high-risk shipment records.

00:10–00:12.5 — Inspect MDR-80421’s assigned-lane relationship to Boise → Tacoma. The native relation evidence identifies Meridian TMS shipment snapshot v4, its source reference and source-stream origin. The source was observed at 14:28 UTC and known at 14:30 UTC on 20 August 2026. Expanding this shipment’s neighborhood adds its carrier and lane to the 17 shipment records; this does not change the risk selection.

00:12.5–00:16 — Inspect the scenario inputs and the published Carrier failure redistribution model version 3. Inputs retain source snapshot v4, the Object Set, an 80-percent risk threshold, fallback capacity of ten and seven loads, and deterministic seed 80421. Compliance approval is not recorded. The scenario is a modeled alternative, not an observed operating result.

00:16–00:20.5 — Compare the completed reference and candidate runs. Shipments above the modeled risk threshold change from 17 to zero, and capacity allocation changes from zero to 17. No new constraint, risk or SLA breaches are projected. The 17 modeled capacity slots assume any required future approval; all three hazardous-load holds remain. Only 14 shipments are eligible for the separate operating proposal.

00:20.5–00:23 — Open Prepare reroutes. Its status is proposed, execution is locked behind proposal and approval checks, and the native Open linked Task control leads to the operating decision. No tender or external writeback has occurred.

00:23–00:26 — The Reroute Horizon Freight lanes Task is paused for approval of 14 eligible reroutes. MDR-80421, MDR-80434 and MDR-80439 remain held for compliance sign-off. Approve once and Decline remain available; neither is selected.