Managed-agent OSAT incident review

OSAT Yield Watchtower

Persistent agent loop for package and test excursions. It watches package maps, X-ray/SAM clues, assembly travelers, equipment traces, final-test bins, and reliability data, then assembles a cited packet for engineer-approved containment.
Watch drift Investigate evidence Verify claims Contain with approval
Symptom: Corner-heavy fail pattern detected on SiP Lot AP-2097 / Strip 14.
Ready: incident data loaded
Incident State Loading replay Waiting for watchtower_state.json
Replay Score -- Waiting for replay score
Top Suspect -- -- lots exposed
Managed Runtime Checking Waiting for local bridge
Guardrail Human approval Approval required before holds or shutdowns

Visual evidence

Public samples + simulated incident timeline

The incident timeline is simulated. These samples come from public manufacturing datasets, showing the screen-visible evidence layer before private OSAT data is connected.

WM-811K wafer defect pattern examples
WM-811K wafer-map patterns
DeepPCB defect detection result with bounding boxes
DeepPCB defect localization
DeepPCB tested image sample
DeepPCB tested board image

Evidence artifacts

Test records + package strip map

Each incident replay has concrete files the agents can inspect, cite, and score against: final-test records, a package map, a rendered visual, and a scenario answer key.

Rendered package strip map for the selected scenario

Yield economics

Why the drift window matters

A one percentage-point yield movement can be worth tens to hundreds of millions annually in high-volume semiconductor flows. In OSAT, the costly case is package/test drift that burns already-good die, substrates, assembly time, and customer trust before containment.

Mechanism wafers/mo × 12 × dies/wafer × yield point × value/die Use contribution value or margin for defensible business cases.
Example A ~$115M/year 100k wafers/mo, ~640 dies/wafer, +1 point, $15 value/die.
Example B ~$77M/year 20k wafers/mo, ~64 dies/wafer, +1 point, $500 value/die.

Investigation Agents

The coordinator assigns evidence, runs specialist checks, and merges only cited findings into the incident packet.

0 agents complete

Long-Running Agent Loop

watch / investigate / verify / contain

Reflow trace cross-exam

waiting

Assembly commonality

not run