The future is arriving badly explained.
In brief.
Updated on · Four signals worth your attention.
TSMC’s 2nm chips are showing up in revenue.
TSMC says its 2-nanometer technology generated 8% of third-quarter wafer revenue. The financial report makes this chipmaking generation’s commercial footprint visible. The node name is not a literal transistor size; the figure measures revenue share, not chip volumes, and comes from the company’s own quarterly results.
Three U.S. grids hit summer demand records.
A new EIA analysis puts summer peak demand at 162.6 gigawatts in PJM, 91.1 in ERCOT and 58.0 in Southwest Power Pool. The records occurred on different July days, mostly during heat waves. They measure peak hourly load, not annual electricity use; reported operator data can be revised.
ORCA puts its new quantum computer beside GPUs.
ORCA says its PT-3 is running at Digital Realty’s London innovation lab. It reports an energy-scheduling workflow more than 12 times faster than on its predecessor, at the same solution quality. That is a generational comparison within a hybrid quantum-classical system, not proof that it beats the best conventional solver.
Cambridge’s quantum center starts with nine projects.
IonQ says its new Cambridge research center has opened with nine initial projects. One will develop microscopic mirrors to collect light from trapped ions more efficiently, a step toward linking quantum processors. The center is open; the promised 256-qubit computer and entanglement network are still described as future deployments.
Sources published October 15, 2026. TSMC reports on Q3; EIA analyzes July peaks. Company results and future deployment plans are attributed, not independently proven.
In Charts.
EVs Took 0.67% of U.S. Electricity in Early 2026
The axis ends at 1%, not 100%. These national estimates cover light-duty battery-electric and plug-in-hybrid vehicles, not every electric vehicle or a local grid's peak load.
Twice the charging, a small slice of the total
Cars can draw more electricity without becoming a large part of the national power bill. EIA estimates that U.S. light-duty electric vehicles used 13.7 terawatt-hours in the first half of 2026, up from 5.9 TWh in the same months of 2023. Total U.S. electricity end use in the latest half-year was about 2,043.3 TWh. Divide the two and EVs account for 0.67%.
The comparison uses January through June in every year, rather than mixing winter and summer halves. It starts in 2023 because EIA changed how it estimates vehicle miles traveled that year; earlier observations are not strictly comparable.
The country is not one charging socket
A national energy total cannot show whether a neighborhood transformer can serve several new chargers, or whether charging coincides with a local evening peak. Terawatt-hours measure energy over a period; those constraints also depend on where electricity is drawn and how much power is needed at once.
The useful distinction is scale: EV charging grew rapidly from a small national base. That does not make every local connection easy, but it does keep a growing load from being mistaken for a dominant share of U.S. electricity use.
Sources, Method & Data
Calculation. We sum January–June monthly observations in EIA's September 2026 Table 7.6 and downloadable data. Share = estimated EV electricity use (series ESVHPUS) / total electricity end use (ELTCPUS) × 100. Both series are published in million kWh; 1,000 million kWh equals 1 TWh. Ratios use unrounded source values. Display rounding is not a measure of model certainty.
Coverage. The numerator estimates electricity used by on-road light-duty battery-electric and plug-in-hybrid vehicles up to 8,500 lb gross vehicle weight, including cars and light trucks. It is not a census of charger meters and excludes heavy trucks, buses, off-road vehicles and gasoline burned by plug-in hybrids. The geography is the 50 U.S. states and District of Columbia. EIA's estimation method combines vehicle stock, travel and energy-use assumptions.
Denominator and break. Electricity end use is retail sales plus direct use, not power-generation capacity, electricity generation or total primary energy. EV use is already part of that denominator and is not added again. This is not a claim to measure every behind-the-meter rooftop-solar kWh. EIA notes a vehicle-miles-traveled methodology change beginning in 2023, so no earlier-year growth comparison is drawn.
| Period | EV use | Total end use | EV share |
|---|---|---|---|
| Jan–Jun 2023 | 5.9 | 1,899.3 | 0.31% |
| Jan–Jun 2024 | 8.2 | 1,967.6 | 0.42% |
| Jan–Jun 2025 | 10.9 | 2,021.3 | 0.54% |
| Jan–Jun 2026 | 13.7 | 2,043.3 | 0.67% |
Source version and rights. New explanation of existing data, not an October demand reading. Latest observations: June 2026. EIA's public aggregate data are reused with attribution under its reuse policy. Original chart by Vastkind; no EIA logo or third-party microdata reproduced.
Estimated EV electricity use more than doubled between the first halves of 2023 and 2026. Its national share remained below 1%.
Explore the chartBattery Incidents Barely Fell. Capacity Almost Doubled.
These are report-snapshot values, not a complete count of every battery failure. Annual events divided by installed GWh are not an individual site's failure probability. The public CSV has 23 events for 2025, versus 24 in the report; the versions are not combined.
The denominator does most of the moving
For a community considering a large battery installation, a falling incident rate sounds reassuring. But the numerator matters too: did incidents become rare, or did the amount of installed storage grow much faster?
In EPRI's October 2026 report, the recorded annual count falls from 26 to 24, a decline of 7.7%. The published capacity figure rises from 343 to 634 gigawatt-hours, up 84.8%. Divide one by the other and the result falls from 7.58 to 3.79 incidents per 100 GWh, a 50.1% decline. The large change in that ratio is not a halving of the incident count.
A useful ratio is not a site-risk forecast
The report tracks major internal thermal incidents in stationary lithium-ion storage, including utility and commercial or industrial installations. It is not a census of every malfunction, electric-car battery or home battery. Reporting is incomplete, and each incident counts once regardless of its severity.
The denominator is stored-energy capacity, not electricity generated, power in gigawatts or operating years. Newly installed capacity can enter the annual stock without having operated for a full year. We also could not independently verify that the proprietary capacity series covers every installation type in the incident count.
The fair reading is narrower than “batteries are half as dangerous”: in this report, recorded incidents fell slightly while the installed capacity denominator rose sharply between these two years. A decision about one installation still depends on its design, operation and consequences of a failure.
Sources, Method & Data
Snapshot and calculation. Four aggregate values come from printed pages 6–7 of EPRI report 3002034920, dated October 2026. Its PDF was created on October 8; the exact first-publication day was not established. This chart is a new explanation of 2024–2025 data, not a new incident count for October 2026. Each ratio is annual recorded events / cumulative installed capacity in GWh × 100. Changes compare 2025 with 2024. Input capacities are already rounded; two decimal places on the ratio do not imply extra measurement precision.
Source versions do not fully reconcile. The public stationary-storage CSV retrieved on October 10 carried a September 29, 2026 Last-Modified header. It contains 26 events dated 2024 and 23 dated 2025, versus 26 and 24 in the newer report. Some regional and confidential-case totals also differ. A version difference is plausible, but no case-by-case revision history resolves it. We reproduce the report aggregates, not a reconstructed current global total; no cases have been invented or added to the CSV.
Coverage and denominator. EPRI includes major thermal events caused by internal battery-system failures and excludes external causes such as wildfires. Some cases are confidential. The report's source figure cites Benchmark Mineral Intelligence's BESS Forecast Q1 2026, China Energy Storage Alliance and Korea Electrical Safety Corporation. The underlying capacity records were not independently accessible. Matching of utility, commercial/industrial and UPS coverage between numerator and denominator remains unverified. This simple annual quotient is not exposure in GWh-years, an individual failure probability, a severity-adjusted measure or the report's separate age-based analysis.
| Year | Recorded incidents | Capacity (GWh) | Incidents per 100 GWh |
|---|---|---|---|
| 2024 | 26 | 343 | 7.58 |
| 2025 | 24 | 634 | 3.79 |
Graphic and rights. Own calculation and original graphic using four published aggregate facts; no EPRI figure or layout reproduced. EPRI's report is © 2026, all rights reserved, not an open-licensed dataset. The accessible CSV is linked for source-version checking, not substituted for the report.
EPRI's October report records 26 incidents in 2024 and 24 in 2025. A much larger capacity denominator roughly halves the ratio, not an individual battery's risk.
Explore the chartCan AI Customer Service Solve the Same Case Four Times?
Numbers inside the bars count cases, not individual runs. “Every time” means success in all four recorded runs, not four chances to succeed once. Two examples, not a model ranking.
Getting it right once is the easier bar
Imagine asking customer service to replace a lost card. A successful interaction is encouraging. The harder question is whether the same request still works when the conversation takes a different path.
In these published simulations, Claude Opus 5 succeeded at least once on 64 of 97 cases; Qwen 3.8 Max did so on 71. Require success in all four runs, and those counts fall to 31 and 34. The middle segment shows cases that sometimes worked and sometimes did not.
A benchmark, not a bank
These are recorded evaluations in a fictional banking environment, with an AI playing the customer. Vastkind grouped the original scores; we did not run the agents again or independently regrade their conversations. The chart measures neither real customer satisfaction nor financial safety.
Both agents received the same embedded case definitions and tool access, but used different reasoning settings. These two examples do not establish a general model ranking or equal-cost comparison. Four runs per case are a small sample, not a guarantee about the next run.
A further reproducibility limit: 15 of the 97 embedded task definitions differ from the code revision named in the run files. They match between the two files analyzed here. The reason for the repository discrepancy is unresolved.
Sources, Method & Data
What we counted. The τ-knowledge banking_knowledge AllTools run files contain 97 case definitions and 388 runs per model, four distinct trial IDs per case. We treated a logged reward within 0.000001 of 1 as success, matching the project metric, then grouped cases by zero, one to three, or four successes. Both selected files contain no infrastructure-error terminations. Bar widths are group counts divided by 97; labels give the counts.
Settings and timing. Qwen 3.8 Max used xhigh reasoning; Claude Opus 5 used max. Both used GPT-5.2 with low reasoning as the customer simulator and a 200-step limit. The metadata evaluation date is August 3, 2026; raw timestamps span August 3–4 without a stated time zone. The submission date is August 4; the hosted files also carry August 4 modification timestamps. This is a new explanation of that snapshot, not a new October test or a comprehensive current leaderboard.
Denominators matter. Individual-run success was 189/388 for Claude and 214/388 for Qwen. That average is not the first attempt. “At least once” counts cases with one or more successes; “every time” counts cases with four. We make no independence assumption or statistical-significance claim.
Original records. Repository snapshot; MIT code license. Own aggregation and graphic, not a copied source figure. The hosted conversation files carry no separate license notice; full dialogs are not republished here.
- Claude Opus 5: submission metadata; original run file (about 240 MB). SHA-256:
80bd60cd0dc19855e685b85ef2c40efcbc2dabae1ffa16988b40b781cbeee2a3. - Qwen 3.8 Max: submission metadata; original run file (about 240 MB). SHA-256:
8c8191c43dfb2d21c1322cc154740e5e6044151837ab817c2cbbcd13ffeb626e.
Task-version boundary. The run files name code commit fc0055dc4e0a316c3f83133267fbd6faaa770992. Fifteen embedded task definitions differ from that revision and from the repository snapshot above. Our counts describe the scores in the published run files. They do not establish an exact reproduction from the named code revision. Other model results were not included because their comparability was not fully verified.
| Model | 0 of 4 | 1 of 4 | 2 of 4 | 3 of 4 | 4 of 4 | Total |
|---|---|---|---|---|---|---|
| Claude Opus 5 | 33 | 11 | 12 | 10 | 31 | 97 |
| Qwen 3.8 Max | 26 | 14 | 5 | 18 | 34 | 97 |
Related: Can AI spot an IKEA assembly mistake? A different capability test, with its own limits.
Two AI agents, 97 simulated cases each, four runs per case. Most cases succeed at least once. Far fewer succeed every time.
Explore the chartLatest
Pick a frontier.
Seven fields. A clear place to begin.
Stay ahead
of the story.
A personal take on the week. By Dorian.
Occasional editions. Free to subscribe.
Unsubscribe anytime.