Build and reuse AI-assisted chip-verification workflows

What the source reports

OpenAI’s FDE account describes engineers embedding with a semiconductor verification team to build directed-test generation, debugging and architecture assistance, with customer engineers helping define evaluations. It later describes moving custom applications onto shared Codex harnesses, plugins and skills, while adapting connectors and evaluations for additional teams.

Reported technology: OpenAI Forward Deployed Engineering and Codex. Scope and outcomes are source-reported.

What the enterprise environment would need

The following is a proposed project design for an enterprise doing similar work. Published details are marked; the remaining systems, data and scenarios would be agreed for your project.

Systems and tools

Published: custom harnesses evolved into shared Codex-based plugins and skills. Proposed: connect only the agreed test-design, repository and simulation tools in a licensed engineering environment.

Data and state

Proposed: use an approved design subset, specifications, testbench and seeded failures with known expected behavior; retain their versions.

People and handoffs

Published: FDEs worked with customer verification engineers on evaluations. Proposed: domain engineers review generated tests and diagnoses before accepting changes.

Rules and authority

Proposed: restrict design and repository access; generated tests cannot redefine the expected behavior or authorize a production change.

Normal and exception cases

Proposed: include a real design defect, an incorrect test expectation, ambiguous specification and a failure that cannot be reproduced.

Reset and replay

Proposed: rerun held-out cases after harness, skill, model or connector changes; verify adaptation to another team rather than assuming transfer.

A proposed simulation

An illustrative practice design derived from this work, not an executed assessment.

Build a bounded verification assistant, demonstrate useful tests and supported diagnoses, then adapt it to a second approved design context.

Review gate: Independently verify test effectiveness, diagnosis support and tool authority, preserving domain-engineer acceptance.

Challenge the result: Allow a generated test to encode the same wrong assumption as the agent’s diagnosis. A separate reference and seeded defect must expose the shared error.

What needs checking

• Proposed: domain experts qualify expected behavior independently of the generating agent and check that tests expose known defects.
• Proposed: reproduce diagnoses and rerun unchanged regression checks before accepting a proposed repair.
• Proposed: record integration, expert review and correction effort when reusing the harness on another team.

Review environment fidelity, human capability and agent performance separately. The enterprise’s accountable owners decide acceptance of the shared workflow and any operating use.

Shape this around your enterprise

Bring a similar workflow and the people responsible for it. Together, define the records and systems to use, the result your team will build or configure, and how its owners will check it. Nuvepro scopes the simulation, environment and preparation. Agree any existing-agent evaluation, implementation assistance and production responsibilities separately.

Sources and limitations

Curation review: 23 October 2026. This is the date this source example was reviewed, separate from source publication dates.

• The customer is unnamed and the account is provider-reported. It does not publish full evaluation data or independently audited business results. The 22 October publication describes earlier engagements; reported reuse and deployment timelines are not promises for another enterprise.

1. OpenAI: What FDE means at OpenAISource publication: 2026-10-22