Law & Language: How Rules Learn to Mean
Key Insights
- From Savigny's historical school to Hart's open texture: how law evolves the way language does, why natural-language rules always carry a penumbra of uncertainty, and what that means for turning legislative sentences into executable compliance predicates.
Law is a language technology. Rules are written in words, interpreted through words, and enforced because words can bind. This essay traces the long argument β from Savigny to Hart β that law evolves the way language does, and draws out what that means for modern compliance systems that must turn legislative sentences into executable predicates.
Savigny and the historical school
Friedrich Carl von Savigny, writing at the turn of the nineteenth century, rejected the idea that law was a timeless, deductive system that a legislature could simply invent. In On the Vocation of Our Age for Legislation and Jurisprudence (1814) he argued that law grows organically out of a people's life β its Volksgeist, its spirit β the same way language does. A language cannot be designed by committee and decreed into being; it lives in speakers, changes with usage, and dies when no one speaks it.
Law, Savigny held, is the same: it is not a closed formal system but a living practice carried by jurists and citizens. The insight that matters for us is not romantic nationalism but the analogy itself β rules, like words, acquire meaning through use, drift with time, and resist being fixed by flat.
Hart: rules about rules, and open texture
H. L. A. Hart's The Concept of Law (1961) gives the analogy a precise shape. Law, for Hart, is a union of two kinds of rule:
- Primary rules impose obligations β do not launder money, do not mislead investors, do not misreport.
- Secondary rules are rules about rules β how rules are recognised (a constitution, a statute book), how they are changed (legislation), and how they are adjudicated (courts).
Hart's crucial claim for systems design is open texture: natural-language terms always have a "penumbra" of uncertainty. Words like "suspicious", "reasonable", "beneficial", and "risk" have a settled core and a hazy fringe. At the fringe, judges exercise discretion. Open texture is not a defect of language; it is what lets law adapt to cases the legislator never imagined. But it is exactly the property that makes natural-language rules hard to execute mechanically.
The translation problem in compliance
Every AML and compliance rule faces the same journey: legislative sentence β regulator guidance β internal policy β executable predicate (a Boolean filter, a threshold, a machine-learning score). Each step of translation is a lossy compression of meaning.
- "Suspicious transaction" becomes a pattern rule about structuring around reporting thresholds.
- "Beneficial ownership" becomes a lookup across a corporate register with a cutoff at a percentage ownership stake.
- "Reasonable steps" becomes a documented due-diligence checklist.
The gap between what the words mean and what the predicate tests is where compliance risk actually lives. A model that exactly follows the predicate can still be entirely unfaithful to the rule β and a rule faithfully applied can still be wrong in open-textured cases. Understanding this gap is the difference between a compliance function that mechanically checks boxes and one that reasons about whether the boxes mean what the law says.
Semantic drift and the linguistic arms race
Words change meaning as the world changes, and law must chase them. "Money" once meant notes and coin; it now includes crypto-assets, stablecoins, and tokenised instruments. "Identity" once meant a paper document; it now means a verified credential in an ecosystem. Regulators respond through guidance, interpretive notes, and amendment β a linguistic arms race in which the regulated community and the regulator continuously renegotiate what the words mean.
Two modern movements respond directly to this. The plain-language movement tries to shrink open texture by drafting rules a citizen can read. The Rules-as-Code / legislation-as-code experiments (in New Zealand, Canada, and elsewhere) try to draft law in machine-executable form from the start, so that the translation loss described above shrinks to zero.
What a schema has to do with a statute
From a data-engineering perspective, the analogy is almost literal. A schema is a legislature for a database: it fixes the shape of the words (fields, types, allowed values) and the rules of change (versioning, migration, breaking-change review). A data contract between two systems is a treaty about meaning. The same open texture Hart found in statutes appears in schemas whenever a field is vaguely defined or a contract is silent on semantics. The discipline of governing a database's vocabulary is, in miniature, the discipline of governing a legal system's vocabulary. That is why this essay belongs in the lawβlanguageβdata story: the problems of meaning are shared, and so are the tools.
Article Metadata
Bloom Taxonomy Questions
Explain Hart's distinction between primary and secondary rules, and where open texture comes from.
Take one open-textured term in AML (e.g. 'suspicious' or 'beneficial ownership') and trace its translation from statute to executable predicate, identifying where meaning is lost.
Should legislation be drafted in machine-executable form from the start? Weigh the benefits against the risks of fixing open texture too early.
Design a rule artifact that captures the meaning of an open-textured legal term better than a naive threshold does.
Further Reading
FATF
Financial Action Task Force β global AML/CFT standards and grey/black lists
FinCEN Press
FinCEN press releases β rulemakings, advisories, enforcement orders
ACAMS
Association of Certified Anti-Money Laundering Specialists β training, research, typologies
FinCEN
US Financial Crimes Enforcement Network β SAR filings, advisories, BSA guidance
OFAC
US Office of Foreign Assets Control β sanctions lists, enforcement actions
AMLA
EU Anti-Money Laundering Authority β rulebook, RTS, direct supervision