Changelog

Every release that can touch a tool, written down.

Waferira has not shipped a release yet, so this page is the build log: what is planned by phase, how a release will reach a module, and the policy for promoting models and autonomy. When the first release ships, its notes replace the top of this page.

0 releases shipped3 planned phasesRelease policy published

Status

Pre-release

QUEUEDMVP · 0 to 6 months

The first release is SECS/GEM connectors, the agent loop, the review console and the IP-isolated excursion and quality audit log, for one wedge workflow on one module.

Planned

The build log by phase

Everything here is planned. Nothing here has shipped.

0 to 6 months · planned

Phase 1

  • Onboard 2 to 4 IDM or foundry design partners on the wedge workflow with baseline yield, excursion, cycle-time and engineer-load metrics captured first
  • Ship the MVP: SECS/GEM connectors, agent loop, review console, IP-isolated excursion and quality audit log
  • Prove accuracy and yield, excursion and cycle-time ROI in shadow then assist mode
  • Security and IP baseline: SOC 2 Type I and fab-security review in progress, on-prem and fab-edge deployment

6 to 12 months · planned

Phase 2

  • Convert design partners to paid; early revenue
  • Graduated autonomy for low-risk APC, defect and metrology loops; fab twin hit-yield-before-run
  • Second module within the fab; deeper tool integrations
  • SOC 2 Type II; SSO and RBAC; IP-isolation and security assurance packages

1 to 3 years · planned

Phase 3

  • Own the full litho, etch, deposition, CMP, metrology and yield loop end to end
  • Single fab to multi-fab IDM or foundry to global semiconductor group
  • Process-tool and inspection and metrology vendor channel; international expansion
  • Data-network products: yield, excursion, cycle-time and virtual-metrology benchmarks as premium tiers
Policy

How a release reaches a module

The promotion and rollback rules.

  • Models are promoted by module. A new model version reaches one module or tool fleet as a canary before it reaches the fab, and falls back to the previous validated version automatically.
  • Autonomy policy is versioned like code. Recipe windows, parameter limits, tool-state checks and approval chains are reviewed and recorded before a release can write to a tool.
  • Every release carries its evaluation record. Golden datasets and judged evaluations gate model and prompt changes in CI before promotion; engineer review and immutable audit logging follow.
  • Rollback conditions are declared up front. Each release names the signals that return a recipe to its previous qualified version.
Support

Version support, when versions exist

The support policy the first releases will follow.

Version support
ComponentVersioningSupport window
Fab-edge runtimeSemantic, per nodeCurrent and previous minor
ModelsPer module, per process familyPrevious validated version kept for fallback
Autonomy policyReviewed and versioned like codeHistory retained in the audit log
SDK and CLIDesign previewBreaking changes expected before release
Run timeline · scenario

The reference scenario, per release

Each release will be checked against this scenario before it reaches a module.

run_7b2e9c Module M2 · 300 mm · metal-1 · lot L-48213 illustrative scenario SUCCEEDED
  1. 01 ingest.lot SUCCEEDED 0.7 s

    Fab Orchestrator · Pulled lot L-48213 from fab MES: 25 wafers, 300 mm, metal-1 layer, route, reticle, overlay and CD spec and the standing cycle-time target. Locked the target envelope for the run.

  2. 02 twin.simulate SUCCEEDED 38 s

    Fab Twin · Simulated 64 candidate correctable, recipe and dispatch sets on the as-run fab twin and ranked them on predicted overlay residual, CD uniformity, excursion risk and cycle time.

  3. 03 litho.correctables SUCCEEDED 1 m 20 s

    Litho-and-Overlay · Per-field overlay correctables and a focus-dose trim written to scanner SCN-07 over SECS/GEM after the previous lot's residual trended toward the control limit. Predicted overlay residual back inside spec.

  4. 04 etch.uniformity SUCCEEDED 58 s

    Etch-and-Depo · Chamber B on etcher ETCH-12 showed an edge-fast uniformity drift in FDC. Pressure and RF trims written within the qualified recipe window; predicted CD uniformity recovered.

  5. 05 cmp.removal SUCCEEDED 46 s

    CMP-and-Implant · Downforce and platen-speed trim on CMP-03 against the virtual removal-rate estimate to hold post-CMP thickness and dishing inside the window.

  6. 06 inspect.classify SUCCEEDED continuous

    Defect-and-Inspect · Inline optical, e-beam review and SEM imagery fused at the tool edge. 1,412 events classified, most dispositioned nuisance; one reticle-repeater signature on three dies flagged for review.

  7. 07 vm.score SUCCEEDED 2.1 s

    Metrology-and-Virtual · Virtual metrology scored every wafer at post-etch and post-CMP from tool-sensor and FDC signatures. Two wafers routed to physical metrology on predicted variance; the rest sampled at plan.

  8. 08 approve.human APPROVAL 1 m 04 s

    Fab Orchestrator · The reticle-repeater signature called for a reticle inspection hold and a recipe move outside the qualified window. Held for the module process engineer and approved at 03:14:27.

  9. 09 dispatch.route SUCCEEDED 4.3 s

    Yield-and-Dispatch · Dispatch re-optimised across 1,840 lots in WIP under reticle, chamber and qualification constraints. The lot routed to the qualified chamber with the shortest predicted queue; AMHS move issued to the stocker.

  10. 10 lot.release SUCCEEDED 1 m 05 s

    Quality-and-Conformance · Lot L-48213 moved on: genealogy written (recipe moves, correctables, FDC signatures, VM scores, defect map, approvals) and checked against the layer spec.

Tool calls · scenario

What the tool log will show per release

Every tool invocation, argument and result is written to an append-only, IP-isolated, human-readable log, and every reasoning step is expandable. Nothing about a run is hidden from the fab.

tool-call stream · run_7b2e9c
  1. 03:02:10mes.read_lot({ lot: "L-48213", layer: "M1", module: "M2" })
  2. 03:02:11ok 25 wafers · reticle R-M1-114 · overlay and CD spec locked
  3. 03:02:11twin.simulate({ candidates: 64, horizon: "lot" })
  4. 03:02:49ok best set #41 · overlay residual 2.6 nm · excursion risk 0.05
  5. 03:02:50policy.evaluate({ set: 41, autonomy: "L3" })
  6. 03:02:50ok 7 recipe writes inside qualified window · 1 move requires human approval
  7. 03:02:51secs.write_recipe({ tool: "SCN-07", correctables: "per_field", dose: "-0.3%" })
  8. 03:04:11ok predicted overlay residual 3.1 → 2.6 nm · CD on target
  9. 03:04:12secs.write_recipe({ tool: "ETCH-12", chamber: "B", pressure: "+1.5%", rf: "-0.8%" })
  10. 03:05:10ok edge-fast drift cleared · predicted uniformity inside window
  11. 03:05:11secs.write_recipe({ tool: "CMP-03", downforce: "-2%", platen: "+1%" })
  12. 03:05:57ok virtual removal rate on target · dishing inside window
  13. 03:05:58vision.stream({ tools: ["INS-02", "EB-01", "SEM-04"] })
  14. 03:09:40repeater: 3 dies · same field position · reticle R-M1-114 · killer class
  15. 03:09:41vm.predict({ lot: "L-48213", steps: ["post_etch", "post_cmp"] })
  16. 03:09:43ok 25 wafers scored · 2 routed to physical metrology
  17. 03:09:44approval.request({ action: "reticle_hold", recipe_move: "outside_window" })
  18. 03:14:27ok approved by module process engineer · OCAP linked · logged
  19. 03:14:28cuopt.dispatch({ wip: 1840, constraints: ["reticle", "chamber", "qual"] })
  20. 03:14:32ok lot routed to ETCH-12/B · AMHS move to stocker ST-14
  21. 03:14:33amhs.move({ foup: "F-20911", to: "ST-14" })
  22. 03:15:21ok carrier delivered · handling exceptions 0
  23. 03:15:22mes.log_lot({ lot: "L-48213", genealogy: "full" })
  24. 03:16:27ok scenario complete · 10 steps · 1 hold reviewed · released

Reasoning trace

Plan, thought, action, observation, exactly as the orchestrator would record it.

GoalRun lot L-48213 through metal-1 on module M2, hold overlay and…

Run lot L-48213 through metal-1 on module M2, hold overlay and CD inside the layer spec, catch any excursion before physical metrology, and dispatch on cycle-time target.

PlanSimulate the lot on the twin first. Lead with litho so the cor…

Simulate the lot on the twin first. Lead with litho so the correctables are right before etch, then trim etch and CMP against virtual metrology, keep inspection continuous, and hold anything outside the qualified window for a human.

ThoughtThe previous lot's overlay residual on SCN-07 trended toward t…

The previous lot's overlay residual on SCN-07 trended toward the control limit. On the twin, a per-field correctable update with a small dose trim brings the predicted residual back to 2.6 nm without touching focus.

Actiontwin.simulate(candidates=64) returns set #41: per-field correc…

twin.simulate(candidates=64) returns set #41: per-field correctables and dose minus 0.3% on SCN-07, chamber B pressure and RF trims on ETCH-12, downforce minus 2% on CMP-03.

ObservationSet #41 predicts overlay residual 2.6 nm, CD uniformity inside…

Set #41 predicts overlay residual 2.6 nm, CD uniformity inside window and excursion risk 0.05. Nine candidates cut cycle time further but routed the lot to an unqualified chamber and were discarded.

ActionExecute set #41 under autonomy level L3: seven recipe writes i…

Execute set #41 under autonomy level L3: seven recipe writes inside the qualified window, the reticle hold and the out-of-window move routed to the module process engineer.

ObservationReticle-repeater signature on three dies at 03:09:40 from the …

Reticle-repeater signature on three dies at 03:09:40 from the fused inspection stream. Virtual metrology routed two wafers to physical measurement on predicted variance.

OutcomeScenario complete. Overlay and CD predicted inside spec, the r…

Scenario complete. Overlay and CD predicted inside spec, the repeater held and reviewed with the OCAP linked, the lot dispatched to a qualified chamber and released with full genealogy.

Autonomy

Four levels, set per agent and per tool

A fab does not go from manual APC to unattended control in one step. Waferira makes the level explicit, auditable and reversible at any time. The first release runs shadow mode, then assist mode, then graduated autonomy for low-risk APC, defect and metrology loops.

Autonomy levels and the human role at each
LevelWhat the agent doesWhat the human doesWhere it sits in a pilot
L1 · AdvisoryRecommends recipe moves, dispositions and dispatch, with citationsEnters every change manuallyShadow mode, first on the design-partner cell
L2 · SupervisedProposes a recipe write or hold; it executes on approvalApproves each move in the review consoleAssist mode, where accuracy and ROI are proven
L3 · BoundedWrites inside the qualified recipe window, tool-state checks and OCAP linkageApproves holds, out-of-window moves and lot releaseGraduated autonomy for low-risk APC, defect and metrology loops
L4 · Qualified loopsRuns a qualified loop without prompting, inside its envelopeSets the envelope; reviews the shift recordPlanned; reserved for loops the fab has qualified
Accelerated computing

Physical AI, at the tool

Computational lithography, defect classification on e-beam and SEM imagery, per-wafer virtual metrology and a full-fab twin are among the most compute-intensive workloads in manufacturing. Waferira keeps IP-sensitive inference and feature storage at the fab edge and runs training, simulation and optimisation on GPUs the fab controls.

Metropolis · DeepStream · Holoscan · TensorRT

Inspection vision

Inline optical, e-beam and SEM imagery and sensor fusion on fab-edge GPUs. 10 to 50 inspection streams per pilot module and sub-200 ms priority defect triage are the design targets.

CUDA · RAPIDS · Triton

Virtual metrology and FDC

High-volume multivariate tool-sensor and FDC time-series scoring on every wafer, 1 to 5 seconds per lot-step in the design, with nightly retraining as recipes and chambers drift.

DGX or HGX · CUDA · cuDNN

Training

Defect, virtual-metrology and process-response models retrained per process family; 500 to 2,000 GPU-hours per family per quarter is the design target. Dedicated capacity is planned.

Omniverse · OVX

Fab twin

As-run process and flow simulation, 1,000 to 10,000 candidate recipe, metrology and dispatch scenarios per fab per day in the design. OVX access is planned.

Cosmos · Omniverse Replicator

Synthetic rare events

Rare defect, particle, overlay-drift, CMP-dishing and film-uniformity variants generated and validated against real distributions before promotion. Planned.

cuOpt · RAPIDS

Dispatch optimisation

Constrained WIP dispatch re-optimised every 1 to 5 minutes across reticle, chamber, route, tool-state and cycle-time constraints.

Jetson Orin · Isaac · TensorRT

AMHS and handling

Local FOUP and robot perception and exception detection at the fab edge. Jetson Thor is planned for higher sensor density.

NIM · NeMo · Retriever · Guardrails · AI Enterprise

Process reasoning

Tenant-isolated process Q&A and OCAP reasoning over recipes, SEMI procedures and audit logs, with citations enforced on every answer.

FAQ

Straight answers

The questions fab directors and process engineers ask in the first meeting.

Yes, over SECS/GEM, but only inside the qualified recipe window for that tool, with per-parameter limits and tool-state checks, and only at the autonomy level your fab has set. Level 1 is advisory: Waferira recommends and an engineer enters everything. Design partners start there, in shadow mode.

Get started

Follow the release line

Ask to be told when the first release ships.