← Latest papers
💻 computer science

The Varieties of Ought-Implies-Can and Deontic STIT Logic

This paper presents a modular framework and sound, complete sequent calculi for deontic STIT logic that formalizes, compares, and analyzes the logical relationships among ten distinct interpretations of the Ought-implies-Can principle.

Original authors: Kees van Berkel, Tim S. Lyon

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

Original authors: Kees van Berkel, Tim S. Lyon

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 the captain of a ship. You have a map (your duties) and a compass (your choices). The ancient philosophical rule "Ought-implies-Can" (OiC) is like a safety check on your map. It says: "You can only be ordered to sail to a place if your ship is actually capable of getting there." You can't be blamed for not flying to the moon if you don't have a rocket.

However, philosophers have been arguing for centuries about exactly how strict this rule should be. Does "can" mean "physically possible"? Does it mean "I have the muscle to do it"? Or does it mean "I have the freedom to choose not to do it"?

This paper by Kees van Berkel and Tim Lyon is like a universal translator and a giant logic puzzle designed to sort out these ten different arguments. They take the messy, abstract debates of philosophy and translate them into a precise, mathematical language called STIT Logic (Seeing To It That).

Here is the breakdown of their work using simple analogies:

1. The Problem: The "Can" is Too Vague

The authors start by saying that the phrase "Ought implies Can" is like a Swiss Army knife with ten different blades. Some people use the "screwdriver" blade (logical possibility), while others use the "bottle opener" blade (physical ability).

They identified 10 distinct versions of this rule, ranging from very weak to very strong:

  • The "Dreamer" (Weak): "You ought to do X" implies "X isn't a logical contradiction." (e.g., You can't be ordered to make a square circle).
  • The "Realist" (Medium): "You ought to do X" implies "X is actually possible right now." (e.g., You can't be ordered to open a window if you are tied to a chair).
  • The "Agent" (Strong): "You ought to do X" implies "You have the specific ability to choose X."
  • The "Rebel" (Very Strong): "You ought to do X" implies "You also have the ability to refuse to do X." (If you can't say no, you aren't really free to say yes).

2. The Solution: A Modular Lego Kit

The authors realized that old logic systems were like a pre-built house; you couldn't easily change the walls to fit different "Can" rules. So, they built a modular Lego kit (called a "Deontic STIT Framework").

  • The Base: A standard logic system that handles agents making choices.
  • The Bricks: They created specific "rules" (like D2, D3, D4, D5) that act like Lego bricks.
    • If you snap on the "Possibility Brick," your logic system now only allows duties that are possible.
    • If you snap on the "Control Brick," your system now requires that the agent has total control over the outcome.

This allows them to build 16 different logic systems, each representing a different philosophical stance on what it means to "be able to" do something.

3. The Tool: The "Proof-Search" Machine

To test these systems, they built a Labelled Sequent Calculus. Think of this as a high-tech detective's checklist.

  • How it works: You write down a rule (e.g., "If you ought to do X, then you can do X"). The machine tries to prove it.
  • The Magic: If the machine gets stuck and can't prove it, it doesn't just say "Error." It automatically builds a Counter-Model.
    • Analogy: Imagine you claim, "I can fly." The machine tries to prove you can. It fails. Instead of just saying "No," it builds a tiny, perfect simulation of a world where you can't fly (maybe you have no wings, or gravity is too strong). This proves your claim is false in that specific scenario.

4. The Discovery: The "Endorsement Ladder"

By running their checklist on all 10 versions of "Ought-implies-Can," they discovered a hierarchy (a ladder).

  • The Endorsement Principle: This is their biggest finding. It's like a "Ripple Effect" in logic.
    • If you adopt the Strongest version (e.g., "I must have total control to be obligated"), you are automatically committed to accepting all the Weaker versions (e.g., "It must be logically possible," "It must be physically possible").
    • However, if you only accept the Weakest version, you are not committed to the Stronger ones.

They mapped out exactly which rules force you to accept others. It's like saying: "If you agree that a driver must have a license to drive, you automatically agree that the driver must be alive. But if you agree the driver must be alive, you don't necessarily agree they need a license."

5. Why This Matters

Before this paper, philosophers were shouting past each other, using the same words ("Ought," "Can") but meaning different things.

  • For Philosophers: This paper provides a "Rosetta Stone." It shows exactly how different interpretations of moral responsibility relate to each other.
  • For AI and Law: As we build AI agents that make decisions (like self-driving cars or legal bots), we need to know exactly what "duty" means. If an AI is told "You ought to save the pedestrian," does it matter if the AI could have chosen not to? This paper gives the engineers the precise mathematical tools to define those boundaries.

Summary

In short, the authors took a fuzzy philosophical debate, built a precise mathematical toolbox to dissect it, and produced a family tree of moral rules. They showed us that "Ought implies Can" isn't just one rule; it's a spectrum, and choosing one point on that spectrum logically forces you to accept the points below it.

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 →