ReadHow I Actually Work09 Aug 20262:063 min readSemiconductors: 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 picture for this piece. Made for it: no people, no brands.

In plain words

Your factory's AI spots defects better than any engineer. On the newest line, it goes almost blind.

Every inspection AI learns from history: thousands of wafers, labelled defects, known-good results.

A mature production line has years of that. A brand-new line, the one that just cost billions, has none.

This is the cold-start problem. The AI works best where the money is safest and worst where the money is at risk.

Gartner says about one company in three hits this wall on a new project.

The fix is not a better model. It is deciding on day one what to record, so the history exists when you need it.

Picture it. A doctor who has only ever seen one disease is confident right up to the first new one.

Why it matters to you. Starting anything new? List the eight signals you should log from day one. Six months from now, that list is the difference between an AI that helps and one that guesses.

Terms in this piece

ramp yield ramp
The stretch between a finished fab building and a wafer it is allowed to sell. Every tool is qualified one at a time and every recipe qualified on that tool, using wafers that are consumed by the proving and never sold.

The number

1 IN 3

COMPANIES HITTING THE COLD-START WALL · GARTNER 2026

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.

The honest caveat

Cold start is real, but transfer learning and physics-based models narrow it, and a new line borrows history from the one before it. The gap closes in months, not years. Deciding what to log on day one still shortens it.

Your turn

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. AnalystGartner 2026 MES Market Guide (1 in 3 vendors with a live production AI use case)
  2. As citedSemiEngineering 2026 (cold-start — insufficient historical data at new process / equipment ramp; transfer + few-shot learning cuts the modelling cycle weeks→days)
  3. PrimaryDIGITIMES 2026-08-03 (Samsung 2nm project wins expected to more than double in 2026).
Read the full script (288 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.