SV-Gap now has a najaeda-based structural backend

[xtofalex]

SV-Gap is an open evaluation layer for AI-generated RTL: it takes a functional benchmark result, adds declared design intent for clock-domain crossing (CDC), reset-domain crossing (RDC), and power-on state, and reports structural evidence: pass/fail/unknown/tool_error, that a verification team can actually review.

As of PR #21, it ships a second structural backend, reference-naja, built on najaeda:

• Runs entirely in-process against from najaeda import naja: no external binary, just pip install "svgap[naja]".
• Implements the same rule set behind an identical result/schema contract.
• Opt-in (the default is unchanged) switched per manifest with one field.
• Benefits from najaeda's bundled slang frontend, which covers some SystemVerilog constructs the original backend's frontend doesn't parse (e.g. an explicit return inside a function).

Posting here so anyone landing on Naja looking for RTL verification tooling, or on SV-Gap looking for najaeda details, has a direct path between the two.
Happy to answer questions about the backend or the najaeda side of it.

[shsridhar-beep]

Thank you for opening this, Christophe. From the SV-Gap side: the backend is merged and ships as the optional naja extra (pip install "svgap[naja]"), and the two oracles agree 72 of 72, rule for rule, on the frozen reset-release corpus, with the claim boundary stated next to the result. The link now runs both ways at the source level: SV-Gap's backend page points here, and the cross-oracle result carries the full method.

For najaeda users curious what the contract asks of a backend, the backend SDK page documents it, and the registry accepts conforming evidence from any engine; the first external submissions merged this morning, so the pipeline is demonstrably open. Looking forward to the STA exploration. Timing intent is a natural next field for the contract, and the RFC would welcome that perspective: shsridhar-beep/svgap#20