Skip to content

Non-retroactivity

A legal temporal-application principle that bars a later rule from worsening the legal consequences of conduct completed before that rule took effect, with jurisdiction- and field-specific exceptions.

Version
v2 · 2026-09-06 · History
Domain-specific #
2386
Origin domain
law
Subdomain
temporal application of legal rules
Aliases
Principle of non-retroactivity

Core Idea

Non-retroactivity is the legal principle that a later rule should not worsen the legal consequences of conduct, facts, or completed situations predating that rule's entry into force. Its strongest and most widely entrenched form is criminal: conduct cannot be made criminal, or punishment increased, after the act. Article 7 of the European Convention on Human Rights prohibits retrospective criminal law to an accused's disadvantage, and the U.S. Constitution's Ex Post Facto Clauses bar retroactive criminal legislation.

The principle is broader but less uniform outside criminal law. Article 28 of the Vienna Convention on the Law of Treaties supplies a default rule: absent a different intention, a treaty does not bind a party regarding an act, fact, or situation that ceased before the treaty entered into force for that party.

Scope of Application

Criminal law. The clearest core bars creation of an offense or increase in punishment after conduct. Foreseeability and accessible law constrain unforeseeable judicial expansion as well.

Treaty law. Article 28 states a default, not an absolute prohibition: treaty text or otherwise established intent may authorize a different temporal reach, and continuing situations require careful classification.

Judicial decisions. Systems differ on when a new interpretation applies to pending, final, direct-review, or collateral cases. The U.S. constitutional Ex Post Facto Clauses apply to legislation, while due process constrains unexpectedly expansive judicial criminal interpretation.

Clarity

Use a five-column ledger:

  1. conduct or situation date;
  2. old rule and consequence;
  3. new rule's enactment and effective dates;
  4. proposed application and changed burden;
  5. controlling doctrine and exception.

This prevents three frequent errors. First, enactment and effective date may differ. Second, a situation beginning earlier may continue after entry into force. Third, a later rule may be merely procedural in one jurisdiction yet materially burdening in another. Labels cannot replace consequence analysis.

Manages Complexity

Legal change creates a versioning problem: many events are open, completed, pending, adjudicated, or continuing when the new rule arrives. Non-retroactivity partitions that mixed population and supplies a transition discipline. It protects notice, reliance, constraint on arbitrary punishment, and stable planning while allowing legal systems to change.

Abstract Reasoning

Fix the legally relevant event. The filing date, conduct date, injury date, conviction date, or continuing status may control differently.

Version the rule. State the old and new legal texts or holdings rather than saying “the law changed.”

Compare consequences. Determine whether the later rule creates, enlarges, mitigates, or merely administers the burden.

Knowledge Transfer

The temporal versioning skeleton transfers to software migrations, contracts, policy transitions, and data schemas: events produced under version A meet rules from version B. But legal non-retroactivity carries authoritative validity, rights, remedies, and jurisdictional exceptions. A database migration can borrow the reasoning without becoming an instance of the legal principle.

Within law, transfer is literal only when the same roles remain: legally relevant event, effective rule, consequence, jurisdiction, and exception. The result can differ even on identical dates because the governing field changes.

Relationships to Other Abstractions

Local relationship map for Non-retroactivityParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Non-retroactivityDOMAINPrime abstraction: Rule of Law — is a kind ofRule of LawPRIME

Current abstraction Non-retroactivity Domain-specific

Parents (1) — more general patterns this builds on

  • Non-retroactivity is a kind of Rule of Law Prime

    Rule of Law is presupposed because non-retroactivity constrains law's application through law.

Hierarchy paths (2) — routes to 2 parentless roots

Neighborhood in Abstraction Space

Non-retroactivity sits in a sparse region of the domain-specific corpus (80th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (1565 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08