Let AI help build the hardware. Keep every release under a named engineer you can replay.
A hardware release is high-stakes and often irreversible: one un-checked tapeout burns a mask set, one un-reviewed firmware OTA bricks a fleet, one silent BOM swap voids a compliance declaration. Electronics OEMs and semiconductor teams are putting AI agents to work across the lifecycle — drafting layouts, screening parts for obsolescence, staging firmware, recommending a release. KYE Hardware & Electronics Engineering Authority Console™ sits between the AI and the engineering toolchain and decides, at the moment of each action, whether that AI-assisted action may proceed, under whose authority, and with what evidence on the record.
A governed authority layer for AI across the hardware lifecycle.
- Action admissibility. Every consequential AI-assisted action — release a PCB to fab, approve a tapeout, push a firmware OTA, approve a component substitution, change the BOM, declare EMC/FCC/CE compliance, release to manufacturing — is admitted only when a decision is recorded: which agent, which action, the intended effect, and the authority under which it proceeds. No recorded authority, no action.
- Sign-off and evidence binding. A release-to-fab or tapeout binds to the recorded design-review sign-off for the exact revision; a compliance declaration binds to the recorded test-evidence record for the matching hardware revision; a component substitution binds to an approved equivalence record. The console refuses an action that references no bound sign-off — an AI agent may not release a revision that has not passed the recorded review, nor declare conformity without cited measurement evidence.
- Named-engineer finality. An AI-assisted firmware OTA release stays advisory until a named, accountable release engineer records sign-off. The accountability for pushing software to fielded hardware is personal and named — it never transfers to the AI.
- Recall-defensible replay. Every governed action carries its bound chain (action record / design-review or test-evidence / authority decision / decision map) and an ed25519 signature against the team’s published keys, so a field recall or an engineering-change dispute can be answered by replaying exactly what was released and under whose authority — offline, from public keys alone.
Honest scope: KYE™ governs the AI’s authority and evidence, not the layout tool.
KYE™ does not do EDA/CAD layout, design-rule checking, physical test, or RF/EMC measurement — those stay with your engineering toolchain and your accredited test lab. KYE™ sits above the toolchain. What KYE™ does is govern the moment an AI agent acts: whether the action is admissible, under whose authority, bound to which sign-off or test evidence, and with what record on the file. That maps cleanly to the AI-governance and functional-safety duties your engineering oversight already sets — the EU AI Act (human oversight, record-keeping, deployer obligations), the NIST AI Risk Management Framework (accountability, documentation), and IEC 61508 (functional-safety decision accountability, documentation of safety decisions, verification of contestable outcomes). Each is a governed authority-and-evidence boundary, never a claim that KYE™ makes the engineering decision for you. Authority finality, not the layout tool.
Pick the tier that fits your engineering function.
Solo
For a single engineering team. One product line on synthetic data, four-week engagement, the full action-admissibility and named-engineer finality boundary.
- Action admissibility across the release lifecycle
- Resolved authority on every consequential action
- Single-team workspace, synthetic / anonymised data only
- Signed end-of-pilot evidence pack
Practice
For an electronics OEM or engineering function. Multiple product lines, multi-user roles, design-review sign-off binding on every release-to-fab and tapeout, six-week engagement.
- Multiple product lines and action types
- Release-engineer / firmware-lead / change-control / read-only-auditor roles
- Design-review sign-off binding required before any release or tapeout
- Signed end-of-pilot evidence pack
Network
For a large OEM, semiconductor design house, or multi-site engineering network. Full lifecycle including compliance test-evidence binding, named firmware-OTA finality, recall-replay readiness, audit-firm integration, ten-week engagement.
- All action types across every participating site
- Compliance declarations bound to recorded test evidence
- Firmware OTA releases gated behind named-engineer finality
- Recall determinations bound to a replayable release chain, with independent audit-firm sampling
Pilot fees credit one hundred per cent against the first-year annual licence when signed within sixty days of pilot close-out.
Release engineers, firmware leads, change-control officers, and compliance owners.
- Release engineer. You own the release to fab, the tapeout, the release to manufacturing. KYE™ makes the rule explicit and computes whether each AI-assisted action is admissible — so the AI helps without quietly releasing a revision that has not passed design review.
- Firmware lead. You own what ships to fielded devices. KYE™ keeps every AI-assisted OTA release advisory until you record finality, and binds the build to a recorded rollout plan before any push.
- Change-control officer. You own substitutions, BOM changes, and compliance declarations. KYE™ binds every substitution to an approved equivalence record and every declaration to recorded test evidence.
- Compliance owner. You answer to oversight and to recall investigators. KYE™ gives every AI-assisted action a recorded authority decision and a replayable evidence pack in one queue.