{ "schemaVersion": 2, "title": "Texas autonomy research library", "author": "Sulayman Bowles", "editionDate": "2026-10-19", "purpose": "Two authored Texas autonomy essays with dated sources, declared comparisons and historical supporting claim ledgers. Review dates are editorial reminders, not legal deadlines or scheduled jobs; this edition consolidates the earlier library without refreshing every source.", "previousEdition": { "editionDate": "2026-10-16", "href": "/research/texas-research-library-2026-10-16.json", "articleCount": 18, "sha256": "4c1a592e0f20c2fd1d3ce223cddcd2db2d399b910799cfee2ecb6e570249c1b1" }, "articles": [ { "slug": "texas-robotaxi-business-service-map", "title": "Texas robotaxis, one trip at a time", "canonical": "https://sulayman-bowles.dev/research/texas/texas-robotaxi-business-service-map", "pillar": "Autonomous mobility and freight", "reader": "Travel managers, employers and mobility suppliers", "decision": "Choose a usable passenger journey and size the commitment to the supported service", "sourceCutoff": "2026-10-14", "datePublished": "2026-10-13", "dateModified": "2026-10-19", "evidenceBoundary": "Method & limits: This is a reading of dated operator and government records, not a firsthand ride review or a live dispatch map. Passenger access was checked October 12–14, 2026; the October 14 San Antonio opening, Austin booking instructions and Texas authorization guidance were rechecked October 19. Other sources keep their listed check dates. The fare and fallback calculation below uses invented inputs; employee time is an allocated value, not necessarily a cash payroll cost. Preliminary investigations are identified as such.", "opening": [ "On October 14, 2026, Waymo removed the invitation requirement for San Antonio and opened SAT airport to everyone. That is a change I can use: a traveler can now request a ride without first winning access. It also exposes what is wrong with most robotaxi maps. A colored city tells me very little about the trip I need to make. [Waymo’s announcement](#source-waymo-sa-open).", "I would allow a suitable robotaxi ride as an option in a Texas travel policy. I would be much slower to promise a conference full of guests that autonomous cars will get them to the venue on time. The first purchase uses a car when one is offered. The second requires enough cars, eligible passengers and working pickups in the same departure window. The difference is the business." ], "sections": [ { "id": "operating-evidence", "title": "Four Waymo cities, two booking arrangements", "paragraphs": [ "Dallas opened to all riders on August 4 and Houston on August 20. San Antonio followed on October 14, including its airport. Austin rides come through Uber: the traveler requests an eligible product, receives a Waymo offer if matched, then accepts it. Switching on the AV preference improves the chance of a match. It does not reserve a car. [Dallas](#source-waymo-dallas); [Houston](#source-waymo-houston); [Austin instructions](#source-waymo-uber).", "That last detail matters more to an organizer than the city count. If the event depends on a Waymo experience, the ordinary Austin booking flow leaves the organizer with a promise the product has never made. If the event depends on getting people there, a conventional ride can do the job when no Waymo is offered.", "Here is the access comparison I would keep open while planning a trip." ], "table": { "caption": "Texas passenger access in the October 12–14, 2026 source review", "columns": [ "Market / program", "Public access / channel", "Onboard driving role", "Unresolved trip condition" ], "rows": [ [ "Waymo", "Dallas, Houston and San Antonio: Waymo app. Austin: eligible Uber match. SAT opened October 14.", "ADS drives; remote support remains part of the service", "Endpoints, pickup instructions and an available offer" ], [ "Zoox", "Austin page: coming soon / waitlist. Dallas and Houston: announced testing stages.", "Retrofitted test SUVs use a safety driver; purpose-built vehicles have a different rollout", "An admitted rider and a bookable Texas journey" ], [ "Tesla Robotaxi", "Limited Austin/Dallas/Houston areas through its app", "Current onboard role not established by reviewed rider guidance", "Assigned vehicle, self-booking, age rules and supported route" ], [ "Avride Dallas", "Eligible Uber request / AV offer in Central Dallas north of Trinity River", "Onboard specialist can take control", "Three rear-seat riders; boarding window and actual match" ], [ "May Mobility Arlington", "Dated Uber plan; active-page list lacks Arlington booking entry", "Current local role not established by reviewed access records", "A current Arlington booking route and rider admission" ] ], "note": "Read with the dated sources below. The app decides whether a particular trip is offered. The table records access and operating roles, without ranking safety." } }, { "id": "booking-and-trip-fit", "title": "The airport is another journey", "paragraphs": [ "The San Antonio opening covers SAT. Earlier terminal guidance puts pickup and dropoff at Terminal A/B Departures and the Arrivals outer curb near Rideshare Zone 2; the app supplies the current instructions. The August Dallas announcement described autonomous testing at Love Field and future freeway testing. I would not turn that announcement into a public airport reservation. The reviewed record supplies no such booking for Love Field, DFW, Houston’s airports or Austin-Bergstrom. [SAT announcement](#source-waymo-sa-open); [terminal guidance](#source-travel-airports); [Dallas announcement](#source-waymo-dallas).", "The doorway matters too. Waymo says construction, traffic and pickup restrictions can leave a walk at either end. An eight-minute ride with luggage and a distant pickup can be a worse way to reach a meeting than a longer ride that starts outside the hotel. I would compare the time from leaving the building to being ready at the destination. [Pickup guidance](#source-travel-pickup).", "Payment follows the booking channel. A Waymo business profile can carry a separate payment method, while an Austin Uber request uses the relevant Uber arrangement. The reviewed Waymo for Business page did not name Texas among its markets. An employer subsidy belongs in the budget after the traveler qualifies for it. [Profiles](#source-travel-business-profile); [business program](#source-travel-business-program).", "The October 12 freeway guidance also described limited access. I would preview the offered route before budgeting a suburban meeting. [Freeway guidance](#source-travel-freeways)." ] }, { "id": "zoox-and-the-next-stage", "title": "Zoox can have a customer before it has a passenger", "paragraphs": [ "Zoox’s Austin page directed readers to a waitlist in the October 12 rendered review. Dallas’s March announcement and Houston’s September announcement described mapping and testing sequences. Those activities can create work for a supplier or a depot landlord long before a hotel can offer its guests a ride. [Austin](#source-zoox-austin); [Dallas testing](#source-zoox-dallas-testing); [Houston testing](#source-zoox-houston).", "The vehicle in the street is a clue. Zoox says its retrofitted testing SUVs use a safety driver and are intended for mapping, testing and validation. Its purpose-built robotaxi follows a different deployment path. A count that adds them together conceals what the fleet can sell. [Testing fleet](#source-zoox-test-fleet).", "The federal commercial exemption runs from July 31, 2026, through July 31, 2028. It permits up to 2,500 exempted vehicles to enter interstate commerce for commercial deployment in a twelve-month period; local operation remains subject to Operational Authorizations. The grant also requires Zoox to retain lifetime operational control on its terms. Those are consequential conditions for a supplier underwriting the fleet, but they provide neither a Texas vehicle allocation nor a fare. [Federal grant, sections X.A and X.G](#source-zoox-commercial-grant).", "I would take a signed testing-support order seriously on its own economics. I would price fleet-specific property works against the lease’s commencement and exit terms. Neither investment needs an invented forecast of hotel passengers to become a real business." ] }, { "id": "tesla-product-and-rider", "title": "A passenger has to fit the product", "paragraphs": [ "Tesla’s reviewed rider guidance listed limited areas in Austin, Dallas and Houston, with Model Y and Cybercab rules that differ by vehicle. It requires self-booking and excludes added stops. Accompanied riders aged 8–17 can use Model Y; Cybercab’s corresponding range starts at 13. Its wheelchair-accessible links refer riders to city providers. A concierge with a phone cannot solve every guest’s account, age or access problem. [Tesla rider guidance](#source-tesla-rider).", "Uber’s current Avride Dallas guidance describes Central Dallas north of the Trinity River, an optional AV match and an onboard specialist who can take control. Three passengers fit in the rear seats, and the boarding window is seven minutes. Those are usable event-planning facts. A photograph of an autonomous car is less helpful. [Dallas rider guidance](#source-avride-current).", "May Mobility’s May 20 release described Arlington on Uber as upcoming; the reviewed active-locations page supplied no Arlington booking entry. I would ask for the current program before offering the ride to an employee. [Arlington plan](#source-may-arlington); [active locations](#source-may-locations)." ] }, { "id": "authorization", "title": "A permit and a trip do different work", "paragraphs": [ "Texas made its commercial driverless authorization requirement enforceable on May 28, 2026. The operation’s holder and vehicle listing are the place to start, followed by the supported route and platform-specific responder plan. The statutory test concerns commercial transport without a human driver; an onboard person’s driving role matters. [TxDMV program](#source-permit-program); [Transportation Code](#source-permit-code).", "The authorization has no fee and does not expire. Material information must be updated within 30 days of a change. That is a document-maintenance clock, not a blanket cure period for every unsafe-operation action. A buyer still needs notice when the purchased service pauses and an alternative that can carry the passenger. A contractual credit arrives too late to make the meeting. [Continuing duties](#source-permit-program); [operator and vehicle lookup](#source-permit-lookup).", "I would keep the safety question tied to the service being bought. NTSB’s preliminary account of the January 12 Austin school-bus event describes an incorrect remote-assistance response before a Waymo passed the bus; no crash occurred, and the investigation was ongoing at the October 13 check. NHTSA’s September 4 Cybercab release opened a self-certification inquiry. These records warrant specific questions about correction and support. Raw incident totals, collected under differing reporting rules without comparable exposure, cannot supply a sensible safety ranking. [Austin investigation](#source-austin-school-bus); [Cybercab inquiry](#source-cybercab-audit); [reporting limits](#source-crash-method)." ] }, { "id": "worked-trip-budget", "title": "A cheaper fare has to survive the fallback", "paragraphs": [ "Suppose a company needs 200 trips a month. Geography leaves 160 eligible, rider and account rules leave 140, and pickup points and hours leave 120 usable AV trips. Give those trips an invented $20 fare and the other 80 an invented $28 conventional fare. The mix costs $4,640 against $5,600 for the all-conventional plan: $960 of apparent savings.", "Now give each failed AV attempt an additional $28 replacement fare and 20 minutes of staff time valued at $60 an hour. Each exception costs $48, with the original AV charge retained. Ten exceptions consume half the saving. Twenty consume all of it." ], "table": { "caption": "Hypothetical monthly pilot; every fare, count and time input is assumed", "columns": [ "Case", "Calculation", "Fares plus allocated exception time" ], "rows": [ [ "All-conventional baseline", "200 × $28", "$5,600" ], [ "Eligible AV/conventional mix", "120 × $20 + 80 × $28", "$4,640" ], [ "Mix plus 10 exceptions", "$4,640 + 10 × $48", "$5,120" ], [ "Mix plus 20 exceptions", "$4,640 + 20 × $48", "$5,600" ] ], "note": "Normal travel time is held equal. An exception adds the replacement fare and staff time to the retained AV charge; an actual refund would reduce the total. Twenty exceptions is a break-even calculation, not a provider failure estimate. Staff time has an economic value without necessarily changing payroll." } }, { "id": "decision-from-the-model", "title": "The fare is only one part of the saving", "paragraphs": [ "Twenty failures out of 120 attempted AV journeys is one in six, or 16.7%. Dividing by all 200 company requests would make the exposure look smaller without changing a dollar. The pilot should keep failed requests in the denominator and connect each replacement trip, refund and delay to the journey that caused it.", "There is an even simpler trap in Austin. Uber says a Waymo match costs the same as the eligible product’s driver match. That booking flow starts with no fare saving to spend on extra waiting. For a direct-booked trip, a quoted $5 discount pays for six extra minutes only while employee time is worth less than $50 an hour. Both figures in that threshold are assumptions, so I would replace them with the actual quotes and observed walking and waiting time. [Uber pricing explanation](#source-travel-uber-price).", "My test is ordinary: can the traveler get from the requested entrance to the required destination, at an acceptable total cost, with enough time left to switch? I would start with optional local journeys and keep a funded alternative for the deadline that matters. The city earns its place on the map when the trip works." ] } ], "sources": [ { "id": "waymo-dallas", "label": "Waymo Dallas opens to all riders", "href": "https://blog.waymo.com/blog/shorts/dallas-open-to-all/", "publisher": "Waymo", "date": "2026-08-04", "lastVerified": "2026-10-12", "note": "Dated public-access announcement. Love Field and freeway statements were testing/future plans at that date; do not silently treat them as current passenger availability." }, { "id": "waymo-houston", "label": "Waymo Houston opens to all riders", "href": "https://blog.waymo.com/blog/shorts/houston-open-to-all/", "publisher": "Waymo", "date": "2026-08-20", "lastVerified": "2026-10-12", "note": "Dated open-public-access announcement; not a guarantee of any address or individual trip." }, { "id": "waymo-areas", "label": "Waymo service areas and rider admission", "href": "https://support.google.com/waymo/answer/9059119?hl=en", "publisher": "Waymo Help", "date": "Undated current support page", "lastVerified": "2026-10-14", "note": "Current service-area page rechecked October 14: Austin remains on Uber and San Antonio no longer carries the gradual-admission label. The separately dated opening announcement establishes the new admission policy; maps and available trips remain specific to the request." }, { "id": "waymo-uber", "label": "Ride with Waymo in Austin on Uber", "href": "https://support.google.com/waymo/answer/16011725?hl=en", "publisher": "Waymo Help", "date": "Undated current support page", "lastVerified": "2026-10-19", "note": "Eligible Uber ride request, preference and matched offer differ from guaranteed vehicle selection." }, { "id": "zoox-austin", "label": "Zoox Austin current rider page", "href": "https://zoox.com/austin", "publisher": "Zoox", "date": "Undated current city page", "lastVerified": "2026-10-12", "note": "Full rendered body says coming soon and invites app waitlist entry. A city name/menu entry alone does not establish bookable public rides." }, { "id": "zoox-houston", "label": "Zoox Houston and San Diego testing announcement", "href": "https://zoox.com/journal/zoox-now-testing-houston-san-diego", "publisher": "Zoox", "date": "2026-09-01", "lastVerified": "2026-10-12", "note": "Retrofitted test fleet/manual mapping first; autonomous testing and purpose-built vehicles are later stages. Twelve-location presence is not twelve open ride-hail markets." }, { "id": "tesla-rider", "label": "Tesla Robotaxi rider support", "href": "https://www.tesla.com/support/robotaxi", "publisher": "Tesla", "date": "Undated current support page", "lastVerified": "2026-10-12", "note": "Lists limited Austin, Dallas, Houston service areas, self-booking, vehicle-specific rules and app fare estimates. Does not establish a citywide service guarantee or trip-level vehicle assignment." }, { "id": "tesla-fsd", "label": "Tesla Full Self-Driving (Supervised) support", "href": "https://www.tesla.com/support/fsd", "publisher": "Tesla", "date": "Undated current support page; official indexed body checked2026-10-12", "lastVerified": "2026-10-12", "note": "Official support states active driver supervision and that the feature does not make the vehicle autonomous. Direct retrieval encountered protection/timeout; indexed official text supplies this narrow distinction, not comparative collision-rate evidence." }, { "id": "avride-launch", "label": "Uber and Avride Dallas launch", "href": "https://www.uber.com/us/en/newsroom/avride-on-uber/", "publisher": "Uber", "date": "2025-12-03", "lastVerified": "2026-10-12", "note": "Launch described nine square miles and an onboard specialist behind the wheel, with future driverless operation. Those are dated launch conditions, not an assertion of unchanged October coverage or onboard mode." }, { "id": "may-arlington", "label": "May Mobility fifth-generation update and Arlington plan", "href": "https://maymobility.com/posts/may-mobility-launches-new-av-architecture/", "publisher": "May Mobility", "date": "2026-05-20", "lastVerified": "2026-10-12", "note": "Release describes Arlington Uber deployment as upcoming. Issuer-wide rides/miles are not used as Texas-only or driverless-only metrics." }, { "id": "may-locations", "label": "May Mobility active deployments", "href": "https://maymobility.com/locations/", "publisher": "May Mobility", "date": "Undated current locations page", "lastVerified": "2026-10-12", "note": "Current active list read at review includes Atlanta, Grand Rapids and Eden Prairie, without an Arlington public-booking listing. That absence warrants confirmation; it does not independently prove no Texas operations." }, { "id": "dps-catalog", "label": "DPS platform-specific responder-plan catalog", "href": "https://www.dps.texas.gov/section/cav/connected-autonomous-vehicles", "publisher": "Texas Department of Public Safety", "date": "Page labeled2026-02-27; current catalog checked2026-10-12", "lastVerified": "2026-10-12", "note": "Includes multiple passenger/freight platforms. Posting is not an operator census, authorization finding or commercial-booking map." }, { "id": "crash-method", "label": "NHTSA crash-reporting limitations", "href": "https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting", "publisher": "National Highway Traffic Safety Administration", "date": "2025 amendment effective2025-06-16; current data through2026-08-17", "lastVerified": "2026-10-12", "note": "Different reporting conditions and exposure denominators prevent a valid simple ranking from raw counts; information can be incomplete and updated." }, { "id": "avride-current", "label": "Avride on Uber: current Dallas rider guidance", "href": "https://www.uber.com/us/en/r/autonomous/dallas-tx-us/", "publisher": "Uber", "date": "Undated current service page", "lastVerified": "2026-10-13", "note": "Central Dallas north of Trinity River; optional matching for eligible requests; onboard specialist can take control; three rear-seat riders and seven-minute boarding window. Trip-level availability is not independently booked." }, { "id": "austin-school-bus", "label": "NTSB preliminary Austin school-bus investigation", "href": "https://www.ntsb.gov/investigations/Pages/HWY26FH007.aspx", "publisher": "National Transportation Safety Board", "date": "Event 2026-01-12; preliminary release 2026-03-03", "lastVerified": "2026-10-13", "note": "HWY26FH007: preliminary narrative says no crash; remote-assistance response preceded passing. Status observed Ongoing October 13. No final probable cause, current defect persistence or comparative failure rate established." }, { "id": "cybercab-audit", "label": "NHTSA announces Cybercab certification audit after Austin deployment", "href": "https://www.nhtsa.gov/press-releases/investigation-tesla-cybercab-self-certification", "publisher": "National Highway Traffic Safety Administration", "date": "2026-09-04", "lastVerified": "2026-10-13", "note": "Announced audit of self-certification against applicable FMVSS. Establishes the inquiry opening, not noncompliance, suspension or its current disposition; future rulemaking does not itself change existing standards." }, { "id": "waymo-sa-open", "label": "San Antonio and SAT open to all riders", "href": "https://support.google.com/waymo/answer/18765688", "publisher": "Waymo Help", "date": "2026-10-14", "lastVerified": "2026-10-19", "note": "October 14 notice removes the invitation requirement for San Antonio and opens SAT to all riders. A specific route, pickup and available vehicle still require the booking app." }, { "id": "travel-uber-price", "label": "Uber: eligible Waymo matches and same requested-product price", "href": "https://www.uber.com/us/en/blog/waymo-on-uber/", "publisher": "Uber", "date": "2026-07-24", "lastVerified": "2026-10-12", "note": "Current page price parity applies to a Waymo match for the selected Uber product. It is not a fixed fare or a comparison with another provider." }, { "id": "travel-airports", "label": "Airport service and San Antonio rider eligibility", "href": "https://support.google.com/waymo/answer/14298153?hl=en", "publisher": "Waymo Help", "date": "Undated current guidance", "lastVerified": "2026-10-12", "note": "Terminal pickup guidance reviewed October 12: A/B Departures and Arrivals outer curb near Rideshare Zone 2. Its earlier invitation restriction is superseded by the October 14 opening announcement." }, { "id": "travel-freeways", "label": "Freeway access and route preview", "href": "https://support.google.com/waymo/answer/16580405?hl=en", "publisher": "Waymo Help", "date": "Undated current guidance", "lastVerified": "2026-10-12", "note": "Access is limited and gradually rolled out; access does not mean every trip uses a freeway." }, { "id": "travel-pickup", "label": "Pickup, walking distance and pullover locations", "href": "https://support.google.com/waymo/answer/9696059?hl=en", "publisher": "Waymo Help", "date": "Undated current guidance", "lastVerified": "2026-10-12", "note": "Pickup/dropoff can require walking; selected spots, no-show and accessibility settings affect the door-to-door trip." }, { "id": "travel-pricing", "label": "Trip pricing and current fare estimates", "href": "https://support.google.com/waymo/answer/9059184?hl=en", "publisher": "Waymo Help", "date": "Undated current guidance", "lastVerified": "2026-10-12", "note": "Distance, duration, demand, booking, applicable fees and trip changes can affect price. Published Las Vegas rates are not used as Texas rates." }, { "id": "travel-business-profile", "label": "Individual business profiles and sponsored-ride eligibility", "href": "https://support.google.com/waymo/answer/15128101?hl=en", "publisher": "Waymo Help", "date": "Undated current guidance", "lastVerified": "2026-10-12", "note": "Separate payment method and verified business email; employer discounts require an actual eligible program and the correct profile." }, { "id": "travel-business-program", "label": "Waymo for Business: organizational programs", "href": "https://blog.waymo.com/business/", "publisher": "Waymo", "date": "Undated current program page", "lastVerified": "2026-10-12", "note": "Named markets in the public program description do not include Texas at review. An Other city inquiry option does not establish a contract or local program eligibility." }, { "id": "zoox-austin-rollout", "label": "Purpose-built robotaxi arrives in Austin", "href": "https://zoox.com/journal/zoox-robotaxi-is-now-in-austin", "publisher": "Zoox", "date": "2026-03-25", "lastVerified": "2026-10-12", "note": "Initial employees/family/friends stage; later-2026 Explorers access is a plan, not proof it opened." }, { "id": "zoox-dallas-testing", "label": "Dallas and Phoenix testing expansion", "href": "https://zoox.com/journal/zoox-expanding-testing-dallas-phoenix", "publisher": "Zoox", "date": "2026-03-09", "lastVerified": "2026-10-12", "note": "Retrofitted SUV mapping then autonomous testing with a safety driver; purpose-built robotaxi testing and depots were planned." }, { "id": "zoox-test-fleet", "label": "The role and phases of the Zoox testing fleet", "href": "https://zoox.com/journal/autonomous-zoox-testing-vehicle", "publisher": "Zoox", "date": "2023-10-18; revised 2026-03", "lastVerified": "2026-10-12", "note": "Retrofitted SUVs with a safety driver; no plans for public testing-fleet rides or driverless testing SUVs. Later Houston announcement adds scope beyond March's location list." }, { "id": "zoox-operating-areas", "label": "Operating-area maps include testing", "href": "https://zoox.com/zoox-operating-areas", "publisher": "Zoox", "date": "Undated current map page", "lastVerified": "2026-10-12", "note": "Maps show where a robotaxi may be seen, including testing. An Austin map is not evidence of public rider admission." }, { "id": "zoox-app-access", "label": "Zoox app availability and city navigation", "href": "https://zoox.com/app", "publisher": "Zoox", "date": "Undated current app page", "lastVerified": "2026-10-12", "note": "App listed as available through US App Store and US Google Play; Austin link does not create city access." }, { "id": "zoox-vehicle-and-support", "label": "Purpose-built vehicle and rider support", "href": "https://zoox.com/know-your-ride", "publisher": "Zoox", "date": "Undated current vehicle page", "lastVerified": "2026-10-12", "note": "Bidirectional design, four-wheel steering and live rider assistance are company-described features; no Texas performance or response-time guarantee." }, { "id": "zoox-commercial-grant", "label": "NHTSA grant: conditions for commercial deployment", "href": "https://www.govinfo.gov/content/pkg/FR-2026-07-31/html/2026-15485.htm", "publisher": "NHTSA / Federal Register", "date": "2026-07-31", "lastVerified": "2026-10-19", "note": "Effective through July 31, 2028; commercial introduction ceiling and simultaneous-operation conditions differ. Safety-equivalence analysis is limited to specific FMVSS exemptions. X.A specifies the public docket; X.G binds lifetime operational control and limits transfer/licensing. Applicable Texas-specific Operational Authorization not established." }, { "id": "zoox-commercial-transition", "label": "Zoox announces the commercial exemption", "href": "https://zoox.com/journal/zoox-nhtsa-part-555-commercial-exemption", "publisher": "Zoox", "date": "2026-07-30", "lastVerified": "2026-10-12", "note": "Distinguishes 2025 demonstration path from the commercial exemption and says further state requirements remain; no Texas fare launch asserted." }, { "id": "permit-code", "label": "Texas Transportation Code Chapter 545, Subchapter J", "href": "https://tcss.legis.texas.gov/resources/TN/htm/TN.545.htm", "publisher": "Texas Legislature", "date": "Current code; SB2807 amendments effective 2025-09-01", "lastVerified": "2026-10-19", "note": "Sections 545.451–545.459. Governing definitions, authorization, maintenance, collision and commercial-vehicle duties; agency implementation dates are separately verified." }, { "id": "permit-program", "label": "TxDMV Automated Vehicles Regulatory Program", "href": "https://www.txdmv.gov/AVprogram", "publisher": "Texas Department of Motor Vehicles", "date": "Undated current program page", "lastVerified": "2026-10-19", "note": "Reports May 28, 2026 enforcement, application process, no authorization fee, continuing updates and the current Truck Stop lookup/complaint route. Read with the statute." }, { "id": "permit-enforcement", "label": "Texas begins enforcement of commercial automated-vehicle requirements", "href": "https://www.txdmv.gov/sites/default/files/body-files/2026-06-02_Automated_Vehicle_Enforcement_System.pdf", "publisher": "Texas Department of Motor Vehicles", "date": "2026-06-02", "lastVerified": "2026-10-12", "note": "One-page announcement confirms enforcement and public complaints are implemented; not merely a projected board timetable." }, { "id": "permit-lookup", "label": "TxMCCS Truck Stop: motor-carrier and AV-operator lookup", "href": "https://txmccs.txdmv.gov/truckstop", "publisher": "Texas Department of Motor Vehicles", "date": "Undated current public portal", "lastVerified": "2026-10-12", "note": "Actual rendered portal verified with search and complaint links. Old /automated-vehicles/operators URL returned a rendered 404; no exhaustive search or fleet-level approval audit was performed." }, { "id": "permit-sb2807", "label": "SB 2807 enrolled text and implementation provisions", "href": "https://capitol.texas.gov/tlodocs/89R/billtext/html/SB02807F.HTM", "publisher": "Texas Legislature", "date": "2025 session; effective 2025-09-01", "lastVerified": "2026-10-12", "note": "Section 12 separates initial law effectiveness from compliance after agency rules; current agency announcement supplies the implemented May 28 date." }, { "id": "permit-beacon-exemption", "label": "FMCSA final warning-beacon exemption and operating conditions", "href": "https://www.govinfo.gov/content/pkg/FR-2026-10-09/html/2026-20734.htm", "publisher": "FMCSA / Federal Register", "date": "2026-10-09; effective 2026-10-07–2031-10-07", "lastVerified": "2026-10-13", "note": "91 FR 64736–64741, VI.B–C: prior notice for other carriers, validated domain, excluded cargo/passenger work, equipment and activation conditions. This replaces specified warning-device requirements; it is not a general driverless approval or recovery-time guarantee." }, { "id": "permit-texas-carrier-incorporation", "label": "37 TAC §4.11: current commercial-vehicle incorporation rule", "href": "https://texas-sos.appianportalsgov.com/rules-and-meetings?recordId=211918&queryAsDate=10%2F13%2F2026&interface=VIEW_TAC_SUMMARY&$locale=en_US", "publisher": "Texas Secretary of State / Texas Department of Public Safety", "date": "2023-01-08", "lastVerified": "2026-10-13", "note": "Official current rendered text: §4.11(a) incorporates federal amendments/interpretations through September 1, 2022; (b)(6) substitutes the DPS director for intrastate vehicles. That text does not automatically adopt a later federal exemption." }, { "id": "permit-texas-carrier-exceptions", "label": "37 TAC §4.12: current Texas exemptions and exceptions", "href": "https://texas-sos.appianportalsgov.com/rules-and-meetings?recordId=226974&queryAsDate=10%2F13%2F2026&interface=VIEW_TAC_SUMMARY&$locale=en_US", "publisher": "Texas Secretary of State / Texas Department of Public Safety", "date": "2025-12-11", "lastVerified": "2026-10-13", "note": "Complete current exception list inspected, latest amendment effective December 11, 2025. The inspected rule contains no beacon relief or blanket prospective adoption of federal exemptions; this bounded reading does not rule out every other legal instrument." } ], "claims": [ { "id": "avmap-1", "claim": "Waymo Dallas/Houston public-access openings were dated August 4/August 20, 2026; San Antonio and SAT opened to all riders on October 14. Austin remains available through eligible Uber requests.", "status": "dated operator update", "qualification": "A city-level opening is not an individual trip guarantee.", "sourceDate": "2026-10-14", "sources": [ { "url": "https://blog.waymo.com/blog/shorts/dallas-open-to-all/", "date": "2026-08-04", "pinpoint": "Dated public-access announcement. Love Field and freeway statements were testing/future plans at that date; do not silently treat them as current passenger availability." }, { "url": "https://blog.waymo.com/blog/shorts/houston-open-to-all/", "date": "2026-08-20", "pinpoint": "Dated open-public-access announcement; not a guarantee of any address or individual trip." }, { "url": "https://support.google.com/waymo/answer/9059119?hl=en", "date": "Undated current support page", "pinpoint": "Rechecked October 14: Austin Uber channel; San Antonio no longer labeled gradually adding riders. The dated opening announcement establishes current admission; service maps remain trip-specific." }, { "url": "https://support.google.com/waymo/answer/16011725?hl=en", "date": "Undated current support page", "pinpoint": "Eligible Uber ride request, preference and matched offer differ from guaranteed vehicle selection." }, { "url": "https://support.google.com/waymo/answer/18765688", "date": "2026-10-14", "pinpoint": "Dated San Antonio/SAT all-rider opening; invitation requirement removed." } ], "recheck": "Relevant provider access/role/domain change, official record change or actual pilot evidence" }, { "id": "avmap-2", "claim": "Zoox Austin current page remains coming-soon/waitlist; September 1 Houston announcement begins with manual mapping/test fleet.", "status": "current access/announced sequence", "qualification": "No general-public Texas booking or purpose-built deployment completion inferred.", "sources": [ { "url": "https://zoox.com/austin", "date": "Undated current city page", "pinpoint": "Full rendered body says coming soon and invites app waitlist entry. A city name/menu entry alone does not establish bookable public rides." }, { "url": "https://zoox.com/journal/zoox-now-testing-houston-san-diego", "date": "2026-09-01", "pinpoint": "Retrofitted test fleet/manual mapping first; autonomous testing and purpose-built vehicles are later stages. Twelve-location presence is not twelve open ride-hail markets." } ], "recheck": "Relevant provider access/role/domain change, official record change or actual pilot evidence" }, { "id": "avmap-3", "claim": "Tesla current Robotaxi support lists limited Austin/Dallas/Houston service and self-booking; FSD (Supervised) requires a driver.", "status": "operator guidance", "qualification": "No citywide coverage, assigned platform or corporate-dispatch permission assumed.", "sources": [ { "url": "https://www.tesla.com/support/robotaxi", "date": "Undated current support page", "pinpoint": "Lists limited Austin, Dallas, Houston service areas, self-booking, vehicle-specific rules and app fare estimates. Does not establish a citywide service guarantee or trip-level vehicle assignment." }, { "url": "https://www.tesla.com/support/fsd", "date": "Undated current support page; official indexed body checked2026-10-12", "pinpoint": "Official support states active driver supervision and that the feature does not make the vehicle autonomous. Direct retrieval encountered protection/timeout; indexed official text supplies this narrow distinction, not comparative collision-rate evidence." } ], "recheck": "Relevant provider access/role/domain change, official record change or actual pilot evidence" }, { "id": "avmap-4", "claim": "Current Uber Dallas guidance identifies Avride service north of Trinity River, an onboard specialist able to take control and three rear-seat riders; May’s reviewed Arlington evidence leaves public access unresolved.", "status": "current issuer guidance plus unresolved May access", "qualification": "Historical nine-square-mile launch area is separate. Qualifying request and match still need verification; omission from May’s list does not prove no activity.", "sources": [ { "url": "https://www.uber.com/us/en/newsroom/avride-on-uber/", "date": "2025-12-03", "pinpoint": "Launch described nine square miles and an onboard specialist behind the wheel, with future driverless operation. Those are dated launch conditions, not an assertion of unchanged October coverage or onboard mode." }, { "url": "https://www.uber.com/us/en/r/autonomous/dallas-tx-us/", "date": "Undated current service page; checked 2026-10-13", "pinpoint": "Eligible opt-in matching; Central Dallas north of Trinity River; specialist behind the wheel; three rear-seat riders and seven-minute boarding window" }, { "url": "https://maymobility.com/posts/may-mobility-launches-new-av-architecture/", "date": "2026-05-20", "pinpoint": "Release describes Arlington Uber deployment as upcoming. Issuer-wide rides/miles are not used as Texas-only or driverless-only metrics." }, { "url": "https://maymobility.com/locations/", "date": "Undated current locations page", "pinpoint": "Current active list read at review includes Atlanta, Grand Rapids and Eden Prairie, without an Arlington public-booking listing. That absence warrants confirmation; it does not independently prove no Texas operations." } ], "recheck": "Relevant provider access/role/domain change, official record change or actual pilot evidence" }, { "id": "avmap-5", "claim": "Federal raw crash counts are not exposure-normalized; DPS responder catalog is not an open-service census.", "status": "agency evidence and interpretation", "qualification": "No comparative safety ranking, exhaustiveness or permit status inferred.", "sources": [ { "url": "https://www.dps.texas.gov/section/cav/connected-autonomous-vehicles", "date": "Page labeled2026-02-27; current catalog checked2026-10-12", "pinpoint": "Includes multiple passenger/freight platforms. Posting is not an operator census, authorization finding or commercial-booking map." }, { "url": "https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting", "date": "2025 amendment effective2025-06-16; current data through2026-08-17", "pinpoint": "Different reporting conditions and exposure denominators prevent a valid simple ranking from raw counts; information can be incomplete and updated." } ], "recheck": "Relevant provider access/role/domain change, official record change or actual pilot evidence" }, { "id": "avmap-6", "claim": "Declared 200-trip model leaves 120 eligible AV trips, baseline $5,600 versus mix $4,640; 10$48 exceptions yield $5,120 and 20 yield $5,600.", "status": "declared hypothetical", "qualification": "No actual quote, exception rate or vendor choice; original AV charge retained and refunds separate. Fare cash and allocated exception time are shown separately; normal trip time is excluded/held equal.", "sources": [], "recheck": "Relevant provider access/role/domain change, official record change or actual pilot evidence" }, { "id": "avmap-7", "claim": "NTSB’s preliminary January 12 Austin account describes a Waymo vehicle passing a stopped school bus after an incorrect remote-assistance response; no crash occurred. The reviewed page lists the investigation as ongoing.", "status": "preliminary official investigation; status observed 2026-10-13", "qualification": "Not final probable cause, proof a defect persists today, a measured rate or a provider ranking. Remote assistance is advice/information, not automatically remote driving.", "sources": [ { "url": "https://www.ntsb.gov/investigations/Pages/HWY26FH007.aspx", "date": "2026-03-03", "pinpoint": "What Happened paragraphs 1–8; Investigation Details; footnote 4" } ], "recheck": "Final findings, corrective evidence or applicable operating restrictions change." }, { "id": "avmap-8", "claim": "NHTSA announced a Cybercab self-certification audit following Austin commercial deployment on September 4, 2026.", "status": "dated official inquiry opening", "qualification": "Does not establish violation, service suspension or present inquiry status. Underlying technical response and later disposition were not verified.", "sources": [ { "url": "https://www.nhtsa.gov/press-releases/investigation-tesla-cybercab-self-certification", "date": "2026-09-04", "pinpoint": "Opening; How It Works; Additional Information" } ], "recheck": "Official disposition, remedy, compliance basis or restrictions change." }, { "id": "avmap-9", "claim": "The declared model’s combined saving reaches zero at 20 paid fallbacks out of 120 AV attempts, or 16.7%.", "status": "calculated hypothetical", "qualification": "Original AV charge retained; rate is a break-even sensitivity, not observed provider performance.", "sources": [], "recheck": "Actual fares, refunds, eligible requests and incremental time replace assumptions." }, { "id": "itinerary-example", "claim": "Suggested illustrative buyer workflow: Build a conference plan one journey at a time. No private provider contract, actual site design, service entitlement or observed performance inferred.", "status": "editorial recommendation and illustrative workflow", "qualification": "Suggested purchaser analysis; all original source dates, access restrictions, legal conditions and unresolved provider-specific facts remain in the article.", "sources": [], "recheck": "Change to the proposed itinerary, route, contract, fleet stage, accepted volume or stated model input." } ], "absorbedEvidence": [ { "articleSlug": "texas-waymo-business-travel", "sourceCutoff": "2026-10-14", "evidenceRole": "Historical supporting claim ledger from an absorbed article; claims retain their original dates, qualifications and scope.", "claims": [ { "id": "waymo-01", "claim": "Dallas opened to all riders on August 4, 2026.", "status": "dated issuer announcement", "qualification": "Invitation removal does not establish route or vehicle supply.", "sources": [ { "url": "https://blog.waymo.com/blog/shorts/dallas-open-to-all/", "date": "2026-08-04", "pinpoint": "Opening paragraph" } ], "recheck": "Current all-rider access changes." }, { "id": "waymo-02", "claim": "Houston opened to all riders on August 20, 2026.", "status": "dated issuer announcement", "qualification": "No airport or statewide coverage implied.", "sources": [ { "url": "https://blog.waymo.com/blog/shorts/houston-open-to-all/", "date": "2026-08-20", "pinpoint": "Opening paragraph" } ], "recheck": "Current all-rider access changes." }, { "id": "waymo-03", "claim": "Waymo’s October 14 announcement removes the invitation requirement in San Antonio and opens SAT to all riders; Austin’s Uber channel is retained.", "status": "dated operator update", "qualification": "Admission policy does not guarantee route coverage, dispatch, availability or comparative safety.", "sourceDate": "2026-10-14", "sources": [ { "url": "https://support.google.com/waymo/answer/9059119?hl=en", "date": "Undated current guidance", "pinpoint": "Rechecked October 14: Austin Uber channel; San Antonio no longer labeled gradually adding riders. The dated opening announcement establishes current admission; service maps remain trip-specific." }, { "url": "https://support.google.com/waymo/answer/18765688", "date": "2026-10-14", "pinpoint": "San Antonio/SAT opening announcement, October 14" } ], "recheck": "San Antonio admission or Austin channel changes." }, { "id": "waymo-04", "claim": "Austin eligible Uber requests can receive an accepted Waymo match; preference is not reservation.", "status": "current platform/issuer instructions", "qualification": "Both endpoints and nearby vehicle conditions apply. Products can vary by region.", "sources": [ { "url": "https://support.google.com/waymo/answer/16011725?hl=en", "date": "Undated current guidance", "pinpoint": "How can I ride; Austin service area" } ], "recheck": "Eligibility, product, preference or distribution changes." }, { "id": "waymo-05", "claim": "Waymo’s October 14 notice opens SAT airport to all riders; terminal guidance and actual availability remain trip-specific.", "status": "dated operator update", "qualification": "Admission policy does not guarantee route coverage, dispatch, availability or comparative safety.", "sourceDate": "2026-10-14", "sources": [ { "url": "https://support.google.com/waymo/answer/14298153?hl=en", "date": "Undated current guidance", "pinpoint": "San Antonio International Airport; A/B Departures and Arrivals outer curb Zone 2" }, { "url": "https://support.google.com/waymo/answer/18765688", "date": "2026-10-14", "pinpoint": "San Antonio/SAT opening announcement, October 14" } ], "recheck": "Airport access, terminal instructions or San Antonio admissions change." }, { "id": "waymo-06", "claim": "August 4 Dallas notice describes Love Field and freeway activity as testing/future public routes.", "status": "historical stage description", "qualification": "No current public Love Field, DFW, Houston-airport or AUS ride verified in this research.", "sources": [ { "url": "https://blog.waymo.com/blog/shorts/dallas-open-to-all/", "date": "2026-08-04", "pinpoint": "Second paragraph" } ], "recheck": "A current public route/airport announcement supersedes testing." }, { "id": "waymo-07", "claim": "Freeway access is limited; access does not guarantee a freeway route.", "status": "current undated issuer guidance", "qualification": "Preview each route; no particular Texas account's highway eligibility verified.", "sources": [ { "url": "https://support.google.com/waymo/answer/16580405?hl=en", "date": "Undated current guidance", "pinpoint": "How to get a freeway trip; Not all routes" } ], "recheck": "Access or route instructions change." }, { "id": "waymo-08", "claim": "Pickup/dropoff may require walking; minimize-walking can trade off against ride time.", "status": "current undated issuer guidance", "qualification": "No observed walking or wait distribution.", "sources": [ { "url": "https://support.google.com/waymo/answer/9696059?hl=en", "date": "Undated current guidance", "pinpoint": "You may need to walk a bit" } ], "recheck": "Pickup rules or operating conditions materially change." }, { "id": "waymo-09", "claim": "Austin WAV option described in the instructions is manually driven.", "status": "current undated issuer guidance", "qualification": "No statewide autonomous accessible-fleet inference.", "sources": [ { "url": "https://support.google.com/waymo/answer/16011725?hl=en", "date": "Undated current guidance", "pinpoint": "Can I get a Wheelchair-accessible Vehicle through Uber?" } ], "recheck": "Vehicle or accessible-service scope changes." }, { "id": "waymo-10", "claim": "Accepted Waymo match has the price of the eligible Uber product requested.", "status": "dated platform pricing explanation", "qualification": "Within-product comparison; not a fixed fare, blanket cheapest-price result or direct-app Texas fare.", "sources": [ { "url": "https://www.uber.com/us/en/blog/waymo-on-uber/", "date": "2026-07-24", "pinpoint": "Will there be a difference between the price..." } ], "recheck": "Platform pricing or eligible products change." }, { "id": "waymo-11", "claim": "Waymo directs travelers to in-app estimates; route, demand and applicable fees affect pricing.", "status": "current undated issuer guidance", "qualification": "No live quotation and no Las Vegas tariff applied to Texas.", "sources": [ { "url": "https://support.google.com/waymo/answer/9059184?hl=en", "date": "Undated current guidance", "pinpoint": "Trip pricing factors; Get an estimated price" } ], "recheck": "Texas tariff, fees or fare guidance changes." }, { "id": "waymo-12", "claim": "Business profile supports a separate payment method; sponsored discounts depend on an eligible employer program and correct profile.", "status": "current undated issuer guidance", "qualification": "Profile and rider access do not create an employer agreement.", "sources": [ { "url": "https://support.google.com/waymo/answer/15128101?hl=en", "date": "Undated current guidance", "pinpoint": "Opening; Check if eligible; profile discount instructions" } ], "recheck": "Program eligibility, payment workflow or refunds change." }, { "id": "waymo-13", "claim": "Waymo for Business's public named-market description omits Texas at review.", "status": "observed scope of undated program page", "qualification": "Does not prove all Texas enterprise arrangements are unavailable. Other-city inquiry is not a contract.", "sources": [ { "url": "https://blog.waymo.com/business/", "date": "Undated current program page", "pinpoint": "Program opening description and City form" } ], "recheck": "Documented Texas offer or named-market scope changes." }, { "id": "waymo-14", "claim": "The declared 200-trip base case totals $6,400 versus $6,200, and the 40-fallback sensitivity totals $7,440.", "status": "calculated hypothetical", "qualification": "No company quote, observed failure frequency, safety comparison or predicted return. Time value is an allocated opportunity cost, not guaranteed payroll savings.", "sources": [], "recheck": "Actual fares, comparable door-to-door time, completed/failed requests or organizational payment evidence replaces any input." }, { "id": "waymo-15", "claim": "NTSB’s preliminary January 12 Austin account describes a Waymo vehicle passing a stopped school bus after an incorrect remote-assistance response; no crash occurred. The reviewed page lists the investigation as ongoing.", "status": "preliminary official investigation; status observed 2026-10-13", "qualification": "Not final probable cause, proof a defect persists today, a measured rate or a provider ranking. Remote assistance is advice/information, not automatically remote driving.", "sources": [ { "url": "https://www.ntsb.gov/investigations/Pages/HWY26FH007.aspx", "date": "2026-03-03", "pinpoint": "What Happened paragraphs 1–8; Investigation Details; footnote 4" } ], "recheck": "Final findings, corrective evidence or applicable operating restrictions change." }, { "id": "itinerary-approval", "claim": "Suggested illustrative buyer workflow: Give the traveler a usable departure plan. No private provider contract, actual site design, service entitlement or observed performance inferred. Separate invented timetable: 10-minute pickup + 25-minute travel + 10-minute access/buffer = 45 minutes; a 10 a.m. meeting gives a 9:15 a.m. latest switch.", "status": "editorial recommendation and illustrative workflow", "qualification": "Suggested purchaser analysis; all original source dates, access restrictions, legal conditions and unresolved provider-specific facts remain in the article. Timetable inputs are independent of the fare-and-wait comparison and are not provider performance estimates.", "sources": [], "recheck": "Change to the proposed itinerary, route, contract, fleet stage, accepted volume or stated model input." } ] }, { "articleSlug": "texas-zoox-market-entry-business", "sourceCutoff": "2026-10-13", "evidenceRole": "Historical supporting claim ledger from an absorbed article; claims retain their original dates, qualifications and scope.", "claims": [ { "id": "zoox-01", "claim": "Austin's current city page says coming soon and directs users to a waitlist.", "status": "current rendered issuer invitation", "qualification": "Does not establish general public booking. The page has no publication date.", "sources": [ { "url": "https://zoox.com/austin", "date": "Undated current city page", "pinpoint": "Zoox is coming soon; app/waitlist invitation" } ], "recheck": "Current admission page or actual local rider access changes." }, { "id": "zoox-02", "claim": "March 25 Austin purpose-built rollout began with employees/family/friends; later-year Explorers access was planned.", "status": "dated issuer rollout with future plan", "qualification": "No completion of that future admission milestone inferred.", "sources": [ { "url": "https://zoox.com/journal/zoox-robotaxi-is-now-in-austin", "date": "2026-03-25", "pinpoint": "The journey so far" } ], "recheck": "A later dated source verifies a new admission or service stage." }, { "id": "zoox-03", "claim": "March 9 Dallas notice describes retrofitted SUV mapping/testing and planned depots.", "status": "dated issuer testing expansion", "qualification": "Future purpose-built testing is not a public ride commitment or delivered fleet count.", "sources": [ { "url": "https://zoox.com/journal/zoox-expanding-testing-dallas-phoenix", "date": "2026-03-09", "pinpoint": "Deploying our Zoox Testing Fleet; opening expansion" } ], "recheck": "Current vehicle stage, public booking or executed facility evidence changes." }, { "id": "zoox-04", "claim": "September 1 Houston announcement begins with manual mapping and later test/robotaxi stages.", "status": "dated issuer testing expansion", "qualification": "Depots and local hiring remain plans; no ready passenger fleet inferred.", "sources": [ { "url": "https://zoox.com/journal/zoox-now-testing-houston-san-diego", "date": "2026-09-01", "pinpoint": "Opening; operations will begin; physical operations plans" } ], "recheck": "Later Houston stage or actual facility commitment is documented." }, { "id": "zoox-05", "claim": "Testing SUVs have safety drivers; Zoox says no plans for public rides or driverless operation of that fleet.", "status": "issuer testing methodology", "qualification": "March revision's location list predates September Houston addition; no comparative safety metric inferred.", "sources": [ { "url": "https://zoox.com/journal/autonomous-zoox-testing-vehicle", "date": "2023-10-18; revised 2026-03", "pinpoint": "Safety is foundational to testing; no plans paragraph" } ], "recheck": "Testing-fleet role or methodology changes." }, { "id": "zoox-06", "claim": "Operating maps include robotaxi testing areas.", "status": "current rendered issuer map explanation", "qualification": "Map presence is not a public rider-admission guarantee.", "sources": [ { "url": "https://zoox.com/zoox-operating-areas", "date": "Undated current map page", "pinpoint": "Opening explanation" } ], "recheck": "Map scope or service admission changes." }, { "id": "zoox-07", "claim": "Zoox app distribution is stated as US App Store/Google Play.", "status": "current rendered issuer app instructions", "qualification": "App installation does not create local rider access; international-device eligibility not tested.", "sources": [ { "url": "https://zoox.com/app", "date": "Undated current app page", "pinpoint": "App availability statement" } ], "recheck": "Store distribution or account/booking requirements change." }, { "id": "zoox-08", "claim": "Vehicle page describes bidirectional design, four-wheel steering and live assistance.", "status": "current issuer design/support description", "qualification": "No measured Texas pickup or support-response guarantee.", "sources": [ { "url": "https://zoox.com/know-your-ride", "date": "Undated current vehicle page", "pinpoint": "A smooth operator; Support when you need it" } ], "recheck": "Vehicle generation, boarding or rider support changes." }, { "id": "zoox-09", "claim": "Commercial grant runs July 31 2026–July 31 2028; ≤2,500 commercial introductions per 12 months.", "status": "official grant", "qualification": "Separate Operational Authorizations limit simultaneous operations; no Texas allocation inferred.", "sources": [ { "url": "https://www.govinfo.gov/content/pkg/FR-2026-07-31/html/2026-15485.htm", "date": "2026-07-31", "pinpoint": "DATES; Executive Summary; VIII.D (1)–(2)" } ], "recheck": "Grant or Operational Authorization changes." }, { "id": "zoox-10", "claim": "NHTSA's safety-equivalence analysis covers specific exempted FMVSS requirements.", "status": "official scope qualification", "qualification": "No blanket comparative ADS safety conclusion.", "sources": [ { "url": "https://www.govinfo.gov/content/pkg/FR-2026-07-31/html/2026-15485.htm", "date": "2026-07-31", "pinpoint": "Executive Summary, safety-equivalency scope paragraphs" } ], "recheck": "Grant analysis or relevant official finding changes." }, { "id": "zoox-11", "claim": "Section X.G binds lifetime Zoox operational control and restricts sale, transfer, licensing and public-road operation except on NHTSA-authorized terms.", "status": "binding official grant condition", "qualification": "No independent third-party ownership/operation entitlement or Texas allocation inferred.", "sources": [ { "url": "https://www.govinfo.gov/content/pkg/FR-2026-07-31/html/2026-15485.htm", "date": "2026-07-31", "pinpoint": "X.G Sale and Transfer of Possession" } ], "recheck": "Ownership, vehicle or service model changes." }, { "id": "zoox-12", "claim": "July 30 company notice distinguishes demonstration and commercial paths.", "status": "dated issuer transition notice", "qualification": "Further existing-market state requirements described; no Texas fare launch asserted.", "sources": [ { "url": "https://zoox.com/journal/zoox-nhtsa-part-555-commercial-exemption", "date": "2026-07-30", "pinpoint": "The exemption process" } ], "recheck": "New commercial market, fare or authorization evidence." }, { "id": "zoox-13", "claim": "Declared available and occupied hours yield 704 completed vehicle trips; lower occupied share yields 512, a reduction of 192.", "status": "calculated hypothetical", "qualification": "Same completed-trip population for hours and duration; no actual fleet, cost, fare, occupancy or peak-capacity estimate.", "sources": [], "recheck": "Actual completed-trip population, available service-hours, occupied share and trip duration replace model inputs." }, { "id": "zoox-14", "claim": "Grant X.A specifies public Operational Authorizations in docket NHTSA-2025-0523.", "status": "official oversight condition", "qualification": "No current Texas-specific instrument retrieved; failure to retrieve is not evidence one does not exist.", "sources": [ { "url": "https://www.govinfo.gov/content/pkg/FR-2026-07-31/html/2026-15485.htm", "date": "2026-07-31", "pinpoint": "X.A Operational Authorization" } ], "recheck": "Applicable area/route authorization changes or becomes retrievable." }, { "id": "depot-commitment-example", "claim": "Suggested illustrative buyer workflow: Turn a depot enquiry into a staged property proposal. No private provider contract, actual site design, service entitlement or observed performance inferred.", "status": "editorial recommendation and illustrative workflow", "qualification": "Suggested purchaser analysis; all original source dates, access restrictions, legal conditions and unresolved provider-specific facts remain in the article.", "sources": [], "recheck": "Change to the proposed itinerary, route, contract, fleet stage, accepted volume or stated model input." } ] }, { "articleSlug": "texas-automated-vehicle-authorization", "sourceCutoff": "2026-10-13", "evidenceRole": "Historical supporting claim ledger from an absorbed article; claims retain their original dates, qualifications and scope.", "claims": [ { "id": "avlaw-01", "claim": "Commercial driverless authorization requirements became enforceable May 28, 2026, with implemented public complaints confirmed June 2.", "status": "implemented", "qualification": "September 1, 2025 statutory effectiveness differs from compliance after implementing rules.", "sources": [ { "url": "https://www.txdmv.gov/AVprogram", "pinpoint": "Authorization requirements and enforcement" }, { "url": "https://www.txdmv.gov/sites/default/files/body-files/2026-06-02_Automated_Vehicle_Enforcement_System.pdf", "date": "2026-06-02", "pinpoint": "Main announcement" } ], "recheck": "Governing law or agency implementation change" }, { "id": "avlaw-02", "claim": "Commercial authorization concerns passenger/property transport furthering a commercial enterprise on public highways/streets without a human driver.", "status": "current law", "qualification": "Classify the actual vehicle, engaged feature, purpose and human role; do not infer from a brand label.", "sources": [ { "url": "https://tcss.legis.texas.gov/resources/TN/htm/TN.545.htm", "pinpoint": "§545.455(c)" } ], "recheck": "Scope amendment or applicable decision" }, { "id": "avlaw-03", "claim": "Authorization is nonexpiring but material information must be updated within 30 days, with separate document and safety enforcement paths.", "status": "current law", "qualification": "The 30-day information deadline is not a universal safety cure period.", "sources": [ { "url": "https://tcss.legis.texas.gov/resources/TN/htm/TN.545.htm", "pinpoint": "§545.456(d)–(h); §545.459" } ], "recheck": "Material supplier record or controlling requirements change" }, { "id": "avlaw-04", "claim": "Current public lookup is TxMCCS Truck Stop; prior /automated-vehicles/operators renders 404.", "status": "observed interface", "qualification": "No exhaustive holder/vehicle audit or census performed.", "sources": [ { "url": "https://txmccs.txdmv.gov/truckstop", "pinpoint": "Rendered lookup landing page" }, { "url": "https://www.txdmv.gov/AVprogram", "pinpoint": "Current enforcement/lookup links" } ], "recheck": "Portal navigation or API migration" }, { "id": "avlaw-05", "claim": "DPS publishes platform-specific responder plans; a catalog entry alone is not booking or current authorization evidence.", "status": "posted plans and procurement interpretation", "qualification": "Use the plan for the actual vehicle, not merely the company name.", "sources": [ { "url": "https://www.dps.texas.gov/section/cav/connected-autonomous-vehicles", "pinpoint": "First Responder Interaction Plans" } ], "recheck": "Relevant platform/plan changes" }, { "id": "avlaw-06", "claim": "Pilot preparedness is $5,500; one 60-load replacement week adds $7,200; combined incremental stress cost $12,700 above common $324,000 freight.", "status": "declared hypothetical", "qualification": "Rates, hours, loads and interruption are invented. $3,100 values existing staff time; $2,400 is an assumed paid backup-capacity reservation; $7,200 is the incremental paid replacement premium. $12,700 is economic burden above common freight, not all-cash spending. No frequency or quote inferred.", "sources": [], "recheck": "Actual staffing, contract, service or replacement evidence" }, { "id": "avlaw-07", "claim": "FMCSA grants a limited cab-mounted warning-beacon exemption effective October 7, 2026–October 7, 2031; other Level 4 carriers must give prior written notice.", "status": "official final exemption", "qualification": "Specific warning-device alternative only. Other federal rules continue; no competitor participation or fleet compliance verified. Intrastate treatment must be resolved separately from federal interstate preemption.", "sources": [ { "url": "https://www.govinfo.gov/content/pkg/FR-2026-10-09/html/2026-20734.htm", "date": "2026-10-09", "pinpoint": "DATES; VI.A–C.1–5; VI.D" } ], "recheck": "Current exemption, participating carrier evidence, cargo, configuration, domain or state intrastate treatment changes." }, { "id": "avlaw-08", "claim": "NHTSA announced a Cybercab self-certification audit following Austin commercial deployment on September 4, 2026.", "status": "dated official inquiry opening", "qualification": "Does not establish violation, service suspension or present inquiry status. Underlying technical response and later disposition were not verified.", "sources": [ { "url": "https://www.nhtsa.gov/press-releases/investigation-tesla-cybercab-self-certification", "date": "2026-09-04", "pinpoint": "Opening; How It Works; Additional Information" } ], "recheck": "Official disposition, remedy, compliance basis or restrictions change." }, { "id": "avlaw-09", "claim": "General §545.455(b) operating conditions remain distinct from the additional commercial driverless gate in (c); §545.452(b) bars local AV-operation franchises/regulation.", "status": "controlling statute", "qualification": "Does not establish individual compliance or general permission for property/airport access. Onboard observation alone is not a human driving role.", "sources": [ { "url": "https://tcss.legis.texas.gov/resources/TN/htm/TN.545.htm", "date": "Current code read 2026-10-13", "pinpoint": "545.452(b); 545.455(b)–(c); 545.456(b)(2)(C)" } ], "recheck": "Governing provision, actual driving role or applicable site/vehicle conditions change." }, { "id": "texas-intrastate-beacon-basis", "claim": "Official current §4.11 incorporates federal amendments through September 1, 2022; the complete inspected §4.12 exception list does not adopt the October 2026 beacon relief. Federal permission alone does not establish a Texas intrastate legal basis.", "status": "current official rendered rule text checked 2026-10-13; bounded interpretation", "qualification": "No exhaustive absence finding about other DPS instruments, no individual state permit process inferred, and no real shipment classification determined. Two Texas endpoints alone do not establish intrastate commerce.", "sources": [ { "url": "https://texas-sos.appianportalsgov.com/rules-and-meetings?recordId=211918&queryAsDate=10%2F13%2F2026&interface=VIEW_TAC_SUMMARY&$locale=en_US", "date": "2023-01-08", "pinpoint": "37 TAC §4.11(a), (b)(3), (b)(6), (c)" }, { "url": "https://texas-sos.appianportalsgov.com/rules-and-meetings?recordId=226974&queryAsDate=10%2F13%2F2026&interface=VIEW_TAC_SUMMARY&$locale=en_US", "date": "2025-12-11", "pinpoint": "37 TAC §4.12 entire exception list and source note" } ], "recheck": "Current Texas rule amendment, actual applicable relief instrument/interpretation, changed shipment classification or proposed warning-device arrangement." }, { "id": "service-change-example", "claim": "Suggested illustrative buyer workflow: Review a driverless service change before promising the new capacity. No private provider contract, actual site design, service entitlement or observed performance inferred.", "status": "editorial recommendation and illustrative workflow", "qualification": "Suggested purchaser analysis; all original source dates, access restrictions, legal conditions and unresolved provider-specific facts remain in the article.", "sources": [], "recheck": "Change to the proposed itinerary, route, contract, fleet stage, accepted volume or stated model input." } ] } ], "updateTriggers": [ "Provider rider admission, booking rules or service area changes", "Onboard role, platform or business payment program changes", "Actual trip costs and exception evidence diverge", "Official passenger-safety findings, remedies, certification inquiry disposition or restrictions change", "Zoox Texas rider admission or vehicle stage advances", "Federal Operational Authorization or exemption conditions change", "Executed depot, charging, supplier or service evidence arrives", "Governing law, agency rules or enforcement guidance changes", "Holder, fleet, responder plan or operating domain changes", "Actual interruption, replacement and restart evidence changes" ] }, { "slug": "texas-autonomous-trucking-operators", "title": "The Texas driverless truck has to finish the job", "canonical": "https://sulayman-bowles.dev/research/texas/texas-autonomous-trucking-operators", "pillar": "Autonomous mobility and freight", "reader": "Shippers, carriers, procurement and finance teams", "decision": "Buy a complete freight route with priced handoffs, recovery and backup", "sourceCutoff": "2026-10-13", "datePublished": "2026-10-13", "dateModified": "2026-10-19", "evidenceBoundary": "Method & limits: Operator records retain the October 12–13, 2026 review cutoff and their individual dates. Operating claims are attributed to issuers; no new freight trial, quote or comparative safety measurement is claimed. All costs, acceptance rates and exceptions in the route model are invented inputs. Economic totals include allocated staff time and lost contribution as labeled, alongside cash costs. The model concerns first-year completed shipments, not truck utilization or operator profit.", "opening": [ "Bot Auto reported a paid 230-mile load from northeast Houston to Hutchins on April 30, 2026, with no driver or observer in the cab. That is a shipment I can examine. I care more about its endpoints, cargo handoff and recovery arrangement than another chart of autonomous miles. A shipper buys a delivered load. [Company release](#source-bot-commercial).", "Texas now contains several different freight businesses under the autonomous label: regional store replenishment, Permian industrial deliveries and highway linehaul. I would shortlist operators by the job they accept today, then price the people and handoffs that remain around the truck. Removing the driver is valuable only to the extent that the complete route becomes cheaper or more useful." ], "sections": [ { "id": "operating-comparison", "title": "The freight job sorts the operators", "paragraphs": [ "Aurora reports public-road driverless freight. Gatik identifies recurring driverless regional networks. Kodiak’s industrial work and its highway program have different stages, while Waabi and PlusAI disclose people onboard. Those distinctions tell me where to begin a buying conversation." ], "table": { "caption": "Selected Texas freight programs: evidence available October 12, 2026", "columns": [ "Program", "Reviewed operation", "Procurement boundary" ], "rows": [ [ "Aurora", "Commercial public-road driverless freight; second-generation International LT launch July 22; some trips may carry rear-seat support staff", "Confirm platform, lane, endpoint and reserved capacity; support staff are not driving supervision" ], [ "Kodiak / Atlas", "Customer-owned driverless Permian industrial deliveries; 35 trucks reported at June 30", "Industrial domain differs from I-45 highway launch and proposed public-road expansion" ], [ "Kodiak highway / Charger", "I-45 driver-out launch targeted by end 2026; October 8 Laredo service has a safety driver", "Current highway freight and driverless highway availability are separate" ], [ "Gatik", "Driverless DFW/regional retail networks; June 8 PepsiCo disclosure confirms existing Texas operation", "Match box-truck capacity, stops, goods and store receiving requirements" ], [ "Bot Auto", "April 30 issuer report of paid 230-mile Houston–Hutchins load without onboard driver or observer", "Confirm current accepted endpoints, recurring slots, recovery and contracted terms" ], [ "Waabi / Volvo", "October 5 Warp freight directly to third-party Dallas–Houston facilities; observer in driver’s seat", "Customer freight is operating; the reviewed release does not establish driver-out operation" ], [ "PlusAI / International / Ryder", "March 31 supervised Laredo–Temple live-freight pilot; daily 600-mile route", "92% autonomous route coverage is supervised; September 3 issuer roadmap targets factory-built commercial launch in 2027" ], [ "Torc / Daimler", "DFW testing and fleet hub; closed-track driver-out validation; 2027 market-entry roadmap", "Testing and production intent do not establish an available driver-out freight slot" ], [ "Einride", "March SH 130 testbed MoU and Austin R&D cabless demonstration", "Company-reported approval and testbed are distinct from a contracted commercial Texas lane" ] ], "note": "The dated releases cited below control each row. Kodiak’s industrial and highway programs have different operating roles. Availability for a new customer requires a proposal." } }, { "id": "aurora", "title": "An empty seat is a precise claim", "paragraphs": [ "Aurora’s July 22 explanation says its second-generation International LT has an empty driver’s seat. A rear-seat roadside-support person may travel on some trips; Aurora says that person neither drives nor supervises driving. I would preserve that distinction in the tender. The staff member can be part of the service without being the driver. [Platform explanation](#source-aurora-faq).", "Its July shareholder letter describes driverless operations from Detmar’s Midland facility to Capital Sand’s Monahans mining site along I-20. Fueling and weigh-station work appear elsewhere as supervised testing. If a proposed lane needs either activity, the buyer needs its released configuration rather than an extrapolation from the Midland run. [Shareholder letter, pages 7–8](#source-aurora-q2).", "Aurora describes Transportation-as-a-Service as owning and operating the trucks while customers buy dedicated capacity; customer ownership is a future model. Kodiak’s Driver-as-a-Service instead puts the technology on customer-owned and operated trucks. The invoice is covering a different bundle of work. [Aurora model](#source-aurora-faq); [Kodiak arrangement](#source-kodiak-charger)." ] }, { "id": "kodiak", "title": "Permian work is ahead of the highway promise", "paragraphs": [ "Kodiak reported 35 Atlas-owned driverless trucks and more than 40,000 paid driverless hours at June 30. Atlas later announced a second Dune Express load-out point and targeted public-road work for early 2027, subject to milestones. Those are industrial operating facts and a future expansion. They cannot supply an I-45 highway slot today. [Industrial measures](#source-kodiak-highway); [Atlas expansion](#source-kodiak-atlas).", "The September release targeted an unsupervised Dallas–Houston launch by the end of 2026. October 8 Dallas–Laredo customer work with Charger still had a safety driver. Its 96% Autonomy Readiness Measure concerned materially completed safety-case claims and evidence. Reading that as 96% of a route, or a launch probability, would give the number a meaning the issuer did not assign. [Highway target](#source-kodiak-highway); [Charger operation and metric](#source-kodiak-charger)." ] }, { "id": "regional-and-linehaul", "title": "A store route and a highway load need different trucks", "paragraphs": [ "Gatik’s disclosed DFW networks use 26- and 30-foot trucks between facilities and stores. PepsiCo’s June announcement identifies existing driverless work in Texas, Arizona and Arkansas. Store windows, temperature requirements and the receiving dock belong in that procurement before a long-haul comparison does. [Regional vehicles](#source-gatik-driverless); [PepsiCo agreement](#source-gatik-pepsico).", "Bot Auto’s Houston–Hutchins load supplies a concrete linehaul example. The company’s release reports a commercial shipment without onboard safety staff or dependence on low-latency remote human feedback. Its profitability language is a reason to ask for costs, rather than a substitute for a cost ledger or a current tariff. [Commercial load](#source-bot-commercial).", "For either business, an accepted-load record matters more than a broad company percentage. An operator can improve its on-time rate by accepting only the easiest jobs and leaving the shipper with a harder, more expensive residual schedule. I would send every candidate the same tender and keep the rejected movements in the comparison." ] }, { "id": "supervised-customer-freight", "title": "Customer freight can still have a person onboard", "paragraphs": [ "Waabi and Volvo’s October 5 Warp release describes Dallas–Houston customer operations reaching third-party facilities, with an observer in the driver’s seat. International and Ryder’s Laredo–Temple PlusAI trial reports 92% autonomous route coverage under a human safety driver and inspection below 30 minutes. These are operating shipments with disclosed human roles. I would price the current service before giving it credit for a future labor change. [Warp](#source-waabi-warp); [Ryder pilot](#source-international-ryder).", "PlusAI’s later roadmap targets factory-built commercial launch in 2027. Torc likewise pairs DFW testing and a fleet hub with closed-track driver-out validation and a 2027 market-entry roadmap. Einride’s SH 130 memorandum and Austin demonstration concern a testbed and an R&D project. Each may be useful to a supplier planning ahead; a shipper needs the release and capacity commitment before assigning next week’s freight. [PlusAI roadmap](#source-plus-roadmap); [Torc](#source-torc-roadmap); [Einride testbed](#source-einride-testbed); [Austin demonstration](#source-einride-austin)." ] }, { "id": "route-economics", "title": "The $1,150 quote becomes a $1,310 route", "paragraphs": [ "Here is a first-year scenario for 1,000 one-way Dallas–Houston shipments, each with 250 loaded road miles. The current carrier costs an assumed $1,400 per load, and the shipper performs $100 of warehouse work. That gives a $1,500 economic baseline.", "An invented $1,150 direct-service quote becomes $1,310 after $60 of extra inspection and release work and the same $100 of warehouse labor. A $950 transfer design becomes $1,380 after two $120 local moves, $40 of transfer processing, $50 of extra release work and the common warehouse labor. Each new service also needs $40,000 of first-year setup.", "The apparent cheapness of the linehaul is already less impressive. The service prices include the provider’s equipment, fuel, tolls, maintenance, normal support and repositioning; adding those expenses again would double-count them. The warehouse and release amounts value existing staff work. They are not assumed new payroll." ], "table": { "caption": "Declared price stack per shipment accepted by the selected service", "columns": [ "Cost item", "Current human service", "Direct option", "Transfer option" ], "rows": [ [ "Inclusive carrier service / linehaul", "$1,400", "$1,150", "$950" ], [ "Local drayage beyond included service", "$0", "$0", "$240: two × $120" ], [ "Additional transfer processing", "$0", "$0", "$40" ], [ "Additional shipper inspection/release", "$0", "$60", "$50" ], [ "Loading and receiving labor in every option", "$100", "$100", "$100" ], [ "Comparable variable cost per completed shipment", "$1,500", "$1,310", "$1,380" ], [ "First-year fixed setup, separate from per-load cost", "$0", "$40,000", "$40,000" ] ], "note": "All inputs are hypothetical. Provider service prices include its equipment, fuel, tolls, maintenance, normal roadside/remote support and repositioning; extra recovery costs are modeled separately below. Do not add these items again. Equipment fit and endpoint acceptance are assumed, not proven." } }, { "id": "acceptance-and-exceptions", "title": "The rejected loads stay on the shipper’s bill", "paragraphs": [ "Let the service accept and complete 800 of the 1,000 shipments, including any that need recovery. The other 200 stay with the conventional carrier at $1,500. Direct service costs $1,388,000 including setup before extra exceptions, against $1,500,000 for the old arrangement. Transfers cost $1,444,000.", "Now assume an incremental exception burden, relative to the current arrangement, on 2% of the new-service loads: sixteen events, each with $350 of recovery and $500 of lost contribution. The $13,600 burden leaves $98,400 of first-year saving for direct service and $42,400 for transfers. These are economic savings, combining cash costs, allocated labor and lost contribution on a common basis.", "I would ask the backup carrier to quote the actual 200-load remainder. If those loads have harder windows or less attractive return freight, the old average price may disappear. A cheap accepted subset can leave an expensive transport business behind it." ], "table": { "caption": "Declared first-year direct-service sensitivity for 1,000 total shipments", "columns": [ "Input or result", "Downside", "Base", "Higher acceptance" ], "rows": [ [ "New-service shipments accepted and completed", "400", "800", "1,000" ], [ "Comparable new-service variable cost per shipment", "$1,410", "$1,310", "$1,310" ], [ "Human backup shipments at $1,500", "600", "200", "0" ], [ "Fixed setup cost", "$40,000", "$40,000", "$40,000" ], [ "Incremental exception allowance: accepted loads × 2% × $850", "$6,800", "$13,600", "$17,000" ], [ "Total annual economic cost", "$1,510,800", "$1,401,600", "$1,367,000" ], [ "Saving against $1,500,000 baseline", "−$10,800", "$98,400", "$133,000" ] ], "note": "Each new-service variable cost includes the $100 loading/receiving labor. All numbers are assumptions; the downside adds $100 to the direct price stack and reduces acceptance. Fractional expected exceptions are permitted in the formula, although these examples produce whole event counts. Totals include allocated existing labor and lost contribution; recovery invoices and integration are assumed incremental paid costs." } }, { "id": "decision-thresholds", "title": "The model leaves $123 per load for surprises", "paragraphs": [ "On the direct base inputs, each accepted shipment contributes $173 toward the $40,000 setup cost after its assumed exception burden. Break-even is about 231.2 shipments; 232 is the first whole load above it. At 800 shipments, the $98,400 saving leaves $123 per accepted load for additional costs before the comparison turns negative.", "The corresponding maximum road-service price is $1,273. Start with the old $1,500 economic cost and subtract $50 of setup per accepted load, $17 of expected incremental exceptions and $160 of retained shipper work. The example’s $1,150 road quote sits $123 below that ceiling. At the ceiling, the saving is gone.", "A single additional $100,000 production-interruption loss would erase the base saving and leave a $1,600 loss. I have no estimate that such an event will occur. The sensitivity tells me what the shipper should protect: the receiving window and the ability to move replacement freight when several loads need help together. An annual average can hide a very bad Tuesday." ] }, { "id": "roadside-warning-gate", "title": "The roadside task has a legal cost", "paragraphs": [ "FMCSA’s October 9 exemption, effective October 7, 2026, through October 7, 2031, permits specified cab-mounted beacons in place of conventional roadside warning devices. Aurora is covered; other qualifying Level 4 carriers must give prior written notice. The terms include validated operating domains, cargo restrictions, equipment requirements and beacon activation within five minutes of a qualifying stop. That five-minute clock is not a promise that recovery arrives then. [Federal conditions](#source-beacon-exemption).", "For genuinely intrastate freight, the inspected Texas incorporation and exception rules did not themselves adopt that new relief. Two Texas endpoints do not settle the commerce classification. The buyer needs the applicable legal basis or another compliant arrangement before removing the roadside task from the cost model. [Texas incorporation](#source-texas-carrier-incorporation); [exceptions](#source-texas-carrier-exceptions).", "Insurance has a similar boundary. FMCSA’s liability filing chart does not make the nonhazardous for-hire carrier’s public filing proof of cargo coverage. The May 2026 agency FAQ also warns that legacy Licensing and Insurance records are historical-only for newer Motus filings. I would obtain current evidence for the contracting carrier and the actual protection promised for the goods. [Filing requirements](#source-fmcsa-insurance); [record-system guidance](#source-fmcsa-status)." ] }, { "id": "retailer-tender-example", "title": "The dock decides whether the truck is useful", "paragraphs": [ "A retailer should describe the same replenishment job to every candidate: the goods, truck fit, release time, store window and return movement. Then ask which movements the service accepts, who performs the work at each end and what the quote includes. A driverless truck waiting outside an incompatible dock has removed one person without finishing the delivery.", "I would run a bounded lane trial, retain the original requests and rejected loads, and reconcile each invoice and recovery against accepted receipt. The on-time denominator and the endpoint matter. NHTSA’s raw incident counts, which lack comparable exposure, cannot fill those service-performance cells. [Reporting limits](#source-nhtsa-method).", "The business I want to buy is a reliable route with accountable handoffs and enough cost headroom to survive ordinary trouble. An empty cab is a major engineering accomplishment. The shipper earns its return when the freight gets through." ] } ], "sources": [ { "id": "aurora-faq", "label": "Aurora second-generation driverless launch: operating and purchase model", "href": "https://aurora.tech/newsroom/your-questions-about-our-latest-driverless-launch-answered", "publisher": "Aurora", "date": "2026-07-22", "lastVerified": "2026-10-12", "note": "Issuer explanation: empty driver seat, possible rear-seat roadside-support staff, TaaS ownership and future customer-owned model. Support staff are expressly not driving or supervising driving." }, { "id": "aurora-q2", "label": "Aurora second-quarter 2026 shareholder letter", "href": "https://ir.aurora.tech/sec-filings/all-sec-filings/content/0001828108-26-000075/aurora26q2shareholderlet.htm", "publisher": "Aurora / SEC Form 8-K exhibit", "date": "2026-07-29", "lastVerified": "2026-10-12", "note": "Pages 3–8 distinguish commercial agreements, Midland–Monahans driverless operations, customer endpoints and supervised fueling/weigh-station testing; page 15 revenue includes driverless and operator-supervised loads. Issuer-reported performance is not a comparative safety study." }, { "id": "aurora-october", "label": "Aurora October 2026 commercial update", "href": "https://aurora.tech/newsroom/driving-the-inflection", "publisher": "Aurora", "date": "2026-10-08", "lastVerified": "2026-10-12", "note": "CEO statement reports more than 500,000 cumulative driverless miles since commercial launch. The 2030 fleet vision is forward-looking and is not counted as present capacity." }, { "id": "kodiak-highway", "label": "Kodiak Dallas–Houston driverless launch preparation", "href": "https://kodiak.ai/news/kodiak-names-dallas-houston-driverless-launch-lane", "publisher": "Kodiak AI", "date": "2026-09-25", "lastVerified": "2026-10-12", "note": "Daily preparation deliveries retain a safety observer; driverless validation also occurs on closed courses. Unsupervised highway service remains a year-end 2026 target. June 30 Atlas fleet and paid-hours metrics describe the industrial domain." }, { "id": "kodiak-charger", "label": "Kodiak and Charger Dallas–Laredo customer operation", "href": "https://kodiak.ai/news/kodiak-charger-usa-autonomous-trucking-dallas-laredo", "publisher": "Kodiak AI / Charger USA", "date": "2026-10-08", "lastVerified": "2026-10-12", "note": "First delivery September 8; current operation explicitly has a safety driver behind the wheel. Driverless transition depends on the safety case.96% ARM describes completion of safety-case claims/evidence at September-end, not autonomous mileage." }, { "id": "kodiak-atlas", "label": "Atlas expands its Kodiak-powered Permian delivery system", "href": "https://kodiak.ai/news/atlas-driverless-permian-expansion", "publisher": "Atlas Energy Solutions / Kodiak AI", "date": "2026-07-31", "lastVerified": "2026-10-12", "note": "Second Dune Express load-out point is reported operating; 100-truck mid 2027 timetable and early 2027 public-road operation are forward-looking and conditional. Current industrial operation is not general highway-lane availability." }, { "id": "gatik-driverless", "label": "Gatik January 2026 driverless regional operations disclosure", "href": "https://archive.gatik.ai/news/press-releases/gatik-becomes-first-us-company-to-operate-fully-driverless-trucks-at-scale-for-commercial-deliveries/", "publisher": "Gatik", "date": "2026-01-27", "lastVerified": "2026-10-12", "note": "DFW regional operations, 26-/30-foot trucks, highways and surface streets, and driver/safety-observer absence. Aggregated order, mile and contracted-revenue measures have distinct denominators." }, { "id": "gatik-pepsico", "label": "PepsiCo and Gatik regional freight agreement and existing operations", "href": "https://archive.gatik.ai/news/coverage/pepsico-and-gatik-announce-multi-year-agreement-to-deploy-autonomous-freight-in-north-america/", "publisher": "Gatik / PepsiCo", "date": "2026-06-08", "lastVerified": "2026-10-12", "note": "Issuer page identifies existing driverless PepsiCo operations in Texas, Arizona and Arkansas, regional site-to-site scope and the future agreement. Does not publish an open-market lane tariff." }, { "id": "gatik-august", "label": "Gatik August 2026 financing and operating update", "href": "https://archive.gatik.ai/news/coverage/gatik-raises-200-million-series-d-led-by-qia-and-kdt-as-demand-for-driverless-commercial-freight-accelerates/", "publisher": "Gatik", "date": "2026-08-25", "lastVerified": "2026-10-12", "note": "Reports 85,000 completed driverless orders and 99% on-time across its operations; neither is Texas-specific or matched to another operator’s denominator. More than $600 million is contracted revenue, not recognized cash receipts." }, { "id": "bot-commercial", "label": "Bot Auto reports its first commercial Houston–Hutchins driverless load", "href": "https://www.prnewswire.com/news-releases/houston-we-dont-have-a-problem-bot-auto-delivers-americas-first-fully-humanless-commercial-truckload-302757935.html", "publisher": "Bot Auto TX, Inc. / PR Newswire", "date": "2026-04-30", "lastVerified": "2026-10-12", "note": "Company-issued release, including broker Ryan Transportation statement. Describes 230-mile route, no onboard driver/observer and no low-latency remote human feedback. A dated load and unverified cost claims do not establish current open capacity, profitability or comparative safety." }, { "id": "bot-current", "label": "Bot Auto current operating and freight-contact overview", "href": "https://bot.auto/", "publisher": "Bot Auto", "lastVerified": "2026-10-12", "note": "Current company page describes paid freight and its capacity model. It supplies no public lane tariff or buyer-specific service commitment; it is used only for the present inquiry route." }, { "id": "waabi-warp", "label": "Volvo and Waabi begin Warp customer operations in Texas", "href": "https://www.waabi.ai/insights/volvo-and-waabi-kick-off-customer-operations-in-texas-starting-with-warp", "publisher": "Waabi / Volvo Autonomous Solutions", "date": "2026-10-05", "lastVerified": "2026-10-12", "note": "Direct third-party-facility freight on Dallas–Houston; release explicitly says current hauls have an observer in the driver’s seat. LTL-network participation is separate from full driver-out operation." }, { "id": "international-ryder", "label": "International and Ryder live-freight PlusAI trial", "href": "https://news.international.com/2026-03-31-International-Launches-Level-4-Autonomous-Fleet-Trial-on-Live-Freight-Lane", "publisher": "International Motors / Ryder", "date": "2026-03-31", "lastVerified": "2026-10-12", "note": "Laredo–Temple daily 600-mile route with factory-integrated SuperDrive.92% autonomous route coverage is explicitly supervised by a human safety driver; sub 30-minute inspection is a pilot KPI, not an industry standard." }, { "id": "torc-2026", "label": "Torc February 2026 public-road testing update", "href": "https://torc.ai/michigan-public-roads-autonomous-truck-testing/", "publisher": "Torc Robotics", "date": "2026-02-24", "lastVerified": "2026-10-12", "note": "Current-year disclosure identifies established DFW testing and fleet operations; technology development is not asserted to be driver-out customer availability." }, { "id": "torc-roadmap", "label": "Torc production platform, Fort Worth operations and 2027 roadmap", "href": "https://torc.ai/av-3-0-scaling-physical-ai-autonomous-trucking-embedded-hardware/", "publisher": "Torc Robotics", "date": "2025-11-17", "lastVerified": "2026-10-12", "note": "Dated company account separates October 2024 closed-track driverless acceptance testing, May 2025 hub opening, I-35 focus and planned 2027 market entry. Historical product milestones are not retroactively described as a commercial launch." }, { "id": "einride-testbed", "label": "Einride and SH 130 infrastructure testbed memorandum", "href": "https://www.prnewswire.com/news-releases/einride-partners-with-texas-highway-operator-to-create-autonomous-freight-testbed-302715954.html", "publisher": "Einride / PR Newswire", "date": "2026-03-17", "lastVerified": "2026-10-12", "note": "Company-issued MoU announcement concerns validation on SH 130 Segments 5/6 and frontage-road integration. A testbed partnership does not establish a customer freight lane." }, { "id": "einride-austin", "label": "Einride reports Austin approval and research demonstration", "href": "https://news.cision.com/einride/r/einride-secures-fifth-nhtsa-approval-to-operate-autonomous-vehicles-on-u-s--roads,c4341234", "publisher": "Einride / Cision", "date": "2026-03-24", "lastVerified": "2026-10-12", "note": "Issuer reports NHTSA approval and March 19 cabless demonstration, explicitly part of an R&D project. The underlying approval instrument and general Texas commercial eligibility are not independently established by this release." }, { "id": "dps-plans", "label": "Texas DPS public first-responder interaction plans", "href": "https://www.dps.texas.gov/section/cav/connected-autonomous-vehicles", "publisher": "Texas Department of Public Safety", "date": "2026-02-27", "lastVerified": "2026-10-12", "note": "Page date is the displayed date; list read October 12. Published plans are responder documents, not permits, current route availability or a complete operator census." }, { "id": "nhtsa-method", "label": "NHTSA Standing General Order crash-data limitations", "href": "https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting", "publisher": "NHTSA", "lastVerified": "2026-10-12", "note": "Current official methodology: incomplete/unverified initial reports, possible duplicates, unequal reporting visibility, no normalization for miles/fleet/domain and different ADS/Level 2 reporting thresholds. No operator crash ranking is derived." }, { "id": "plus-roadmap", "label": "PlusAI September 2026 Texas operations and commercialization roadmap", "href": "https://www.plus.ai/news-and-insights/2026-09-03-texas-ventures-business-combination", "publisher": "PlusAI", "date": "2026-09-03", "lastVerified": "2026-10-12", "note": "Current issuer announcement separates Texas Ryder/International fleet trials from targeted 2027 commercial launch of factory-built SuperDrive trucks. No funding transaction completion, forecast revenue or open driverless service is inferred." }, { "id": "beacon-exemption", "label": "FMCSA final warning-beacon exemption and operating conditions", "href": "https://www.govinfo.gov/content/pkg/FR-2026-10-09/html/2026-20734.htm", "publisher": "FMCSA / Federal Register", "date": "2026-10-09; effective 2026-10-07–2031-10-07", "lastVerified": "2026-10-13", "note": "91 FR 64736–64741, VI.B–C: prior notice for other carriers, validated domain, excluded cargo/passenger work, equipment and activation conditions. This replaces specified warning-device requirements; it is not a general driverless approval or recovery-time guarantee." }, { "id": "texas-carrier-incorporation", "label": "37 TAC §4.11: current commercial-vehicle incorporation rule", "href": "https://texas-sos.appianportalsgov.com/rules-and-meetings?recordId=211918&queryAsDate=10%2F13%2F2026&interface=VIEW_TAC_SUMMARY&$locale=en_US", "publisher": "Texas Secretary of State / Texas Department of Public Safety", "date": "2023-01-08", "lastVerified": "2026-10-13", "note": "Official current rendered text: §4.11(a) incorporates federal amendments/interpretations through September 1, 2022; (b)(6) substitutes the DPS director for intrastate vehicles. That text does not automatically adopt a later federal exemption." }, { "id": "texas-carrier-exceptions", "label": "37 TAC §4.12: current Texas exemptions and exceptions", "href": "https://texas-sos.appianportalsgov.com/rules-and-meetings?recordId=226974&queryAsDate=10%2F13%2F2026&interface=VIEW_TAC_SUMMARY&$locale=en_US", "publisher": "Texas Secretary of State / Texas Department of Public Safety", "date": "2025-12-11", "lastVerified": "2026-10-13", "note": "Complete current exception list inspected, latest amendment effective December 11, 2025. The inspected rule contains no beacon relief or blanket prospective adoption of federal exemptions; this bounded reading does not rule out every other legal instrument." }, { "id": "aurora-weather", "label": "Aurora fourth-quarter 2025 letter: operating-domain expansion", "href": "https://ir.aurora.tech/sec-filings/all-sec-filings/content/0001828108-26-000014/finalaurora25q4sharehold.htm", "publisher": "Aurora / SEC Form 8-K exhibit", "date": "2026-02-11", "lastVerified": "2026-10-12", "note": "Page 3 reports software validation for rain, fog and heavy wind. The historical 2025 weather-constraint observation is not used to estimate current availability or model another operator." }, { "id": "fmcsa-insurance", "label": "FMCSA operating-authority insurance filing requirements", "href": "https://www.fmcsa.dot.gov/registration/insurance-filing-requirements", "publisher": "FMCSA", "date": "2026-03-26", "lastVerified": "2026-10-12", "note": "Agency chart separates bodily injury/property damage from cargo. Nonhazardous for-hire property row has $0 cargo filing requirement; this does not establish contractual cargo protection. No operator-specific policy or authority is verified here." }, { "id": "fmcsa-status", "label": "FMCSA registration-status FAQs and legacy-record warning", "href": "https://www.fmcsa.dot.gov/registration/ask-fmcsa?topic=23021", "publisher": "FMCSA", "date": "2026-05-21", "lastVerified": "2026-10-12", "note": "May 21, 2026 FAQ says L&I is historical-only as ofMay 14 and does not reflect Motus filings. Adjacent May 2023 FAQs still reference L&I. Verify record-system coverage and obtain current authoritative evidence before relying on a particular carrier record." } ], "claims": [ { "id": "trucking-aurora-platform", "claim": "Aurora reports July 22 second-generation driverless International LT operation with no person behind the wheel; rear-seat roadside-support staff may ride on some trips.", "status": "issuer-reported current operation", "qualification": "Support staff are expressly not driving or supervising driving. No empty-cab assertion for every truck or trip.", "sources": [ { "url": "https://aurora.tech/newsroom/your-questions-about-our-latest-driverless-launch-answered", "date": "2026-07-22", "pinpoint": "Is anyone in the truck?; What did we announce?" } ], "recheck": "Platform/onboard-role update" }, { "id": "trucking-aurora-endpoints", "claim": "Aurora reports deployed driverless Midland–Monahans operations; fueling and weigh-station work are separately supervised testing.", "status": "issuer-reported operation and testing", "qualification": "Specific endpoint/trailer configuration does not establish universal customer access.", "sources": [ { "url": "https://ir.aurora.tech/sec-filings/all-sec-filings/content/0001828108-26-000075/aurora26q2shareholderlet.htm", "date": "2026-07-29", "pinpoint": "Pages 7–8" } ], "recheck": "Released endpoint, fueling or weigh-station capability change" }, { "id": "trucking-aurora-miles", "claim": "Aurora reports more than 500,000 driverless miles since commercial launch in its October 8 update.", "status": "issuer-reported cumulative measure", "qualification": "Not independent comparative safety evidence, present fleet count or available shipper slots.2030 fleet vision remains a forecast.", "sources": [ { "url": "https://aurora.tech/newsroom/driving-the-inflection", "date": "2026-10-08", "pinpoint": "Opening commercial-operation paragraph" } ], "recheck": "Next dated operating disclosure" }, { "id": "trucking-kodiak-industry", "claim": "Kodiak reports 35 Atlas-owned driverless trucks and more than 40,000 paid driverless hours at June 30; Atlas reports second Dune Express load-out operation.", "status": "issuer-reported industrial operation", "qualification": "The industrial program has a separate operating domain; Atlas public-road expansion is targeted early 2027 subject to milestones. Fleet 100 by mid 2027 is a plan.", "sources": [ { "url": "https://kodiak.ai/news/kodiak-names-dallas-houston-driverless-launch-lane", "date": "2026-09-25", "pinpoint": "Permian foundation section; Atlas expansion opening" }, { "url": "https://kodiak.ai/news/atlas-driverless-permian-expansion", "date": "2026-07-31", "pinpoint": "Permian foundation section; Atlas expansion opening" } ], "recheck": "New fleet/reporting cutoff or dated public-road expansion" }, { "id": "trucking-kodiak-highway", "claim": "September 25 Dallas–Houston release describes observer-supported preparation deliveries and closed-course driverless testing; highway driver-out launch remains targeted end 2026.", "status": "preparation and forward-looking target", "qualification": "Intervention-free supervised/observer-supported delivery does not demonstrate removal of the observer.", "sources": [ { "url": "https://kodiak.ai/news/kodiak-names-dallas-houston-driverless-launch-lane", "date": "2026-09-25", "pinpoint": "Launch program; Preparing for launch at the test track" } ], "recheck": "Dated driver-out public-road customer launch" }, { "id": "trucking-kodiak-charger", "claim": "October 8 Charger Dallas–Laredo customer operation has a safety driver; 96% ARM at September-end measures materially completed safety-case claims/evidence.", "status": "issuer-reported current supervised service", "qualification": "96% is not autonomous distance, successful delivery share, route availability or launch probability.", "sources": [ { "url": "https://kodiak.ai/news/kodiak-charger-usa-autonomous-trucking-dallas-laredo", "date": "2026-10-08", "pinpoint": "Current safety-driver paragraph; ARM definition" } ], "recheck": "Onboard-role change and safety-case completion" }, { "id": "trucking-gatik-regional", "claim": "Gatik reports DFW driverless regional 26-/30-foot truck operations; June 8 statement identifies existing Texas PepsiCo driverless work.", "status": "issuer-reported regional service", "qualification": "Regional retail configuration is not interchangeable with every Class 8 linehaul job. No buyer-specific availability inferred.", "sources": [ { "url": "https://archive.gatik.ai/news/press-releases/gatik-becomes-first-us-company-to-operate-fully-driverless-trucks-at-scale-for-commercial-deliveries/", "date": "2026-01-27", "pinpoint": "January regional/vehicle paragraphs; June existing operations" }, { "url": "https://archive.gatik.ai/news/coverage/pepsico-and-gatik-announce-multi-year-agreement-to-deploy-autonomous-freight-in-north-america/", "date": "2026-06-08", "pinpoint": "January regional/vehicle paragraphs; June existing operations" } ], "recheck": "Accepted endpoint/equipment or current customer operation update" }, { "id": "trucking-gatik-latest", "claim": "August 25 Gatik update reports 85,000 driverless orders and 99% on-time delivery across operations.", "status": "issuer-reported aggregated performance", "qualification": "Not Texas-only or normalized to another operator; contracted revenue does not establish recognized revenue or cash receipts.", "sources": [ { "url": "https://archive.gatik.ai/news/coverage/gatik-raises-200-million-series-d-led-by-qia-and-kdt-as-demand-for-driverless-commercial-freight-accelerates/", "date": "2026-08-25", "pinpoint": "Opening operating-metrics paragraph" } ], "recheck": "Next performance disclosure with period/denominator" }, { "id": "trucking-bot-commercial", "claim": "Bot Auto reports a paid 230-mile Houston–Hutchins load without onboard driver/observer or low-latency remote human feedback.", "status": "issuer-reported dated commercial delivery", "qualification": "Company-issued April 30 PRNewswire record; no independently verified cost/profitability or unlimited recurring capacity claim.", "sources": [ { "url": "https://www.prnewswire.com/news-releases/houston-we-dont-have-a-problem-bot-auto-delivers-americas-first-fully-humanless-commercial-truckload-302757935.html", "date": "2026-04-30", "pinpoint": "Opening route paragraphs and Ryan Transportation statement" } ], "recheck": "Current lane acceptance/capacity and service evidence" }, { "id": "trucking-waabi-warp", "claim": "October 5 Waabi/Volvo release reports direct third-party facility freight in Warp’s Dallas–Houston network with an observer in the driver’s seat.", "status": "issuer-reported customer service with onboard role", "qualification": "Does not establish driver-out operation or observer intervention frequency.", "sources": [ { "url": "https://www.waabi.ai/insights/volvo-and-waabi-kick-off-customer-operations-in-texas-starting-with-warp", "date": "2026-10-05", "pinpoint": "Current-operation paragraphs" } ], "recheck": "Explicit onboard-role transition" }, { "id": "trucking-plus-ryder", "claim": "International/Ryder report daily 600-mile Laredo–Temple live-freight pilot with 92% autonomous route coverage supervised by human safety driver and inspection below 30 minutes.", "status": "issuer-reported supervised pilot", "qualification": "Coverage is not driverless availability; inspection is a pilot KPI, not universal allowance or legal standard.", "sources": [ { "url": "https://news.international.com/2026-03-31-International-Launches-Level-4-Autonomous-Fleet-Trial-on-Live-Freight-Lane", "date": "2026-03-31", "pinpoint": "Early findings and KPIs; pilot description" } ], "recheck": "Driver-out release or changed pilot configuration" }, { "id": "trucking-torc", "claim": "Torc 2026 release describes established DFW testing; 2025 platform account separates closed-track driver-out test, Fort Worth hub and 2027 market entry.", "status": "testing with forward-looking commercialization", "qualification": "Production intent and controlled driver-out acceptance are not current unsupervised customer availability.", "sources": [ { "url": "https://torc.ai/michigan-public-roads-autonomous-truck-testing/", "date": "2026-02-24", "pinpoint": "Testing opening; October 2024/May 2025 and Onward to 2027" }, { "url": "https://torc.ai/av-3-0-scaling-physical-ai-autonomous-trucking-embedded-hardware/", "date": "2025-11-17", "pinpoint": "Testing opening; October 2024/May 2025 and Onward to 2027" } ], "recheck": "Dated public-road driver-out and customer-service release" }, { "id": "trucking-einride", "claim": "Einride reports SH 130 validation-testbed MoU and Austin research demonstration with company-reported NHTSA approval.", "status": "research/validation and issuer approval statement", "qualification": "Underlying instrument not independently verified; no bookable commercial Texas lane inferred.", "sources": [ { "url": "https://www.prnewswire.com/news-releases/einride-partners-with-texas-highway-operator-to-create-autonomous-freight-testbed-302715954.html", "date": "2026-03-17", "pinpoint": "March 17 testbed scope; March 24 R&D qualification" }, { "url": "https://news.cision.com/einride/r/einride-secures-fifth-nhtsa-approval-to-operate-autonomous-vehicles-on-u-s--roads,c4341234", "date": "2026-03-24", "pinpoint": "March 17 testbed scope; March 24 R&D qualification" } ], "recheck": "Specified customer freight deployment and approval scope" }, { "id": "trucking-dps", "claim": "DPS posts first-responder plans for named operators including Stack, Fountainhead Logistics and International Transport Engineering.", "status": "official document directory", "qualification": "Plan posting is not authorization, available service or exhaustive census. Displayed page date differs from individual plan versions.", "sources": [ { "url": "https://www.dps.texas.gov/section/cav/connected-autonomous-vehicles", "date": "2026-02-27", "pinpoint": "First Responder Interaction Plans list" } ], "recheck": "Directory/plan changes and independently supported service development" }, { "id": "trucking-safety-comparison", "claim": "NHTSA crash totals are not normalized by fleet, miles or operating domain and may include incomplete information or duplicates.", "status": "official methodological limitation", "qualification": "No operator safety ranking or collision probability derived from totals.", "sources": [ { "url": "https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting", "date": null, "pinpoint": "Data and Limitations; Summary Incident Report Data Are Not Normalized" } ], "recheck": "Method/reporting criteria change" }, { "id": "trucking-plus-roadmap", "claim": "PlusAI September 3 release identifies ongoing Texas Ryder/International autonomous fleet trials and targets factory-built commercial launch in 2027.", "status": "issuer-reported trial and forward-looking launch target", "qualification": "The target does not establish current driver-out service; no funding, projected revenue or capacity treated as completed.", "sources": [ { "url": "https://www.plus.ai/news-and-insights/2026-09-03-texas-ventures-business-combination", "date": "2026-09-03", "pinpoint": "Opening bullets and commercial-momentum paragraphs" } ], "recheck": "Dated driver-out customer operation and completed commercial release" }, { "id": "trucking-warning-exemption", "claim": "FMCSA grants a limited cab-mounted warning-beacon exemption effective October 7, 2026–October 7, 2031; other Level 4 carriers must give prior written notice.", "status": "official final exemption", "qualification": "Specific warning-device alternative only. Other federal rules continue; no competitor participation or fleet compliance verified. Intrastate treatment must be resolved separately from federal interstate preemption.", "sources": [ { "url": "https://www.govinfo.gov/content/pkg/FR-2026-10-09/html/2026-20734.htm", "date": "2026-10-09", "pinpoint": "DATES; VI.A–C.1–5; VI.D" } ], "recheck": "Current exemption, participating carrier evidence, cargo, configuration, domain or state intrastate treatment changes." }, { "id": "texas-intrastate-beacon-basis", "claim": "Official current §4.11 incorporates federal amendments through September 1, 2022; the complete inspected §4.12 exception list does not adopt the October 2026 beacon relief. Federal permission alone does not establish a Texas intrastate legal basis.", "status": "current official rendered rule text checked 2026-10-13; bounded interpretation", "qualification": "No exhaustive absence finding about other DPS instruments, no individual state permit process inferred, and no real shipment classification determined. Two Texas endpoints alone do not establish intrastate commerce.", "sources": [ { "url": "https://texas-sos.appianportalsgov.com/rules-and-meetings?recordId=211918&queryAsDate=10%2F13%2F2026&interface=VIEW_TAC_SUMMARY&$locale=en_US", "date": "2023-01-08", "pinpoint": "37 TAC §4.11(a), (b)(3), (b)(6), (c)" }, { "url": "https://texas-sos.appianportalsgov.com/rules-and-meetings?recordId=226974&queryAsDate=10%2F13%2F2026&interface=VIEW_TAC_SUMMARY&$locale=en_US", "date": "2025-12-11", "pinpoint": "37 TAC §4.12 entire exception list and source note" } ], "recheck": "Current Texas rule amendment, actual applicable relief instrument/interpretation, changed shipment classification or proposed warning-device arrangement." }, { "id": "retailer-tender-example", "claim": "Suggested illustrative buyer workflow: Run one replenishment job through the shortlist. No private provider contract, actual site design, service entitlement or observed performance inferred.", "status": "editorial recommendation and illustrative workflow", "qualification": "Suggested purchaser analysis; all original source dates, access restrictions, legal conditions and unresolved provider-specific facts remain in the article.", "sources": [], "recheck": "Change to the proposed itinerary, route, contract, fleet stage, accepted volume or stated model input." } ], "absorbedEvidence": [ { "articleSlug": "texas-driverless-freight-route-economics", "sourceCutoff": "2026-10-13", "evidenceRole": "Historical supporting claim ledger from an absorbed article; claims retain their original dates, qualifications and scope.", "claims": [ { "id": "freight-endpoints", "claim": "Reviewed Texas programs can serve customer endpoints, but supported facilities, platforms and onboard roles differ.", "status": "issuer-reported selected capabilities", "qualification": "Aurora specific driverless endpoint work; Waabi observer-supported direct facility work; no universal two-terminal requirement or unrestricted yard acceptance.", "sources": [ { "url": "https://ir.aurora.tech/sec-filings/all-sec-filings/content/0001828108-26-000075/aurora26q2shareholderlet.htm", "date": "2026-07-29", "pinpoint": "Aurora pages 7–8; Warp current-operation paragraphs; Ryder pilot" }, { "url": "https://www.waabi.ai/insights/volvo-and-waabi-kick-off-customer-operations-in-texas-starting-with-warp", "date": "2026-10-05", "pinpoint": "Aurora pages 7–8; Warp current-operation paragraphs; Ryder pilot" }, { "url": "https://news.international.com/2026-03-31-International-Launches-Level-4-Autonomous-Fleet-Trial-on-Live-Freight-Lane", "date": "2026-03-31", "pinpoint": "Aurora pages 7–8; Warp current-operation paragraphs; Ryder pilot" } ], "recheck": "Endpoint, platform or operating-role change" }, { "id": "freight-ownership", "claim": "Aurora July model owns/operates trucks under TaaS; Kodiak October describes customer-owned/operated DaaS trucks.", "status": "issuer-reported business models", "qualification": "Labels do not establish full cost inclusions, availability or a completed driver-out transition.", "sources": [ { "url": "https://aurora.tech/newsroom/your-questions-about-our-latest-driverless-launch-answered", "date": "2026-07-22", "pinpoint": "How can I get one?; DaaS paragraph" }, { "url": "https://kodiak.ai/news/kodiak-charger-usa-autonomous-trucking-dallas-laredo", "date": "2026-10-08", "pinpoint": "How can I get one?; DaaS paragraph" } ], "recheck": "Commercial model and responsibility schedule" }, { "id": "freight-inspection", "claim": "International/Ryder supervised pilot reports pre-trip inspection below 30 minutes.", "status": "issuer-reported pilot KPI", "qualification": "Not guaranteed for another configuration and not an industry or legal standard.", "sources": [ { "url": "https://news.international.com/2026-03-31-International-Launches-Level-4-Autonomous-Fleet-Trial-on-Live-Freight-Lane", "date": "2026-03-31", "pinpoint": "Early findings and KPIs" } ], "recheck": "Truck/trailer/inspection process change" }, { "id": "freight-weather", "claim": "Aurora February 2026 letter reports expanded validation for rain, fog and heavy wind.", "status": "issuer-reported domain expansion", "qualification": "Does not establish unrestricted all-weather service; historical 2025 constraints not extrapolated to current availability.", "sources": [ { "url": "https://ir.aurora.tech/sec-filings/all-sec-filings/content/0001828108-26-000014/finalaurora25q4sharehold.htm", "date": "2026-02-11", "pinpoint": "Page 3" } ], "recheck": "Released operating thresholds and dispatch process" }, { "id": "freight-cargo-insurance", "claim": "FMCSA chart distinguishes liability filings from cargo; nonhazardous for-hire property has $0 cargo filing requirement.", "status": "official filing scope", "qualification": "Actual cargo protection needs relevant policy/contract; no operator insurance adequacy assessed.", "sources": [ { "url": "https://www.fmcsa.dot.gov/registration/insurance-filing-requirements", "date": "2026-03-26", "pinpoint": "Insurance Filing Requirements Chart" } ], "recheck": "Agency chart/legal change and actual policy/contract" }, { "id": "freight-authority-records", "claim": "May 21, 2026 FMCSA FAQ says legacy L&I historical-only from May 14 and excludes Motus filings, beside older FAQs that still point there.", "status": "official current-record coverage warning", "qualification": "Resolve source coverage rather than rely on old generic lookup instructions; no carrier authorization verified.", "sources": [ { "url": "https://www.fmcsa.dot.gov/registration/ask-fmcsa?topic=23021", "date": "2026-05-21", "pinpoint": "What can I do in L&I?; adjacent May 2023 lookup FAQ" } ], "recheck": "Registration system coverage/current authority evidence" }, { "id": "freight-performance-comparison", "claim": "NHTSA raw crash counts cannot establish comparative operator risk without exposure and compatible data.", "status": "official methodological limitation", "qualification": "Accepted-load performance also requires matching definitions/periods; no provider safety or savings ranking.", "sources": [ { "url": "https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting", "date": null, "pinpoint": "Data and Limitations" } ], "recheck": "Method or material service-data change" }, { "id": "freight-warning-exemption", "claim": "FMCSA grants a limited cab-mounted warning-beacon exemption effective October 7, 2026–October 7, 2031; other Level 4 carriers must give prior written notice.", "status": "official final exemption", "qualification": "Specific warning-device alternative only. Other federal rules continue; no competitor participation or fleet compliance verified. Intrastate treatment must be resolved separately from federal interstate preemption.", "sources": [ { "url": "https://www.govinfo.gov/content/pkg/FR-2026-10-09/html/2026-20734.htm", "date": "2026-10-09", "pinpoint": "DATES; VI.A–C.1–5; VI.D" } ], "recheck": "Current exemption, participating carrier evidence, cargo, configuration, domain or state intrastate treatment changes." }, { "id": "texas-intrastate-beacon-basis", "claim": "Official current §4.11 incorporates federal amendments through September 1, 2022; the complete inspected §4.12 exception list does not adopt the October 2026 beacon relief. Federal permission alone does not establish a Texas intrastate legal basis.", "status": "current official rendered rule text checked 2026-10-13; bounded interpretation", "qualification": "No exhaustive absence finding about other DPS instruments, no individual state permit process inferred, and no real shipment classification determined. Two Texas endpoints alone do not establish intrastate commerce.", "sources": [ { "url": "https://texas-sos.appianportalsgov.com/rules-and-meetings?recordId=211918&queryAsDate=10%2F13%2F2026&interface=VIEW_TAC_SUMMARY&$locale=en_US", "date": "2023-01-08", "pinpoint": "37 TAC §4.11(a), (b)(3), (b)(6), (c)" }, { "url": "https://texas-sos.appianportalsgov.com/rules-and-meetings?recordId=226974&queryAsDate=10%2F13%2F2026&interface=VIEW_TAC_SUMMARY&$locale=en_US", "date": "2025-12-11", "pinpoint": "37 TAC §4.12 entire exception list and source note" } ], "recheck": "Current Texas rule amendment, actual applicable relief instrument/interpretation, changed shipment classification or proposed warning-device arrangement." }, { "id": "road-quote-ceiling", "claim": "At 800 accepted loads, the declared $1,433 whole-route variable-cost ceiling less $100 common warehouse and $60 added release work gives a $1,273 maximum provider road quote; $1,150 base quote leaves $123 headroom. Setup and incremental expected exceptions were already deducted in deriving the ceiling.", "status": "calculated hypothetical using existing inputs", "qualification": "Suggested purchaser analysis; all original source dates, access restrictions, legal conditions and unresolved provider-specific facts remain in the article.", "sources": [], "recheck": "Change to the proposed itinerary, route, contract, fleet stage, accepted volume or stated model input." } ] } ], "updateTriggers": [ "A driver-out launch, onboard role or accepted endpoint changes", "Operator disclosures revise the program stage or metric definitions", "Current buyer-specific capacity or recovery evidence changes", "Roadside-warning exemption, carrier participation, cargo/configuration or intrastate treatment changes", "Quoted inclusions, price, acceptance or support arrangements change", "Actual trial completion, exception and interruption evidence changes", "Carrier records or insurance evidence change" ] } ] }