← Latest papers
🤖 AI

Citation-Closure Retrieval and Per-Rule Attribution for Real-World Regulatory Compliance Question Answering

This paper introduces RefWalk, a unified framework designed to enhance regulatory compliance question answering by enforcing per-rule attribution and structured procedural lookups, validated through the novel RegOps-Bench benchmark and a U.S. health compliance dataset.

Original authors: Yeong-Joon Ju, Seong-Whan Lee

Published 2026-05-29
📖 5 min read🧠 Deep dive

Original authors: Yeong-Joon Ju, Seong-Whan Lee

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.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 navigate a massive, multi-story library where the books don't just sit on shelves; they are chained together by invisible threads. If you pick up a book on "How to Build a Bridge," it might have a note saying, "See Chapter 4 of the 'Safety Rules' book," which in turn points to a specific paragraph in the "City Permit" book, which finally references a tiny footnote in a "Construction Manual."

This is what Regulatory Compliance feels like for companies. They have to follow strict, layered rules (laws, decrees, manuals) that constantly refer to each other. If they get it wrong, they face huge fines.

The paper argues that current AI tools (Large Language Models) are terrible at this specific job. They are like a student who reads the first book, guesses the answer, and then makes up a fake page number to cite as proof. They are fast, but they are dangerous because they "hallucinate" (lie) about where the rules come from.

Here is the paper's solution, broken down into simple concepts:

1. The Problem: The "Flat" Map vs. The "3D" Maze

Most AI systems treat the library like a flat list. They see the words "bridge" and "safety" and think, "Okay, these two things are related." They miss the structure.

  • The Reality: In law, a rule doesn't just "relate" to another; it delegates to it. One rule says, "Do X, unless the Safety Decree says Y."
  • The Failure: Current AI tries to find the answer by looking for similar words. It misses the specific "threads" connecting the rules. It also treats the final answer and the citation as two separate things, often tacking a fake citation onto the end of a sentence after the fact.

2. The New Tool: "RefWalk" (The Guided Tour)

The authors built a new system called RefWalk. Think of it as a super-organized tour guide who doesn't just read the books but physically walks the threads connecting them.

  • The "Topic Anchor": When you ask a question (e.g., "Can I spend extra money on overseas research?"), RefWalk doesn't just search for the words. It breaks the question down into a "map key": Who is asking? How much money? When? Under what situation?
  • The "Three-View" Search: Instead of looking for the answer in just one way, the guide looks at the library from three angles:
    1. The Narrow View: Looking for the exact words you used.
    2. The Wide View: Looking for the general concept, ignoring the specific words (in case you phrased it weirdly).
    3. The Middle View: A mix of both.
    • Why? Sometimes the exact words lead you to the wrong book, but the general idea leads you to the right one. RefWalk uses a special "voting system" (called RRM) that picks the best result from any of the three views, rather than averaging them out (which would dilute the correct answer).

3. The "Knowledge Graph" (The Thread Map)

The paper created a special map of the library called the Operational Knowledge Graph (OKG).

  • Instead of just linking books by topic, this map links them by legal logic. It knows that "Rule A" delegates to "Rule B," and "Rule B" defines "Rule C."
  • RefWalk follows these threads. If you ask about a budget, it starts at the budget rule, follows the thread to the safety rule, then to the manual, ensuring it doesn't miss a single link in the chain.

4. The "Strict JSON" (The No-Lying Rule)

This is the most important part. In normal AI, the model writes a paragraph and then tries to add a citation at the end. It's like writing an essay and then making up a footnote to look smart.

  • RefWalk's Approach: The AI is forced to wear a "straitjacket" (a strict JSON format). It cannot write a sentence until it has first selected the specific rule (the "Key") and then written the claim as a "Value" attached to that rule.
  • The Metaphor: Imagine a courtroom where a lawyer cannot speak a word unless they are holding the specific page of the law they are quoting. They can't say, "The law says X," and then later say, "Oh, by the way, that's from page 42." They must say, "Page 42 says X." This forces the AI to be honest. If it can't find the page, it can't make the claim.

5. The Test: "RegOps-Bench"

To prove this works, the authors built a new test called RegOps-Bench.

  • They took real, complex Korean government regulations (which are famously complicated and layered).
  • They created 250 difficult questions that required following multiple "threads" across different books.
  • The Result: Old AI systems got stuck or gave fake citations. RefWalk successfully followed the threads, found the exact pages, and attached the answers to the correct rules. It was much better at finding all the necessary rules (recall) and making sure the citations were real (precision).

Summary

The paper says: "AI is great at chatting, but bad at following strict legal chains."
They built RefWalk, a system that:

  1. Maps the threads between rules (not just the words).
  2. Searches from three angles to make sure it doesn't miss anything.
  3. Forces the AI to cite before it speaks, ensuring every claim is glued to its source.

This makes AI safe enough to use for high-stakes jobs like checking if a company is following the law, where a fake citation could lead to a lawsuit.

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 →