⚖️ LEGAL DISCLAIMER: LexClinic Education, Inc. is applying for 501(c)(3) tax-exempt status. Materials, software runtimes, and APIs are for educational research and do not constitute formal legal advice. Read Full Disclaimer ➔
10 Published Modules (1.1–5.2) Individual Class Quizzes 🔒 Magic Link Auth Enabled

Legal Engineering 101 Curriculum

Foundational Video & Audio Lessons & Quizzes (Classes 1.1 through 5.2). Select a class below to listen to the audio/video lesson, review the curriculum summary, and complete the class assessment.

Official Spotify Audio Show

LexClinic Spotify Audio Show

Listen to full audio lectures, Socratic dialogues, and legal engineering episodes directly on Spotify.

Follow on Spotify 🎧 Podcast RSS Feed
🧠

Bottom-Up Curriculum Philosophy

Legal Engineering 101 courseware is designed strictly from the bottom up—crystallizing scaled, repeatable patterns as they organically emerge from weekly Socratic Events, Google Hangout calls, and member discussions.

🎥
Lesson 1.1

Class 1.1: What is a "Performance" in Law?

Explores how legal obligations shift from dormant paper records to active performance states verified upon condition triggers.

🎥
Lesson 1.2

Class 1.2: What is a "Runtime" in Software?

Defines software runtimes, virtual machines, and execution environments as deterministic engines processing input instructions.

🎥
Lesson 2.1

Class 2.1: The Composer Metaphor: Designing Before "Play"

Applies the composer and musical score metaphor to legal engineering—designing state structures and covenants prior to execution.

🎥
Lesson 2.2

Class 2.2: Minimizing Social Transaction Costs

Examines Nick Szabo's principles on how smart contracts and cryptographic protocols reduce human trust and social transaction costs.

🎥
Lesson 3.1

Class 3.1: Charles Goldfarb & GML: The Web's Legal Origin

Traces the history of Generalized Markup Language (GML) created by lawyer Charles Goldfarb, laying the legal foundation for HTML, XML, and structured data.

🎥
Lesson 3.2

Class 3.2: Nick Szabo & Smart Contracts: Hardcoding Consideration

Analyzes how Nick Szabo solved the validator incentive problem by hardcoding gas fees as programmatic legal consideration into state machine execution.

⚡
Lesson 4.1

Class 4.1: Decoupling Logic from Assets: Instructions vs. Data

Introduces computational legalese and the architectural separation between executable instruction code and underlying state asset data.

🎧
Lesson 4.2

Class 4.2: Data Primitives 101: Strings, Numbers, and Booleans

Deconstructs fundamental data primitives—strings, fixed-point numbers, and booleans—that encode legal terms into machine-evaluated conditions.

⚡
Lesson 5.1

Class 5.1: Active Scripts vs. Static Sheets

Examines the paradigm shift from passive legal spreadsheets to self-executing active scripts that automatically monitor and enforce performance state transitions.

🎥
Lesson 5.2

Class 5.2: Typing Domains: How Code Validates Data

Analyzes typing domains, data validation bounds, and compiler-level type checking that prevent invalid or out-of-range covenant state executions.