WENGOLD

Verification that compounds, in the open.

WENGOLD keeps every verification result that still holds after a change, and reruns only what the change could have touched. The graph, the validity kernel and the ledger are open — dual-licensed MIT or Apache-2.0.

After every change: which of my previous results still hold? Valid, invalidated, or unknown — never assumed.
Deck

Pitch deck

Thirteen slides: the problem, the system, the market and the model.

Specification

Architecture spec

The graph, the validity kernel and the ledger, in full.

Strategy

Open-core model

The market, the boundary between open core and enterprise, and the risks.

Code

Repository

The kernel, graph, ledger, agents and MCP server — with 583 tests, a SystemVerilog front-end, and CI that runs both on every push.

Evidence

30 repositories measured

Every project the tool has been run against, with the numbers and the reason for each gap — OpenPiton at 891 blocks, frost at 98% coverage, riscduino's 169 unresolved nodes and why.

Editor

VS Code and Cursor

The graph, the unresolved nodes and the singular configurations in the sidebar, with a squiggle on the line that instantiates something missing.

What it does not do. The formal front-end accepts 11 of 27 files on a modern UVM project and refuses the rest rather than guessing — `ifdef, generate and multiple clock domains are out of scope. The CDC work reads and writes the Accellera format; it does not decide whether a crossing is safe. Every number on this site can be reproduced from the repository.

Install

git clone https://github.com/thejas235689/wengold.git
cd wengold
python -m pip install -e ".[open]"
python -m wengold.demo