← Latest papers
🤖 AI

Knowledge Graphs, the Missing Link in Agentic AI-based Formal Verification

This paper proposes a verification-centric Knowledge Graph that integrates structured intermediate representations from specifications, RTL, and formal tool feedback to guide a multi-agent workflow, significantly improving the grounding, compilability, and coverage of LLM-generated SystemVerilog Assertions for formal verification.

Original authors: Vaisakh Naduvodi Viswambharan, Keerthan Kopparam Radhakrishna, Deepak Narayan Gadde, Aman Kumar

Published 2026-05-08
📖 4 min read☕ Coffee break read

Original authors: Vaisakh Naduvodi Viswambharan, Keerthan Kopparam Radhakrishna, Deepak Narayan Gadde, Aman Kumar

Original paper dedicated to the public domain under CC0 1.0 (http://creativecommons.org/publicdomain/zero/1.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are trying to build a massive, incredibly complex LEGO castle based on a written instruction manual. The manual is written in plain English, but the castle is built with thousands of tiny, specific bricks (the hardware design).

The Problem:
In the world of chip design, engineers use "Formal Verification" to mathematically prove the castle won't collapse. To do this, they write a set of strict rules called SystemVerilog Assertions (SVAs). These rules say things like, "If the red button is pressed, the blue door must open within 3 seconds."

Traditionally, writing these rules is a nightmare. It requires a human to read the messy English manual, look at the complex LEGO structure, and translate it into perfect, error-free code. If the manual is vague or the human misses a tiny detail about a specific brick, the rule fails, and the whole verification process crashes.

Recently, Artificial Intelligence (AI) has been used to write these rules automatically. But the AI often gets confused. It reads the manual but doesn't "see" the LEGO bricks, leading to rules that are grammatically wrong or make no sense for the actual design.

The Solution: A "Digital Librarian" (The Knowledge Graph)
This paper proposes a new way to help the AI. Instead of just letting the AI read the manual and guess, the authors built a Knowledge Graph (KG).

Think of the Knowledge Graph as a super-organized digital librarian that connects three things:

  1. The Instructions: The original English requirements.
  2. The Blueprint: The actual hardware design (the LEGO bricks).
  3. The Feedback: The results from the verification tools (e.g., "This rule failed because the door didn't open fast enough").

The librarian doesn't just store these as separate piles of paper. It creates a web of connections. If you ask the librarian about a specific rule, it instantly pulls up the exact sentence from the manual, the specific brick it refers to, and any previous errors that happened with similar rules.

How the Team Works (The Multi-Agent Workflow)
The authors didn't just build the librarian; they hired a team of specialized AI "agents" to work with it. Imagine a construction crew where everyone has a specific job:

  1. The Architect (Property Generation): This agent looks at the manual and the librarian's connections to write the initial rules. Because the librarian provides the exact context, the rules are much more likely to be correct from the start.
  2. The Grammar Police (Syntax Correction): If the rules have typos or coding errors, this agent fixes them. It uses the librarian to check if a "missing brick" is actually a missing definition in the code.
  3. The Detective (CEX Correction): Sometimes a rule fails because the design is actually broken, or the rule was too strict. This agent looks at the "crime scene" (the error report), checks the blueprint, and rewrites the rule to be fairer or fixes the misunderstanding.
  4. The Inspector (Coverage Improvement): This agent checks if there are any parts of the castle that haven't been tested yet. If so, it asks the librarian for new rules to test those specific areas.

The Results
The team tested this system on seven different "castles" (chip designs), ranging from simple counters to complex memory systems.

  • Success: The system consistently produced rules that the computer could actually read and run (compilable code). It drastically reduced the number of "typos" and basic errors.
  • Coverage: The system managed to verify between 78.5% and 99.4% of the design's behavior, which is a very high success rate.
  • The Limit: While the system is great at fixing small errors and connecting dots, it still struggles with the hardest puzzles. If a rule requires complex, long-term logic (like "if this happens today, it must affect that event three days from now"), the AI sometimes gets stuck, even with the librarian's help.

In Summary
This paper introduces a system where AI doesn't just guess how to verify computer chips. Instead, it uses a structured map (Knowledge Graph) to link the written requirements directly to the hardware design and the test results. This allows a team of AI specialists to write, fix, and improve verification rules much more reliably than before, turning a chaotic guessing game into a structured, traceable process.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →