Methodology
Why operating envelope matters in autonomous freight
Three commercial autonomous-freight deployments at three structurally distinct operating envelopes. The verification framework discriminates per envelope; "driverless commercial freight" is a heterogeneous category.
"Autonomous trucks operate commercially in the United States today" is a sentence that is true and uninformative. The three commercial deployments below are all operating commercially today, all using autonomous driving technology, all transporting customer-paid freight under contracts of record. They are also operating in three structurally distinct envelopes that the verification framework treats differently. An operator evaluating "autonomous truck commercial deployment" needs to know which envelope is being claimed, because the verification state across the framework's four anchors differs by envelope even when the makers all clear the counterparty bar.
The verification framework's second anchor is verifiable operating envelope. Routes, facility types, load categories, regulatory frameworks, and time horizons together define what is being verified. The three deployments below clear the envelope anchor in three different envelopes; their position on the framework's other three anchors (counterparty, human-in-loop posture, repeatability) varies accordingly. The methodology's value is naming the distinctions so claims about one envelope do not bleed into vocabulary about another.
Envelope A: on-highway over-the-road commercial corridor
The on-highway over-the-road envelope is the open public freight network: interstate corridors, public-road infrastructure, mixed traffic, FMCSA's commercial motor vehicle framework, customer freight booked through brokerage relationships. This is the envelope that drives the $4-trillion-plus global long-haul freight market and the one that maps most directly onto vocabulary about "autonomous trucking" in trade press and operator conversation.
The current canonical anchor in this envelope is Bot Auto's Houston-to-Dallas humanless commercial truckload on April 29, 2026: a 231-mile run from Riggy's Truck Parking in northeast Houston to Safe Stop just south of Dallas, booked through Ryan Transportation's brokerage, with no safety driver onboard, no in-cab observer, and no low-latency remote teleoperation backup. The deployment clears three of the four framework anchors at the event (counterparty + on-highway envelope + absence-of-human-in-loop); repeatability anchors via sustained subsequent operation along the Texas corridor that Bot Auto announced as the relationship's near-term scope.
Envelope B: off-highway industrial routes
The off-highway industrial envelope is private-operator infrastructure: closed industrial sites, dedicated mining or energy corridors, restricted-access frac-sand or aggregate roadways, regulatory frameworks that differ from on-highway DOT/FMCSA structure. Verification within this envelope is equally rigorous but operates against different verification surfaces; a load delivered under an industrial-operator contract clears different evidence than a load delivered through public brokerage.
The current canonical anchor in this envelope is Kodiak's relationship with Atlas Energy Solutions in the Permian Basin. Per Atlas Energy's investor disclosure, Kodiak's customer-owned-and-operated driverless RoboTrucks have been hauling frac sand from Atlas's Dune Express conveyor system to well sites across West Texas and Eastern New Mexico since December 2024, with 800-plus paid driverless loads and 1,600-plus hours of driverless service accumulated against Atlas as customer of record. The deployment clears the off-highway envelope's verification bar (counterparty + envelope + absence-of-human-in-loop) and has anchored repeatability via the multi-year operational tail. Kodiak's stated H2 2026 long-haul market entry is the second-mover watch for on-highway envelope graduation.
Envelope C: private-road point-to-point commercial
The private-road envelope is operator-controlled infrastructure between two facilities: a manufacturing site and an adjacent warehouse, a port terminal and an adjacent yard, a factory and its own logistics chain. The envelope is geographically narrow (often under a mile) but operationally sustained (daily-cadence commercial operations); verification operates against the customer's contract, the operating cadence, and the specific private-road regulatory framework.
Einride's relationship with GE Appliances in Selmer, Tennessee anchors this envelope. Per GE Appliances' announcement and Einride's deployment record, the Einride Pod (cabless purpose-built autonomous electric truck) moves finished goods between GE's Selmer manufacturing facility and an adjacent warehouse 0.3 miles away, making approximately seven trips per day Monday through Thursday under a three-year commercial contract. The deployment clears the private-road envelope's verification bar (counterparty + envelope + repeatability) with an honest disclosure on the human-in-loop anchor: Trucking Dive reports a remote human operator with a CDL holds take-over capability, which makes this remote-supervised autonomy under the framework's third anchor rather than humanless. The transparent disclosure (cabless truck, remote operator, daily cadence) is the editorially relevant feature: Einride frames its commercial operation accurately relative to the verification state it actually anchors.
Why the discrimination matters
A trade-press headline that reads "autonomous trucks now operating commercially in the US" is technically true across all three envelopes above and operationally specific to none of them. Bot Auto, Kodiak, and Einride are doing different things in different infrastructures under different contracts with different human-in-loop postures. Operators procuring autonomous freight capacity need to know which envelope they are procuring within because the cost structure, the load types, the route characteristics, and the verification guarantees differ by envelope.
The framework's value to operators is that the discrimination is mechanical, not editorial discretion. Each envelope is identifiable: where (route, facility type, regulatory framework), what (load category, operating cadence), and how (cab versus cabless, observer versus remote backup versus humanless). The other framework anchors (counterparty, human-in-loop, repeatability) layer on top of envelope identification. A claim that does not specify its envelope is a claim that has not been verified; the methodology is for extracting envelope specificity from marketing language and then verifying within the identified envelope.
Implication for category-wide claims
Vocabulary like "autonomous trucking commercial deployment" conflates three operationally distinct envelopes that, today, have different category leaders. Bot Auto leads on-highway OTR. Kodiak leads off-highway industrial. Einride leads private-road point-to-point with transparent remote-supervised framing. Aurora's stated observer-removal target on the International LT platform is the second-mover watch on on-highway. Multiple makers will eventually clear multiple envelopes. The category-level question is not "who is leading autonomous trucking" but "who has cleared which envelope on which framework anchor," and the methodology is designed to surface that question in a form operators can act on.
Continue reading
- DEPLOY's verification framework → the four-anchor methodology this page applies; how to evaluate any maker's commercial-deployment claim.
- Contrast cases in DEPLOY's framework → worked examples of cases that look like canonical commercial deployment but anchor different verification postures; why L2+/L3 fleet scale is editorially distinct from L4 commercial.
- Verified-vs-claimed framework canon → the nine anchored angles + two pending; category-specific instantiations of the verification methodology.