← Latest papers
💻 computer science

Right-to-Act: A Pre-Execution Non-Compensatory Decision Protocol for AI Systems

This paper introduces the "Right-to-Act" protocol, a deterministic, non-compensatory pre-execution framework that halts AI actions if any safety condition is unmet, thereby shifting the focus from optimizing decision quality to strictly governing the admissibility of execution.

Original authors: Gadi Lavi

Published 2026-04-28
📖 4 min read☕ Coffee break read

Original authors: Gadi Lavi

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 have a very smart, fast robot assistant. This robot can do things like send money, lock people out of their accounts, or change the settings on a factory machine. Right now, we have a lot of rules to make sure this robot is safe:

  • Authorization: "Is this robot allowed to touch the machine?"
  • Safety: "Will this action hurt anyone?"
  • Risk Scoring: "On a scale of 1 to 100, how risky is this?"

The paper argues that even if the robot passes all these tests, there is still a missing step. The robot might be allowed, safe, and low-risk, but it might still be wrong to do the action right now because it's missing a crucial piece of the puzzle.

The author calls this missing step the "Pre-Action Legitimacy Gap."

The Core Problem: The "Score" vs. The "Checklist"

To understand the gap, imagine two ways a teacher might grade a student's project:

1. The Compensatory System (How we do it now):
This is like a point-based game.

  • The student gets 10 points for a great design.
  • They get 10 points for good research.
  • They get 10 points for a nice presentation.
  • But, they forgot to include the title page (a missing requirement).
  • The Result: Because they have 30 points total, and the passing grade is 20, the teacher gives them an A. The missing title page is "compensated for" by the other good parts.

2. The Non-Compensatory System (The "Right-to-Act" proposed in the paper):
This is like a security checkpoint with a strict checklist.

  • You have a ticket? Yes.
  • You have a passport? Yes.
  • You have a visa? No.
  • The Result: It doesn't matter if you have a golden ticket, a beautiful passport, and a friendly smile. If you are missing the visa, you cannot enter. No amount of "good points" can fix the missing visa.

The paper argues that for AI making real-world decisions (like locking an account or moving money), we need the Checklist approach, not the Point System.

The "Right-to-Act" Protocol

The author proposes a new rule called the "Right-to-Act."

Think of it as a bouncer at a club who doesn't care how much money you have (your score) or how nice you look (your safety rating). The bouncer only asks: "Do you have the specific key required to open this specific door?"

  • If the AI says, "I want to lock this user's account," the system checks: "Do we have proof that this user actually broke the rules, or is it just a guess?"
  • If the proof is missing, the system says "NO."
  • It doesn't say, "Well, the guess is 90% confident, so let's do it anyway."
  • Instead, it says, "Stop. We don't have the key. Go get more info or ask a human."

Why This Matters (The Account Suspension Example)

The paper uses a real-world example: An AI deciding to ban a user from a website.

  • The Old Way: The AI sees the user acted suspiciously 5 times, looks like a known hacker, and the AI is 95% sure it's a hacker. The "Risk Score" is high. Result: The user gets banned immediately.
  • The Problem: What if the user was just using a shared computer that was hacked? The AI was "right" about the suspicious activity, but "wrong" about who did it. The AI missed a required condition: "Verify the user's identity."
  • The New Way (Right-to-Act): The system checks the checklist.
    • Suspicious activity? Yes.
    • High confidence? Yes.
    • Identity verified? No.
    • Result: The system stops. It does not ban the user. Instead, it says, "I can't do this yet. I need to ask the user for more info."

The Big Takeaway

The paper proves mathematically that you cannot fix this problem just by making the "Risk Score" higher or the "Safety" better. If you use a scoring system, a high score will always be able to cover up a missing requirement.

Legitimacy is not a score; it is a boundary.

The paper suggests that before an AI is allowed to "pull the trigger" on any real-world action, it must pass a strict, non-negotiable checklist. If even one required condition is missing, the action is blocked, no matter how "smart" or "confident" the AI is. This turns "doing nothing" (waiting, asking for help, or escalating to a human) into a valid and necessary outcome, rather than a system failure.

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 →