← Latest papers
🤖 AI

Provably Auditable and Safe LLM Agents from Human-Authored Ontologies

This paper introduces Agentic Redux, a provably correct and auditable LLM agent architecture based on typed lambda calculus and human-authored ontologies, demonstrating its application in healthcare billing compliance and security vulnerability disclosure.

Original authors: Aaron Sterling

Published 2026-06-04
📖 5 min read🧠 Deep dive

Original authors: Aaron Sterling

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 running a very important, high-stakes operation, like a hospital billing department or a security team hunting for software bugs. You hire a team of super-smart AI assistants (LLMs) to help you. But there's a problem: these AIs are brilliant but unpredictable. They sometimes "hallucinate" (make things up), they don't always agree with each other, and if left to their own devices, they might accidentally break the rules of the universe you've built for them.

This paper introduces a new way to organize these AI assistants called Agentic Redux. Think of it not as a new AI, but as a new managerial structure that guarantees safety and creates a perfect, unchangeable record of every decision made.

Here is how it works, broken down into simple concepts:

1. The Problem: The "Write Skew" Disaster

Imagine two employees, Alice and Bob, are managing a shared budget of $100,000.

  • Alice sees she has $45,000 left and decides to spend it.
  • Bob sees he has $60,000 left and decides to spend it.
  • They both act at the same time, not knowing what the other is doing.
  • Result: The system spends $105,000. The budget is broken.

In computer science, this is called a "Write Skew." In the real world, this happens when AI agents act independently without seeing the full picture. Current solutions often just ask an AI, "Is this okay?" and hope it says yes. If the AI is having a bad day, it might say yes when it should say no, and the damage is done.

2. The Solution: The "Smart Container" (Agentic Redux)

The author proposes a structure inspired by a popular software design called Redux. Imagine a company where:

  • The Workers (Sub-agents): These are the AI assistants. They only see a tiny slice of the world (their "local state"). They can think, calculate, and propose actions, but they cannot change the world directly. They are like "dumb components."
  • The Manager (Meta-agent): This is a central decision-maker who sees the entire global state (the whole budget, all the rules, all the history).
  • The Process:
    1. A worker proposes an action (e.g., "Spend $45,000").
    2. The proposal goes to the Manager.
    3. The Manager checks the proposal against a list of Invariants (unbreakable rules, like "Total spending cannot exceed $100,000").
    4. If the rule holds, the Manager approves the change. If not, the Manager rejects it.
    5. The Manager updates the world and tells the workers what the new reality looks like.

The Magic: The paper proves mathematically (using a branch of logic called "typed lambda calculus") that as long as the Manager follows the rules, it is impossible for the system to break the rules, no matter how crazy or hallucinated the workers' proposals are. The architecture itself acts as a safety net.

3. The "Black Box" Ledger (Linear Auditability)

Every time the Manager makes a decision, they write it down in a special notebook.

  • If they say "Yes": They write down the new state and a proof that the rules were followed.
  • If they say "No": They write down the proposal, the reason for rejection, and which rule would have been broken.
  • The Rule: This notebook is append-only. You can add new pages, but you can never tear out or erase old ones.

This creates a "linear audit trail." If an auditor comes in later, they can look at the notebook and see, in perfect chronological order, exactly why every decision was made. They can verify that the system never broke the rules.

4. How to Build These Systems: "Ontology-First Design"

You can't just throw this architecture at any problem. You need to understand the problem deeply first. The author suggests a method called Ontology-First Agent Design:

  1. Map the Territory: A human expert uses a standard map-making tool (called Basic Formal Ontology) to draw a precise map of the problem world (e.g., "What is a patient? What is a drug test? What are the rules?").
  2. Assign Roles: An AI is asked to look at this map and suggest what "jobs" (roles) need to be done.
  3. Build the Team: The AI turns those jobs into code for the workers (sub-agents) and the Manager (meta-agent).

The paper tested this on two real-world problems:

  • Healthcare Billing: Ensuring insurance claims follow complex government rules about drug tests.
  • Security Vulnerabilities: Managing the process of finding and disclosing software bugs without causing panic or breaking laws.

In both cases, the system successfully prevented the "Write Skew" errors that would happen if the agents acted alone.

5. The Human Safety Valve (The Counselor Queue)

What if the rules are too complex for the Manager to decide, or a situation requires a human judgment call?
The system has a Counselor Queue. If the Manager gets stuck or encounters a situation where the rules say "Ask a human," the proposal is paused and put in a line for a human expert.

  • The human reviews the situation and makes a decision.
  • Crucially, even the human must write their decision into the same unchangeable notebook, explaining their choice.
  • The paper proves that even with humans in the loop, the system remains auditable and safe, provided the humans follow the format.

Summary

This paper doesn't claim to make AI smarter. Instead, it claims to make AI safer and more trustworthy by putting them in a cage with a very strict manager.

  • The AI does the thinking and proposing.
  • The Architecture (the Manager) does the checking and enforcing.
  • The Ledger records everything forever.

The result is a system where you can mathematically prove that "bad things" (like breaking the budget or violating regulations) cannot happen by accident, and if a human has to step in, their decision is recorded with total transparency.

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 →