Legal engineering
compliancepolicy as code · rule encoding · legal engineer
The discipline of translating regulatory text and legal judgement into logic an AI system can execute and verify, so the rule stops living in a document and starts living inside the agent.
Legal engineering is the craft of turning a written obligation — a law, a sector regulation, an internal policy or a house risk standard — into verifiable rules an agent applies on every run. It is not automating the lawyer's work: it is encoding the lawyer's judgement so it applies consistently thousands of times. The job has three parts: decomposing the rule into checkable conditions, deciding what evidence proves each one, and defining what happens when it fails (block, flag, escalate). The people who do it usually come from law and work with engineering rather than the other way round, because the hard part is not coding but deciding what 'sufficient' means in each case. For a company already running agents in production, legal engineering is what turns an AI policy PDF into a control that actually executes.
How it differs from
- Agent governance
- Governance sets who decides and with what permissions. Legal engineering writes the concrete rule the agent checks.
- AI assurance
- Assurance independently verifies afterwards that the control worked. Legal engineering builds that control.
- Legal advice
- Advice produces a judgement for one case. Legal engineering produces an executable artefact applying that judgement to every case.
Examples
- Turning the duty to disclose that the user is talking to an AI into a check the agent runs on every first reply.
- Translating the discount policy into authority limits a sales agent cannot exceed without escalating.
- Encoding which claims require an approved source before they can be published.
FAQ
- Do you need a lawyer for this?
- To decide what the rule means, yes. To turn it into an executable check you need someone who knows both, or two people who actually talk. The expensive mistake is letting engineering write it alone: it ends up checking what is easy to check, not what is binding.
- Is it the same as compliance as code?
- Close, but compliance as code came from infrastructure and checks system states. Legal engineering checks decisions and content, where the right answer depends on context rather than configuration.
Related terms
Stanford Law — Legal Engineering: A Paradigm Shift in Law (John J. Nay) · 2025-09-03 · E3