§Legalese

Why Computational Law, Part II: 70 Years of Legal Informatics

Legalese Team
Legalese Team
Cover Image for Why Computational Law, Part II: 70 Years of Legal Informatics

"There is this tremendous body of knowledge in the world of academia where extraordinary numbers of incredibly thoughtful people have taken the time to examine on a really profound level the way we live our lives and who we are and what we've been. That brilliant learning sometimes gets trapped in academia and never sees the light of day." — Malcolm Gladwell

(at least) 70 years of legal informatics

The legal informatics industry is older than most web developers today.

An (incomplete) history in rough chronology—let us know if we missed something.


Formalising Contracts

See also


Formalising Regulations

As the richly interpretable saying goes, "Law is Code" and, conversely, Code is Law (Lessig, 2000). Legislative and regulatory constraints may be modeled using a declarative language.


Modelling Performance


Formal Verification of Smart Contracts

Formal methods and languages like Agda, Idris, Why3, and CoQ, not to mention specification languages like Z, hold much promise. On the spectrum of software reliability, smart contracts ought to live near mission-critical or life-critical software – cryptosystems, human-crewed spacecraft, hospital equipment. Today, they're closer to enterprise web-apps.

See The Atlantic on why formal verification is important.

The need for formal systems appears to be dawning on r/ethereum:

Key Papers:

Startups: Adjoint, Kadena (PACT), Tezos, Cardano


Academia-Industry Partnerships


Workshops & Conferences


"Well, all information looks like noise until you break the code" — Hiro Protagonist, Snow Crash (Neal Stephenson, 1992)


This is Part II of our series on Why Computational Law. See Part I: The Problem with Legal and Part III: Computational Law.