The Expert Systems are a rule-based (CLIPS) judge for the violations that CDC, RDC and Lint tools report. For every violation they answer FIX_RTL, WAIVE, FIX_CONSTRAINT or NEEDS_REVIEW, with the rule that fired and the derivation behind it. They sit next to the Advisor agents of the EDAUtils AI SDK: the Advisor reasons with an LLM over the report text, the Expert System decides from the elaborated design, the SDC, the designer's intent file and the company methodology.
One engine, three domains
- CDC - unsynchronized crossings, multi-bit buses, reset crossings and gated clocks. Approved synchronizer cells are regular expressions in the methodology file.
- RDC - adds destination-without-reset and reset-driven-output checks.
- Lint - latches, combinational loops, multi-driven and undriven nets, unconnected ports and constant flops. Functional classes are never waivable by default.
How it decides
design RTL --yosys--> design model (built once: per-flop cones, enables, chains, origins) SDC + intent.csv + methodology/company.json
| | |
tool report --> violations --> facts per violation (read from the model) --> CLIPS rules (domain pack)
|
FIX_RTL | WAIVE (needs a reference) | FIX_CONSTRAINT | NEEDS_REVIEW + derivation
Every derivation lists the reported violation, the methodology class and whether it is waivable, the setup problems found first (undefined clock, no relation, constant source, intent that conflicts with the SDC), the evidence with its source, the rule that fired and the higher-priority rules that did not apply.
A WAIVE needs all three: technical evidence from the design, the designer's attestation in the intent file, and a methodology policy that allows waiving that class. Heuristics reach NEEDS_REVIEW only, and the answer names the fact that is missing. A set_false_path or set_input_delay is never accepted as a synchronizer.
Unified result with the Advisor
The FECAD Lead, and the helpers/expert_analyze.py script with or without the FECAD flow, run the Advisor and the Expert System in parallel and color every violation:
- GREEN - both recommend the same action.
- YELLOW - they differ without contradicting each other, or only one side answered.
- RED - one says WAIVE and the other says fix.
Skip a side with the prompt ("expert system only", "skip the advisor") or with expert_systems: {advisor, expert} in eu_config.yaml. The per-domain <domain>.unified.html is a detail table with two rows per violation, the Advisor's and the Expert System's recommendation and analysis.
Inputs
- Elaborated RTL (Verilog and SystemVerilog through Yosys), the SDC, an
intent.csvof designer attestations and the company methodology as data (methodology/company.json); swap the methodology with--methodologywithout editing a rule. - A native analysis report, or a Synopsys VC CDC, VC SpyGlass Lint or VC RDC report, or a Questa CDC or RDC report (
--format auto|native|vc_cdc|questa_cdcand the lint and RDC variants). The vendor layouts follow the published formats and are not yet verified against real vendor reports. --model-cache DIRelaborates once and reuses the design model for CDC, RDC and Lint;--jobs Nruns violations in parallel.
Install
With the AI SDK: the SDK installer builds the Expert Systems environment (its own virtual environment with clipspy, kept out of every Lead's Python) and installs Yosys in the tools directory. Nothing else to do.
Independent bundle edautils-expert-systems-<version>.tar.gz, no SDK and no FECAD flow needed:
tar xzf edautils-expert-systems-<version>.tar.gz
cd edautils-expert-systems-*/
./install.sh # local: everything under ~/edautils-expert-systems (Python venv and yosys)
sudo ./install.sh --system # /opt/edautils-expert-systems, OS packages, launchers in /usr/local/bin
Air-gapped sites use --wheelhouse DIR --tools-from DIR.
License
The Expert Systems are a licensed feature, expert-systems. The EDAUtils AI SDK license (features * or one that lists expert-systems) covers it; the independent bundle ships with its own EDAUTILS-EXPERT-SYSTEMS license. The license file is searched in this order: --license FILE, EDAUTILS_LICENSE_FILE (a colon-separated list), then edautils_license.json in the SDK root or the install directory. Without a valid license the tools exit with code 3 and name each refused file. For evaluation or purchase write to sales@edautils.com.
Examples and tests
The scenario suites cover CDC, RDC and Lint, vendor formats and real IP blocks, and the dual runs (Advisor and Expert System, Advisor only, Expert System only); each scenario has an expected result that the SDK test suite checks. Every rule of the current build fires in at least one scenario.
Frequently asked questions
Related
- EDAUtils AI SDK - the agent fleet the Expert Systems plug into
- FECAD reference flows - the static-check flows whose reports it judges
- AI for VS Code and Cursor