llm-eval-ci-gate-rtl-verilog
Dual-tool CI evaluation gate for LLM-generated RTL: static analysis and simulation must agree.
What it does and how it connects
Quorum is a dual-tool CI evaluation gate for LLM-generated RTL, built in Python, Docker and GitHub Actions. Its rule is that no result counts on one witness: for anything a tool can check, two structurally different tools must agree, and for anything only a human can check, two independent reviewers apply the same written rubric, with the agreement rate itself measured rather than assumed. The gate runs static analysis and simulation, with golden sets, tool-grounded scoring, pre-registered pass bars, and CI quality gates on prompt, model and retrieval changes.
Measured results are the point of the repo: 27 single-defect mutants seeded into six known-good reference modules, run through both lanes. The gate passes 6 of 6 known-good modules (no false positives), kills 22 of 27 mutants (81.5 percent), and the lane breakdown is the thesis: 19 mutants were caught by the dynamic lane (Icarus) only, 1 by the static lane (Yosys) only, 2 by both, and 5 survived both, all five being equivalent mutants. A static-only gate would have shipped all 19 dynamic-only catches.
Alternatives
Compare side by side- veriflow-rtl-benchmark
A five-design golden-model harness for AI-written Verilog, rather than a dual-tool CI gate with measured kill rates.
- llm-verilog-reliability-eval
A 30-question graded bank with self-checking testbenches and a repair loop, rather than a dual-tool gate.
- fail2bench
Turns agentic hardware design failures into new benchmark items, rather than gating LLM-generated RTL in CI.
- specread
Tests whether models comprehend hardware specifications, rather than gating their generated RTL.
- cad-mcp-cleanroom
Audits whether a CAD MCP command surface is deterministic and honestly read-only, rather than gating RTL in CI.
Sources
Not verified
- Pricing: none stated on the repo.
- Real user voices: no real linked post read for this page; the repo has no public issues.
- No GitHub releases exist, so latest release fields are null.
- Activity: last push 2026-08-27, so the project looks quiet.
Last verified November 6, 2026. Listings are informational. The evidence score measures public, verifiable evidence and is not an endorsement or a compatibility claim.