SHADOWMODE
Live
less than a minute ago
LIVE
TSLA$...
ELONloading...
@ROBOTAXIloading...
AUSTIN TXPUBLIC DRIVERLESS — Day 207
DRIVERLESS4 CITIES LIVE
TESLA FLEET35+ VEHICLES TRACKED
TSLA$...
ELONloading...
@ROBOTAXIloading...
AUSTIN TXPUBLIC DRIVERLESS — Day 207
DRIVERLESS4 CITIES LIVE
TESLA FLEET35+ VEHICLES TRACKED
Digital Energy TerminalTesla ecosystem

ENERGY → COMPUTE → INTELLIGENCE → MONEY. SHADOWMODE TRACKS TESLA'S PHYSICAL LAYER — THE POWER-AND-COMPUTE BOUND PRODUCTS THAT ABSORB GRID LOAD AND SHIP AUTONOMY.

OPTIMUS PRODUCTION
Q1 2026 CALL · SOURCED
MODEL S/X LINE ENDS
EARLY MAY 2026SRC
FREMONT OPTIMUS PRODUCTION· INITIAL OUTPUT "QUITE SLOW" — MUSK, Q1 CALL
LATE JUL / AUG 2026SRC
GIGA TEXAS OPTIMUS FACTORY· SECOND LINE · GEN 4 VOLUME TARGET
SUMMER 2027SRC
USEFUL WORK IN FACTORIES· MUSK ADMISSION — TRACK CONVERSION HONESTLY
ZERO (JAN 2026)SRC
DEPLOYMENT PULSEROBOTAXI OPS
21
Cities
Being tracked
9
States
With robotaxi activity
35+
Fleet
Vehicles deployed
12/15
Permits
Received across markets
7
Public programs
Test programs launched
0
Testing
Driverless in progress
Driverless
45
Lead market
Miami, FL · Public driverless operation

Cybercab — We, Robot unveil (Oct 2024)

US Robotaxi Map
Shadowmode deployment pulse · self-hosted SVG
Shadowmode
21 cities · 4 driverless/testing
DLDLDLDL

Active markets

21/21

Pulse status

LIVE

Austin88%
Dallas79%
San Francisco71%
Houston71%
Oakland63%
San Jose63%
Miami55%
Mesa, Tempe50%
Las Vegas50%
Phoenix42%
Driverless Testing Tracking 25%+
9
States
With Robotaxi activity
21
Cities
Being tracked
21
Active Cities
With any progress
7
Public Programs
Test programs launched
35+
Est. Vehicles
Deployed total
4
Driverless
No safety monitor

4 cities have achieved driverless operation. 14 more projected within 9 months.

Velocity

Slowing

Active (60d)

3 cities

Near-term

14 in 6-9mo

Highlights

4 signals

4 driverless markets active1 new test launches this quarter1 cities with rising momentum5 AV-friendly states in pipeline

The Ledger

What changed, and what we said would happen

Change Log

Every cell that flips gets an entry — including our own corrections

Aug 12, 2026
CORRECTIONTerminalSourced

Safety Signals panel retired and replaced with Fleet Buildout.

The panel reported a crash count and a crashes-per-mile rate. Three problems, found together: the mileage denominator was modeled from assumed constants (fleet size x 100 mi/day x 180 days) rather than measured; the crash count was a hardcoded figure that had not changed since Dec 2025, so the displayed rate improved automatically as the fleet grew even though no new crash data had arrived; and the cited source was a private individual with no discernible connection to autonomous-vehicle reporting, who never produced the figure attributed to him. That attribution has been removed from this changelog as well. Rather than publish a corrected estimate, the panel has been replaced with Fleet Buildout, which counts vehicles deployed, driverless cities and active states directly from the milestone record — no modeling and no third-party attribution. Tesla does not publish robotaxi production figures, so deployment is what can be counted and is labelled as such.

Jul 3, 2026
FLIPMiami, FLSourced

Miami goes live: public robotaxi rides, unsupervised from day one.

Tesla launched public robotaxi service in Miami on Jul 3, 2026: its first market outside Texas and California and first on the East Coast. No driver or in-car safety monitor from day one. Model Y fleet. Roughly 20 sq mi zone including MIA airport (no terminal pickups yet). Milestones flipped: public_test_program_launched, no_safety_monitor, robotaxi_app_access_opens.

Not a Tesla App, Jul 3 2026
Jul 2, 2026
CORRECTIONTerminalSourced

Safety panel corrected: "0 incidents · Excellent" removed.

The panel previously hardcoded zero incidents and an "Excellent" verdict. It was replaced with reported crash figures attributed to a third-party compilation. The attribution was later found to be incorrect and the whole panel was retired on Aug 12, 2026 — see that entry.

Jul 2, 2026
CORRECTIONTerminalSourced

Austin driverless start date corrected: Dec 14, 2024 → Dec 14, 2025 (internal) / Jan 2026 (public).

Two panels showed "Dec 14, 2024" for the start of Austin driverless operations — a year off from the sourced record. Internal/employee driverless testing began Dec 14, 2025; public driverless rides began Jan 2026.

Jul 2, 2026
TERMINALTerminalSourced

Epistemic tiering shipped: every number now wears SOURCED, MODELED, or CLAIMED.

Modeled figures (TAM, projections, readiness scores, mile estimates) no longer carry verdict badges. Verdicts are earned only by sourced data.

This terminal

Predictions Ledger

Modeled

Calls on the record, scored in public. Never edited after posting.

Brier Score

first resolutions due Dec 31, 2026

Tesla operates public driverless robotaxi service (no safety monitor) in at least 5 US metros by Dec 31, 2026.

55%

OPEN

Judged by: Counted on this terminal's milestone matrix: "No Safety Monitor" completed in ≥5 metros, each backed by a sourced entry in the change log. Austin, Dallas, Houston count as 3 at posting.

posted Jul 2, 2026resolves by Dec 31, 2026

California grants Tesla driverless deployment permission for public rides in the Bay Area by Dec 31, 2026.

30%

OPEN

Judged by: CA DMV driverless deployment permit + CPUC authorization both granted, per the agencies' public records. Bay Area service is supervised-only at posting.

posted Jul 2, 2026resolves by Dec 31, 2026

NHTSA Engineering Analysis EA26002 results in a mandatory recall affecting the robotaxi fleet by Jun 30, 2027.

35%

OPEN

Judged by: A recall citing EA26002 that applies to vehicles operating in Tesla's driverless service, per NHTSA's public database.

posted Jul 2, 2026resolves by Jun 30, 2027

Tesla publishes per-mile safety data for its robotaxi fleet (crashes or interventions per mile, city-level) by Jun 30, 2027.

25%

OPEN

Judged by: An official Tesla publication (report, filing, or investor material) with per-mile robotaxi safety figures. Aggregate FSD-wide claims do not count.

posted Jul 2, 2026resolves by Jun 30, 2027

Brier score = mean squared error of stated probability vs outcome. 0 is perfect; 0.25 is what a coin-flipper scores. Revisions get a new entry — the original stands. JSON API

Milestone Alerts

When a tracked cell flips — a permit granted, a monitor removed, a correction logged — you get the entry. Timestamped, sourced, tiered. Nothing else.

Loading news...
Updated:
Legend:
Completed
In Progress
Not Started
Unknown
N/A
Every number wears one:Sourcedprimary sourceModeledour estimateClaimedsaid, not verified

Deployment Progress by CitySourced

LocationInsuranceAppliedPermitOperator AdsFleet AdsApprovalRoute ValApp AccessTest LaunchExpandedVehiclesDriverlessProgress
Texas
Austin
3
88%
Dallas
3
79%
Houston
3
71%
San Antonio
25%
California
San Francisco
2
71%
Oakland
2
63%
San Jose
2
63%
Los Angeles
25%
San Diego
25%
Florida
Miami
1
55%
Orlando
1
25%
Tampa
1
25%
Jacksonville
1
15%
Arizona
Mesa, Tempe
50%
Phoenix
42%
Nevada
Las Vegas
50%
New York
Brooklyn
1
13%
Queens
1
13%
Massachusetts
Boston
1
21%
Colorado
Denver
20%
Illinois
Chicago
20%
Loading fleet data...

Investor Intelligence

Leading Indicators & Risk Analysis

Readiness Index

Modeled

Weighted deployment score (0-100)

National Avg

41

6-Month Trend

6mo agoNow

City Readiness Rankings

1
Austin, TX
92
2
Dallas, TX
84
3
Houston, TX
79
4
San Francisco, CA
63
5
Oakland, CA
60
6
San Jose, CA
60

State Averages

Texas

73

Arizona

52

California

49

Nevada

43

Florida

25

Colorado

23

Score weights: Regulatory (30%) + Insurance (20%) + App Access (15%) + Fleet (15%) + Driverless (20%)

Time-to-Driverless Projection

Modeled

Estimated timeline based on Austin baseline

4

Live

12

3-5 months

2

6-9 months

0

9-12 months

3

>12 months

Driverless Active

Miami, FLLIVE
Austin, TXLIVE
Dallas, TXLIVE
Houston, TXLIVE

3-5 Months

Mesa, Tempe, AZlowConfidence
Friendly regulatory environmentRegulatory approval secured
Phoenix, AZlowConfidence
Friendly regulatory environmentRegulatory approval secured
Los Angeles, CAlowConfidence
Mixed regulatory environment
Oakland, CAmediumConfidence
Mixed regulatory environmentPublic test program active
San Diego, CAlowConfidence
Mixed regulatory environment
San Francisco, CAmediumConfidence
Mixed regulatory environmentPublic test program active
San Jose, CAmediumConfidence
Mixed regulatory environmentPublic test program active
Denver, COlowConfidence
Friendly regulatory environment
Orlando, FLlowConfidence
Friendly regulatory environment
Tampa, FLlowConfidence
Friendly regulatory environment
Las Vegas, NVlowConfidence
Friendly regulatory environment
San Antonio, TXlowConfidence
Friendly regulatory environment

6-9 Months

Chicago, ILlowConfidence
Boston, MAlowConfidence

Projections based on Austin timeline (~6 months to driverless), adjusted for regulatory environment, current progress, and milestone completion. Low confidence = early stage or restrictive regulation.

Narrative Pressure Index

Modeled

Market patience & execution momentum

Pressure

High

Proof Velocity

1.7

milestones/mo

Half-Life

Active

45d since milestone

Reg Exposure

Moderate

33% restrictive

Narrative Drift

Story-ledMixedExecution-led

Execution-Led (milestones)

What Changes the Stock

  • First city achieves fully driverless operation
  • 3+ cities with public test programs
  • Second market achieves driverless status

Last Catalyst Impact

Execution milestones move the stock. Promises don't.

Market Read

  • Slowing velocity may test investor patience on robotaxi timeline.
  • Market may discount future robotaxi announcements until execution resumes.
  • Consider regulatory or operational bottlenecks as potential causes.

Derived from deployment data. Not investment advice.

Fleet Buildout

Vehicles on the road, and where

35

Vehicles deployed

Sourced

4

Cities running driverless

Sourced

9

States with activity

Sourced

21

Cities with any activity

7

Public programs launched

9

Avg vehicles per driverless city

35 vehicles counted across 4 driverless cities in 9 states, compiled from the per-city deployment record. These are vehicles deployed, not manufactured — Tesla does not publish robotaxi production figures, so any manufacturing number would be an estimate rather than a count.

Data Confidence

Counted

Every figure above is a count of the milestone records behind this dashboard — no modeling, no assumed rates. It is as current as those records, and no more.

Why we show this: Buildout is the rollout's real clock — how many cars, actually driverless, in how many places. We publish what can be counted, and label what can't.

Public Trust Signal

External validation & legitimacy

Trust Score

66

Moderate
Regulatory Permits
3states approved
Insurance Coverage
$5Mliability per incident
Third-Party Validation
1Safety audit completed
Public Operations
3driverless markets (TX)

NHTSA Engineering Analysis (EA26002) active • CA: supervised-only, no AV permit (CPUC)

Analyst assessment from public sources — not a live feed; updated periodically. As of Jun 2026: Tesla runs driverless rides in Austin (since Jan 2026) plus Dallas & Houston (since Apr 2026); the Bay Area service is supervised-only (no CA AV permit). A formal NHTSA Engineering Analysis (EA26002) covers ~3.2M FSD vehicles.

Data Confidence

Medium

Measures "permission to scale" via external validation (permits, insurance, audits) — not Tesla claims. Updated: 2026-06-19

Economic Impact

Modeled

Estimates from stated assumptions — not reported revenue

Annualized TAM

$8.6M

95

Total Fleet

1.1K

Daily Rides

$90K

Rev/Vehicle

4

Active Cities

Active-market run rate vs modeled TAMTAM counts active cities only

Current (Active Markets)

$8.6M

Total Addressable

$8.6M

Revenue by City

1Austin, TX
medium$3.2M
Fleet: 35Rides/day: 403Rev/vehicle: $90K
2Oakland, CA
low$1.8M
Fleet: 20Rides/day: 230Rev/vehicle: $90K
3San Francisco, CA
low$1.8M
Fleet: 20Rides/day: 230Rev/vehicle: $90K
4San Jose, CA
low$1.8M
Fleet: 20Rides/day: 230Rev/vehicle: $90K

Estimates based on: Fleet size from public reports/filings, avg rides/vehicle/day from industry benchmarks (~8-15 rides for active fleets), avg fare $15-25 per ride. TAM includes cities with any robotaxi activity.

Regulatory Friction

State-level AV policy environment

5

AV-Friendly

2

Mixed

2

Restrictive

AV-Friendly- Streamlined permits, supportive legislation
AZ2 cities
~85d avg permit
CO1 cities
FL4 cities
NV1 cities
~8d avg permit
TX4 cities
~60d avg permit
Mixed- Some regulatory complexity
CA5 cities
~180d avg permit
IL1 cities
Restrictive- Significant regulatory barriers
MA1 cities
~240d avg permit
NY2 cities
~365d avg permit

Key insight: Tesla isn't necessarily slow - regulatory environments vary significantly. TX, AZ, and NV have ~8-85 day permit timelines vs CA at ~180 days and NY at 365+.

Rollout Velocity

Slowing

Last Mo

3

This Mo

0

60-Day Activity3 cities
Quarter Launches1 vs 2
Driverless Events4

Deceleration phase. Regulatory bottleneck likely.

Irreversibility

Modeled
Entrenched

Who has made a decision they can't walk back?

Regulatory

TX S.B. 2807 framework active

Insurance

Multi-state underwriting live

Corporate

Fleet CapEx deployed

Operational

Driverless ops running

Reversal CostPROHIBITIVE
Last CommitmentApr 2026

Tesla • Dallas & Houston driverless service

Multi-state capital, insurance, and regulatory commitments in place.