arXiv AI

Code-as-Auditor: Executable Compliance Reasoning via Regulation-to-Code

Code-as-Auditor is an LLM-based framework that transforms regulatory information into formal checklists and executable decision trees, encoding rules as interpretable code. During inference, the model expands each checklist item into factual and counterfactual questions, guiding reasoning over case-specific evidence and potential violations. This pipeline moves from evidence identification to rule application and final decision-making, with a self‑verification loop that enhances logical consistency and traceability, leading to more accurate and evidence‑backed compliance evaluations in privacy and data protection scenarios.

arXiv AI
Jul 7

From Regulation to Requirements: An Automated Requirement Derivation and Explanation Pipeline

arXiv:2607. 04448v1 Announce Type: cross Abstract: Ensuring software compliance with regulations such as the General Data Protection Regulation (GDPR) and the Artificial Intelligence Act (EU AI Act) poses a significant challenge, as requirements engineers must translate complex legal text into actionable software requirements - a process that remains largely manual and error-prone in practice.

By Pavithra PM Nair, Preethu Rose Anish
Hugging Face Trending Papers
5d ago

A decision-support system applied to Law: Reasoning and explainability of the decision

The paper presents a decision‑support framework for Law Enforcement Agencies that formalises EU regulations such as the Law Enforcement Directive and uses symbolic AI with SPARQL to reason over legal rules. It includes an algorithm that generates justifications for its conclusions and a decision‑tree method to identify additional information needed when reasoning is inconclusive. The framework emphasizes explainability to build user confidence in automated legal decisions.

Hugging Face Trending Papers
Aug 3

CTRAG: An In-Context Retrieval-based Framework for Automated Compliance Checking using LLMs

Trust is fundamental in modern regulatory ecosystems, and compliance checking plays a critical role in fostering that trust. Regulatory compliance verification is essential for businesses operating in highly controlled environments, as it ensures alignment with sector-specific guidelines across domains such as financial reporting, data privacy, and cybersecurity.

arXiv AI
Jun 6

PSEBench: A Controllable and Verifiable Benchmark for Evaluating LLMs in Patient Safety Event Triage

arXiv:2606. 05463v1 Announce Type: new Abstract: Patient safety event triage, determining whether a clinical event is reportable under jurisdiction-specific policy, is a high-stakes task typically performed manually by patient safety experts.

By Keqi Han, Ryan Young, Annabel Strauss, Lindsey Hughes, Katharine M. Nesbitt, Nicole Schueler, Che Ngufor, Carl Yang, Yuan Xue, Zhijun Yin
arXiv AI
Sep 18

Governance-as-Code: Translating EU AI Act Technical Requirements into Executable Compliance Pipelines for Generative AI Systems

The paper introduces Governance-as-Code (GaC), a framework that translates the EU AI Act’s technical requirements into 43 machine‑checkable acceptance criteria across six compliance modules. GaC runs within a CI/CD pipeline, producing Article‑indexed audit evidence and providing actual Rego policy code. The authors validate GaC on two enterprise deployments, showing it reproduces manual audit findings—including three penalty‑triggering violations—while reducing audit labor by about 75%.

By Rudrendu Kumar Paul, Sourav Nandy
arXiv Computation and Language
Sep 22

SoK: Formal Methods for Fact-Checking and Information Integrity

The paper "SoK: Formal Methods for Fact-Checking and Information Integrity" discusses how automated fact‑checking systems typically output a verdict but lack a detailed record—called a warrant—explaining the evidence and conditions behind that verdict. It proposes organizing the field by what is being formalised—claims, reasoning, checking systems, ecosystems, and regulatory obligations—rather than by pipeline stages, and surveys 121 works to identify gaps, notably the scarcity of formal methods applied to verifying the checking systems themselves. The authors highlight that existing formal tools, though largely unused in this domain, could address these gaps and outline open problems with suggested first steps.

By Nikolaos Kekatos, Theodoros Nestoridis, Charalampos Bratsas, Charalampos Dimoulas, Georgios Konstantinidis, Georgios Malogiannis, Michael Sirivianos, Andreas Veglis