Platform architecture · Read-first by design

Five layers up.
One gated write path down.

How 34 semiconductor-native AI products run on the estate you already own — SAP, MES, PLM, EDA — without ripping anything out, and without writing a single record no human approved.

Read-first overlay Named human approval gates On-prem · VPC · air-gapped No training on your data

Why this architecture

GenAI pilots with no P&L impact
0
MIT NANDA, Aug 2025 — why SemAi deploys read-first, inside your workflow
Time to first value
Weeks
Read-first connect — vs 9–18-month suite implementations
Answers cited — or abstained
0
Grounded or blank: the platform abstains rather than bluffs
Unattended writes to SAP or MES
0
Every write passes a named human approval gate — audited
The platform, layer by layer

Five layers between your systems and your decisions

Select a layer to see what lives inside it — and what it means on your P&L. Data flows up, read-first. Exactly one write path flows back down, gated.

Layer 1 · Foundation

Your Enterprise Systems

Weeksread-first connect to first value — vs 9–18-month suite projects
0 replacedERP, MES and PLM stay the systems of record — day 1 and day 1,000
SAP ERP / Oracle MES — Camstar · FactoryWorks · Critical Manufacturing PLM — Teamcenter · Windchill EDA — Cadence · Synopsys · Siemens EDA Equipment — SECS/GEM · OPC-UA Sensors & FDC streams Plant historians
What it means for the CEO

Nothing is ripped out, nothing re-implemented — we attach to what you already trust.

Layer 2 · Data

Semiconductor Data Fabric

Days → hourstime-to-root-cause once the genealogy graph does the join
1 canonical modellots · wafers · tools · recipes · quals · suppliers — golden records, lineage on every hop
Read-first connectors Canonical fab data model Genealogy graph — wafer · die · unit · lot · tool · recipe · test · field-return Entity resolution (golden records) Event streams & lineage
What it means for the CEO

The cross-system joins your scarcest engineers do by hand during every excursion get built once — and compound with every lot.

Layer 3 · Models

Digital Twin

~2 wks → minutesdetection-to-action on supply shocks vs the industry norm
3 twins, livethe fab · the fleet · the multi-tier supply network — queryable, kept current by L2
Fab twin — WIP, tools, recipes, schedules Equipment twin — per-tool health, RUL, spares Supply twin — foundry → bump/sort → OSAT → test Scenario engine — costed what-ifs
What it means for the CEO

Rehearse the shock before it costs you: “lose 20% substrate” comes back as a costed mitigation plan — not a two-week war room.

Layer 4 · Intelligence

AI Agent Mesh

0unattended writes to SAP or MES — by construction, not by policy memo
100%of numbers set by deterministic solvers — the LLM never does math
Task agents — expedite · classify · RCA · draft Reasoning over the Decision Graph Deterministic engines (CP-SAT) set the numbers Guardrails — cite-or-abstain · policy bounds · evals Named human approval gates Single audited writer
What it means for the CEO

AI proposes; a named human approves — which is exactly what lets agents sit next to export-controlled shipments and $100M tools.

Layer 5 · Experience

Experience

1 ranked feeddecisions with evidence and dollar impact attached — and an Approve button
▮▮▮ / ▮▮ / ▮an evidence badge on every number — never a “confidence %”
Command centers — ranked decision feeds Copilots — cited answers, honest abstains Approval consoles & audit trails APIs & board packs
What it means for the CEO

Monday morning is a decision feed, not a data hunt.

Inside an agent

Anatomy of a SemAi agent

Every agent runs the same governed loop — perceive, reason, act, learn — with a named human gate before any write. Below: a live yield-excursion investigation, exactly as Yield AI runs it.

Guardrails on every step

Cite-or-abstain — never bluffs Deterministic engines set the numbers Evidence badges — ▮▮▮ / ▮▮ / ▮ Policy bounds per agent Evals-gated releases Immutable audit trail
YIELD AI · EXCURSION INVESTIGATION · LOT A-17

Recommendation — Yield AI

evidence strong ▮▮▮

Hold lots from wafers W-2214–W-2219 · disposition: re-screen at sort · 8D containment draft attached. Root cause in hours, not days — the engineer approves; the agent authors.

The gates have names, not job descriptions

Writes are scoped to a decision type and a named role. Four of the gates running across the platform today:

Lot disposition

Hold / re-screen decisions from a yield RCA. Approved by the quality engineer — the only write to MES.

Yield AI

Dispatch priority

Next-lot-on-tool recommendations on the test floor. Approved by the shift lead; MES stays system of record.

Production AI

PM work order & spare

Predictive maintenance with explicit cost trade-offs. Approved by the reliability owner; written to SAP-PM.

Maintenance AI

Export holds & licenses

Same-day order-book re-screens when rules change. Approved by the trade-compliance officer — prepared, never auto-filed.

Compliance AI

Validated before it ever touches production. Every agent is rehearsed in DemoForgi — golden scenarios, shadow mode, gated autonomy — on a synthetic twin of your enterprise.

Prove it before you deploy it →
Integration

Built to sit on the estate you already run

Read-first connectors for the systems semiconductor companies actually operate — no rip-and-replace, no migration project, no new system of record.

ERP & business

SAP S/4HANAOracle

MES

Camstar / OpcenterFactoryWorksCritical Manufacturing

PLM

TeamcenterWindchill

EDA & design ops

CadenceSynopsysSiemens EDALicense-server telemetry

Equipment

SECS/GEMOPC-UASEMI E10 states

Sensors & test

FDC streamsSTDF test dataPlant historians

Trade & logistics

ICEGATESEZ / bonded importsRosettaNet / EDI-856

Engineering & construction

Autodesk ACCProjectWisePrimavera P6
Automated fab floor with a patterned wafer in the foreground and a glowing map of global connections overhead
Fig. 03 — one fab, every system attached read-first · 8 connector families

Read-first. Writes only through named human approval gates.

We read everything and write nothing on our own. An approved action shows the named approver the exact connector payload, target system and before/after diff — then one audited writer executes it. Blocked stays blocked until named release.

Trust by design

Security & deployment, decided by you

Your premises or your VPC. Your region, your keys, your audit trail — and never a model trained on your data.

Deploys where you decide

SaaS · single-tenant VPC · on-prem · air-gapped · India sovereign cloud

Your region, your keys

Residency pinned per tenant · BYOK / HYOK · deletion by cryptographic erasure

Per-plant isolation

Tenant-siloed by construction — yield genealogy never pooled across customers

No training on your data

Zero cross-tenant model training — your data sharpens only your deployment

RBAC & named approvers

Every gate maps to a named role — shift lead · quality engineer · trade compliance

Audit by construction

One immutable entry per recommendation, approval and write — evidence attached, customer-audit ready

Scales with your ramp

Start with one plant and two decisions. Each addition lands in 60–90 days on the same data fabric and governance spine — autonomy earned per decision-type, never assumed.

34 products · one spine 60–90-day attach into live accounts shadow → propose → one-click → auto-with-sampling

Connectors land; the Decision Graph resolves suppliers, parts, lots and quals; agents shadow your team’s real decisions. Measured evidence by week 8.