ReadHow I Actually Work09 Aug 20262:06Semiconductors: chips, fabs & yield

Your Fab's AI Goes Blind on the 2nm Node — Here's Why

The AI That Finds Every Defect — Except on the Node That Cost You Billions

An electron-microscope column in a dark metrology bay, its viewport glowing faint warm gold
The object this week · generated illustration, no people, no brands
Video

This one has not been published to the channel yet. Subscribe on YouTube and it will turn up there.

The number
1 IN 3

GARTNER 2026

The 60-second version
  • Your fab's new AI spots defects better than any engineer — and on the brand-new node it goes almost blind.
  • Not because the model is bad, but because every one of these systems learns from history: thousands of wafers, labelled defects, known-good outcomes.
  • This video breaks down the cold-start problem in yield ramp — why AI inspection and virtual metrology deliver on mature lines while struggling exactly where the economics are worst, what the first six months of a ramp actually feel like from the yield engineer's seat, and the one approach that's genuinely closing the gap: transfer learning, which carries what a model learned on your existing tools across to the new one and cuts the modelling cycle from weeks to days.
  • Plus the numbers — Samsung's 2nm wins set to more than double this year, and Gartner's 2026 finding that only one in three MES vendors can show a live production AI use case.

Why this matters

A mature line has years of that. A node you just spent billions building has none.

What to do Monday

Starting anything new? Fix the cold-start problem on day one. Paste into Claude or Copilot: "I'm starting X next week with zero historical data. List the 8 signals I should log from day one so that in 90 days I can show a baseline, spot drift, and attribute a change to a cause. Then name the two people usually forget." Run on a new support queue it flagged the two nobody logs — freeze the category taxonomy on day one, and record arrival time separately from created time.

In the video
  1. 0:00The AI that goes blind
Over to you

Six months into a ramp — what did you actually trust first, the model or the engineer who'd seen it before?

Argue with me on LinkedIn
Sources
  1. Gartner 2026 MES Market Guide (1 in 3 vendors with a live production AI use case)
  2. SemiEngineering 2026 (cold-start — insufficient historical data at new process / equipment ramp; transfer + few-shot learning cuts the modelling cycle weeks→days)
  3. DIGITIMES 2026-08-03 (Samsung 2nm project wins expected to more than double in 2026).
Full transcript, 288 spoken words
Your fab just bought AI that spots defects better than any engineer. On the new node it's almost blind. Why? These models learn from history — thousands of labelled wafers, known outcomes. A mature line has years. A new node has none. The tool that nails a defect in seconds on your old line just guesses on the new one. AI helps least where the money is. Where's that money? Samsung's 2nm wins should more than double this year. Gartner found one in three MES vendors can show live production AI. Sound solved? One fix works. Hold that. Six months into a ramp you're not short of data. You're short of data that means anything. How do you find a pattern nobody has seen? Transfer learning. Take a model trained on tools you already run, carry it across. The modelling cycle drops from weeks to days. Not magic. Borrowed history. Now, your FabSpeak Tip of the Week. Starting anything new? Same problem at your desk — in ninety days you can't prove a single thing changed. Fix it on day one. Paste this into Claude or Copilot: "I'm starting X next week with zero historical data. List the eight signals I should log from day one so that in ninety days I can show a baseline, spot drift, and attribute a change to a cause. Then name the two people usually forget." I ran it on a new support queue. It caught the two nobody logs — freeze your category list on day one, or your ninety-day comparison quietly compares two different things. And log arrival time separately from created, or you can never tell queue delay from work delay. That's FabSpeak. A new one every week, straight from the floor.