WENGOLD keeps every verification result that still holds after a change, and reruns only what the change could have touched.
Building a chip takes hundreds of engineers and years of work, and most of that effort goes into proving the design is right. On a leading-edge program that share is now the single biggest item, and it is heading higher.
| Verdict | When | What happens |
|---|---|---|
| valid | No certain dependency on the change | Keep it, with its evidence |
| invalidated | Depends on, or is reached by, the change | Rerun it |
| unknown | Reachable only across an uncertain dependency | Re-establish; never assume |
Where the graph cannot resolve a dependency, the kernel returns unknown rather than a false pass — the safe direction.
| Player | What they do | The gap |
|---|---|---|
| Synopsys · Cadence · Siemens EDA | Full EDA suites | Sell speed, not fewer runs |
| Closed AI-verification startups | Autonomous agents, closed source | Closed, and on commercial tools |
| Open agent projects | CoreSmith, UCAgent, VeriPower, xverif | Do a task, not the program layer |
| Open EDA toolchain | Verilator, Yosys, SymbiYosys, cocotb | Complementary — no validity kernel |
The moat is the kernel and the graph behind it. A competitor can wrap a model around a tool in a weekend; a graph of the whole design that survives every revision is the compounding part.
The kernel stays open. Scale, air-gap and support are the business.