Standard Deontic Logic (SDL) is a modal logic system that extends classical propositional logic with the obligation operator O and the permission operator P to formally represent normative reasoning about what ought to be the case. Axiomatized by Georg Henrik von Wright in his seminal 1951 paper Deontic Logic, SDL treats obligation as a necessity-like modality governed by the rule that if something is obligatory, it is also permitted (i.e., Op → Pp), and that obligation is closed under logical consequence.
Glossary
Standard Deontic Logic (SDL)

What is Standard Deontic Logic (SDL)?
The classical axiomatic system for reasoning about obligation and permission, formalized by Georg Henrik von Wright, that models ideal normative states but is vulnerable to paradoxes in non-ideal scenarios.
SDL models only ideal normative states where all obligations are fulfilled and no violations occur, making it fundamentally unable to represent contrary-to-duty (CTD) obligations—the conditional duties that arise when a primary obligation has been breached. This limitation leads to well-known paradoxes such as Chisholm's Paradox and the Gentle Murderer Paradox, which expose the inadequacy of SDL's monotonic framework for real-world legal reasoning where violations and remedial norms must be consistently modeled.
Key Features of Standard Deontic Logic
Standard Deontic Logic (SDL) provides the foundational axiomatic framework for reasoning about obligation, permission, and prohibition. It models ideal normative states using modal operators but is critically limited in handling contrary-to-duty scenarios.
The Core Modal Operators
SDL extends classical propositional logic with two interdefinable modal operators that capture the essence of normative reasoning:
- Obligation (OB):
OBpreads as 'it is obligatory that p.' - Permission (PE):
PEpreads as 'it is permitted that p.' - Prohibition (PR):
PRpreads as 'it is forbidden that p,' defined asOB¬p.
The dual relationship is central: PEp ≡ ¬OB¬p. An action is permitted if and only if it is not obligatory to refrain from it.
The Axiom Schema K
SDL is built on the Kripke-style normal modal logic KD. The defining axiom is the distribution axiom K:
OB(p → q) → (OBp → OBq)
This states that if it is obligatory that p implies q, then if p is obligatory, q is also obligatory. This axiom ensures that obligations are closed under logical consequence, meaning an agent is obligated to do everything logically entailed by their duties.
The Deontic Consistency Axiom (D)
The characteristic axiom that distinguishes deontic logic from alethic modal logic is Axiom D:
OBp → PEp (or equivalently, OBp → ¬OB¬p)
This enforces the Ought-Implies-Can principle at the logical level: if something is obligatory, it must be permissible. It guarantees that a normative system cannot simultaneously obligate an action and its omission, preventing explicit moral dilemmas from being encoded as theorems.
Possible World Semantics
SDL is semantically interpreted using deontic accessibility relations over possible worlds. A world v is deontically accessible from w if v is an ideal or perfect version of w where all obligations are fulfilled.
OBpis true at worldwiffpis true in all deontically ideal alternatives tow.PEpis true iffpis true in at least one deontically ideal alternative.
Axiom D corresponds to the seriality of the accessibility relation: every world has at least one ideal counterpart.
The Paradox of Contrary-to-Duty
The critical limitation of SDL is its inability to consistently model Contrary-to-Duty (CTD) obligations—conditional duties that activate when a primary obligation is violated. Chisholm's Paradox demonstrates this failure:
- It ought to be that Jones goes to help his neighbors.
- If he goes, he ought to tell them he is coming.
- If he doesn't go, he ought not tell them.
- Jones does not go.
In SDL, this set of intuitively consistent statements derives a logical contradiction, exposing the system's inadequacy for real-world normative reasoning.
The Ross Paradox
The Ross Paradox illustrates a counterintuitive consequence of the K axiom in deontic contexts. From OBp, SDL derives OB(p ∨ q)—if you ought to mail the letter, you ought to mail it or burn it.
This is a paradox of disjunction introduction under obligation. While logically valid, it violates pragmatic norms: fulfilling the obligation to mail-or-burn by burning the letter seems absurd. This highlights the gap between formal deontic consequence and intuitive normative reasoning.
Frequently Asked Questions
Clear, technical answers to the most common questions about the classical system of deontic logic, its axiomatic foundations, and its limitations in modeling real-world legal norms.
Standard Deontic Logic (SDL) is the classical system of deontic logic axiomatized by Georg Henrik von Wright in 1951, formalizing the concepts of obligation, permission, and prohibition using modal operators. SDL extends propositional logic with the O operator (it is obligatory that) and the P operator (it is permitted that), where prohibition is defined as the obligation not to do something: Fφ ≡ O¬φ. The system is built on a normal modal logic foundation, typically the modal system KD, which adds the deontic axiom D: Oφ → Pφ (if something is obligatory, it is permitted) to classical logic. Semantically, SDL uses possible world semantics where obligation corresponds to truth in all deontically ideal worlds—worlds where all norms are perfectly satisfied. The key inference rules include necessitation (if φ is a theorem, then Oφ is a theorem) and monotonicity (if φ → ψ is a theorem, then Oφ → Oψ is a theorem), enabling the derivation of new obligations from existing ones through logical consequence.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Standard Deontic Logic (SDL) is the classical starting point for normative reasoning, but its limitations in handling real-world legal scenarios have spawned a rich ecosystem of extensions and alternatives. Explore the key concepts that build upon, challenge, or complement SDL.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us