<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Tesla on Liam Ding</title>
    <link>https://www.liamding.com/en/tags/tesla/</link>
    <description>Recent content in Tesla on Liam Ding</description>
    <image>
      <title>Liam Ding</title>
      <url>https://www.liamding.com/img/og-cover.png</url>
      <link>https://www.liamding.com/img/og-cover.png</link>
    </image>
    <generator>Hugo -- 0.147.7</generator>
    <language>en</language>
    <lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0800</lastBuildDate>
    <atom:link href="https://www.liamding.com/en/tags/tesla/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tesla&#39;s Q2 2027 &#39;unsupervised FSD&#39; is a fleet product, not a car feature</title>
      <link>https://www.liamding.com/en/posts/2026-10-26-tesla-unsupervised-fsd-is-a-fleet-product/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0800</pubDate>
      <guid>https://www.liamding.com/en/posts/2026-10-26-tesla-unsupervised-fsd-is-a-fleet-product/</guid>
      <description>Reading Tesla&amp;#39;s Q3 2026 call as a product spec: owner cars join Tesla&amp;#39;s geofenced, Tesla-run Robotaxi fleet around Q2 2027. The unit of acceptance moved from the car to the fleet-plus-zone, and that changes what to measure.</description>
      <content:encoded><![CDATA[<h2 id="the-problem">The problem</h2>
<p>On Tesla&rsquo;s Q3 2026 earnings call on 21 October, one of the top retail shareholder questions, backed by about 1.1 million shares according to Electrek, was simple: when does unsupervised FSD arrive in customer cars? Ashok Elluswamy answered with a date, around Q2 2027, and a definition. In his words, as quoted by The Verge, the software for Cybercab and Model Y &ldquo;is the same&rdquo;, it will ship to customers as part of the V15 release, and &ldquo;the only additional requirement is to make sure that, for example, the customer Model Y can be part of the geofences and the fleet management that Tesla has for it to be fully autonomous.&rdquo;</p>
<p>My conclusion up front: Tesla has quietly changed the unit of acceptance. &ldquo;Unsupervised FSD&rdquo; used to be described as a property of a car, meaning your car drives itself wherever you take it. As described on this call, it is a property of a fleet operating inside a zone, with your car allowed to join. That is a sounder spec than the old promise. It is also a different product from the one owners were sold, and it should be judged on fleet-and-zone evidence, not on the software version number.</p>
<h2 id="what-i-concluded">What I concluded</h2>
<p>First, &ldquo;same software&rdquo; does not mean &ldquo;same product&rdquo;. The sentence that matters is the one about geofences and fleet management. A robotaxi&rsquo;s operational design domain (ODD) is not defined by the network weights alone. It is defined by the mapped and validated zone, the remote assistance and recovery behind it, the maintenance and cleaning cadence, and the operator who carries the liability. Saying the owner&rsquo;s car must sit inside Tesla&rsquo;s geofence and fleet management is a statement that the safety case lives there, not in the car.</p>
<p>Second, this is the right call as engineering, and it is narrower than the marketing. A personal car that drives itself anywhere has an ODD equal to wherever the owner goes. That is very hard to validate, insure or permit, which is why Tesla&rsquo;s own Robotaxi service runs inside bounded zones. Electrek describes Tesla&rsquo;s current Robotaxi service as six US metros, mostly small slices of each city, largely off highways, and still with a safety driver in the Bay Area. By framing the Q2 2027 step as owner cars working inside those zones, Tesla is choosing the only version that can actually be accepted. The cost is that it is not what Electrek says Musk has sold to customers since 2016, a car that drives you anywhere while you sleep. Electrek also quotes Musk telling investors in July 2025 that unsupervised FSD would be available &ldquo;for unsupervised personal use by the end of this year in certain geographies.&rdquo;</p>
<p>Third, the business is already pointing this way. CNBC quotes Musk saying &ldquo;the vast majority of the Cybercab stuff will be essentially Tesla-owned and transport-as-a-service.&rdquo; Tesla&rsquo;s own Q3 outlook says deliveries will depend partly on &ldquo;allocation decisions between sale to customers and use for our owned and operated fleet.&rdquo; Read together, the owner-car step looks like a capacity valve for a fleet Tesla runs, not a consumer feature released to owners.</p>
<h2 id="constraints">Constraints</h2>
<p>The binding constraint is fleet heterogeneity. A Tesla-owned fleet in a zone is one configuration with one maintenance regime. Owner cars arrive with different hardware generations, different sensor-cleaning histories, tyre and brake wear Tesla did not schedule, and owners who may need the car back at short notice. Electrek notes that HW3 owners have already been told their computers cannot run unsupervised FSD. Admitting owner cars means the safety case has to include an admission test per vehicle, and that test is a product in its own right.</p>
<p>The second constraint is the denominator. Tesla&rsquo;s Q3 update says the Robotaxi service reached &ldquo;nearly two million cumulative unsupervised miles&rdquo; as of the end of the quarter, 30 September. Tesla&rsquo;s Robotaxi safety page states 3.1 million miles driven autonomously as of 18 October 2026, for 22 January through 18 October, with no safety monitor in the vehicle. From 30 September to 18 October is 18 days. Subtracting the filing&rsquo;s nearly 2 million from that 3.1 million leaves about 1.1 million miles, and neither document explains the jump. That unexplained increment has to be closed before strangers&rsquo; cars join the fleet.</p>
<p>The third constraint is regulatory and legal, and it is per jurisdiction. The Verge points out that driverless ride-hailing needs specific local and state permits, that insurance may be hard to obtain, and that in most places it is still not legal for individuals to run their own self-driving cars as driverless taxis. In California, Electrek reports that state rules still require a safety driver in every Tesla Robotaxi. A Q2 2027 date for owner cars is therefore a date for specific zones in specific states, whatever the software is ready to do.</p>
<p>The demand side is real, and that is what makes the reframing sensitive. Tesla reports FSD (Supervised) attach above 75% of new North American deliveries, up nearly twenty percentage points from the previous quarter, and 1.74 million active subscriptions, up from 1.48 million in Q2. CNBC puts the US price at $99 a month. Most of those buyers live and drive outside any Robotaxi zone.</p>
<h2 id="the-options-and-what-i-traded-away">The options, and what I traded away</h2>
<p>My reconstruction of the choice set, not a description of anyone&rsquo;s internal reasoning.</p>
<table>
  <thead>
      <tr>
          <th>Option</th>
          <th>What it buys</th>
          <th>What it costs</th>
          <th>Why I did / did not pick it</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Ship unsupervised FSD to owner cars everywhere</td>
          <td>Delivers the original promise; one software event</td>
          <td>An unbounded ODD nobody can validate, insure or get permitted</td>
          <td>I would not</td>
      </tr>
      <tr>
          <td>Owner cars join the Tesla fleet inside Tesla&rsquo;s zones (what was described)</td>
          <td>A bounded ODD, one operator, a safety case that can be written</td>
          <td>A much narrower product than owners expected; admission testing for mixed hardware</td>
          <td>I would pick it, if the admission criteria ship with the date</td>
      </tr>
      <tr>
          <td>Tesla-owned fleet only, no owner cars</td>
          <td>A uniform fleet, simplest safety case</td>
          <td>Capital-heavy; leaves the long-standing owner promise unanswered</td>
          <td>A defensible choice, but it gives up the capacity valve</td>
      </tr>
      <tr>
          <td>Owner-only supervised FSD, more markets</td>
          <td>Keeps the subscription business growing (nine EU countries so far)</td>
          <td>Says nothing about unsupervised operation</td>
          <td>Worth doing in parallel; it is not an answer to the question asked</td>
      </tr>
      <tr>
          <td>Reconcile the safety-page miles with the filing&rsquo;s definition, and publish an incident rate per zone</td>
          <td>One definition of miles, plus a rate per zone, that regulators, insurers and owners can compare</td>
          <td>Makes the 18-day jump, and any high-incident zone, visible</td>
          <td>I would do this before admitting the first owner car</td>
      </tr>
  </tbody>
</table>
<h2 id="evidence">Evidence</h2>
<p>The strongest evidence is the wording. The VP answering the shareholder question defined the deliverable as joining Tesla&rsquo;s geofences and fleet management, not as a feature unlock. Tesla&rsquo;s filed update supports the fleet reading: Cybercab rides began on 3 September in Austin, Austin hours are now 6am to midnight, cumulative unsupervised Robotaxi miles grew eightfold quarter on quarter, and the outlook explicitly weighs selling cars against keeping them for Tesla&rsquo;s own fleet. CNBC reports Texas DMV counts of 362 Model Y Robotaxi vehicles and 449 Cybercabs authorised for driverless operation. The mileage gap is the finding. The filing&rsquo;s nearly two million cumulative unsupervised miles are as of 30 September; the safety page&rsquo;s 3.1 million miles with no safety monitor are as of 18 October. About 1.1 million miles in 18 days is left unexplained.</p>
<h2 id="where-this-stops-being-true">Where this stops being true</h2>
<p>Segment: this is about unsupervised operation. For supervised FSD the car is still the right unit of acceptance, because the driver is the fallback, and the 75% attach rate is evidence about that product, not the unsupervised one. Region: in a jurisdiction that licenses individual owners to run driverless vehicles, the fleet framing becomes a choice rather than a necessity, and the argument weakens. Fleet size: with a few hundred cars per city, a Tesla-owned fleet is easier to keep uniform than a mixed one; at tens of thousands, owner capacity may be the only way to grow fast enough, and the admission test becomes the main engineering problem. Model and hardware generation: if V15 needs newer hardware, the share of owner cars that can even apply may be small, which makes the Q2 2027 milestone smaller than it sounds. Company size: my read is that few companies other than Tesla have both a large owner fleet and a robotaxi operation, so the lesson for most OEMs is the acceptance-unit point, not the fleet-sharing model. And if Tesla ships per-vehicle unsupervised operation outside any geofence and it holds up, my reading was too conservative.</p>
<h2 id="what-i-would-do-differently">What I would do differently</h2>
<p>State the acceptance unit in the first sentence of any autonomy promise. &ldquo;Your car, anywhere&rdquo; and &ldquo;your car, inside our zone, run by us&rdquo; are different products, and customers should hear which one they are buying.</p>
<p>Publish the admission criteria with the date: minimum hardware, sensor and camera cleanliness checks, maintenance state, software version, and how a car is removed from the fleet. That turns &ldquo;around Q2 2027&rdquo; into a checklist owners and regulators can track.</p>
<p>Reconcile the safety-page mileage with the filing&rsquo;s cumulative unsupervised miles before admitting a single owner car. About 1.1 million miles separate the nearly two million as of 30 September from the 3.1 million as of 18 October, and that gap is still unexplained.</p>
<p>Keep improving supervised FSD as its own product, with its own success metrics, and stop letting it stand in for progress on unsupervised operation. The two are now different businesses with different acceptance tests.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
