Uchechi Ngonadi · RESEARCH JOURNAL OF PURE SCIENCE AND TECHNOLOGY 2026 · 2026
DOI: 10.56201/rjpst.vol.8.no8.2025.pg142.212
Counts differ because each database indexes a different set of publications. We treat OpenAlex as the canonical count; Google Scholar is not shown (no API, and crawling it violates its ToS).
Contract portfolios at large enterprises now routinely exceed tens of thousands of active agreements, and the regulatory obligations attaching to those agreements have multiplied faster than legal review capacity. In 2025 this gap became acute: the EU Digital Operational Resilience Act (DORA) became applicable on 17 January without a transition period, forcing thousands of financial entities into large-scale contract remediation, while the general-purpose AI obligations of the EU AI Act took effect on 2 August. Both events created demand for systems that can read an entire contract portfolio and flag, with evidence, where regulatory liability exists. This paper reviews the state of natural language processing for automated regulatory liability detection as of the end of 2025 and sets out a layered architecture for production deployment. Regulatory liability detection is distinguished here from the better-studied task of clause extraction, on the argument that the former is a normative verification problem requiring a rule base, an evidence retrieval mechanism, and an adjudication step, rather than a span-labelling problem. Four technical shifts that reshaped the field during 2025 are surveyed: the maturation of long-context models beyond the length of most commercial contracts, the emergence of legal-specific retrieval evaluation, the arrival of explicit reasoning models capable of rule-grounded justification, and the closing but still material gap between proprietary and open-weight models on clause-level risk identification. Evidence is also drawn from compliance analytics research in financial audit, cybersecurity governance, critical infrastructure protection, procurement, supply chain assurance, payments, pharmaceutical regulation, aviation safety oversight, and enterprise systems engineering, on the argument that the design problems in regulatory liability detection are not confined to legal NLP and that adjacent literatures have already resolved several of them. A metric suite appropriate to the asymmetric cost structure of compliance work is then set out, in which a missed mandatory clause is not commensurate with a false alarm, and the F1 scores dominant in the literature are argued to be a poor proxy for deployment value. The paper closes on a reflexive governance question specific to this application: a system that classifies legal risk may itself fall within the scope of the regulation it is deployed to manage.
No comments yet — start the discussion below.