§18 · Lane 1 — Rules-as-Code / Law-as-Code

Rules as Code and the Rule of Law the rule-of-law critique as design constraint

Burton Crawford (2023) · Public Law

Academic Tier 2 Lane 1 DOI
Read on publisher · DOI

Bibliographic data

Title
Burton Crawford (2023) — Rules as code and the rule of law
Authors / Issuing body
Lisa Burton Crawford
Venue / Publisher
Public Law (UK; AGIS-indexed)
Year
2023
Designation
Academic
Licence
Refer to publisher for full licence terms.

How to cite

Burton Crawford (2023). Burton Crawford (2023) — Rules as code and the rule of law. Public Law (UK; AGIS-indexed). https://search.informit.org/doi/10.3316/agispt.20230721091881.

A peer-reviewed Australian public-law critique of Rules-as-Code on rule-of-law grounds. Identifies the constitutional and administrative-law objections to translating legislation into code. The academic counterweight to the Mowbray, Chung, Greenleaf technical-implementation lineage.

Why it matters for NETEVO

Burton Crawford is the peer-reviewed Australian public-law critique of Rules-as-Code — the constitutional and administrative-law objections to translating legislation into executable code. For any practitioner methodology in this space, including NETEVO's published Law-to-Code Methodology, the critique operates as a design constraint: it is what separates naive Rules-as-Code maximalism from a defensible practitioner position.

Academic counterweight. The Rules-as-Code literature has an implementation lineage in Mowbray, Chung and Greenleaf and a language-design strand in the Catala DSL work. Burton Crawford supplies the missing corner: the public-law analysis of what is lost, or put at risk, when legislative rules become code. Read together, the two sides yield the defensible position — Rules-as-Code where the rule-of-law objections are mitigated by control design, not Rules-as-Code for its own sake.

Design constraint, not embarrassment. Each of the critique's concerns converts into a concrete engineering requirement: human-in-the-loop intercepts, traceability of every coded rule to its legislative source, version control on rule translations, and the requirement that machine decisions remain reversible by human review. A practice that can name the concern and point to the engineered mitigation has treated the critique as a specification rather than a reputational threat to manage around.

Four-corner debate. With the Amantea, Governatori and Quaranta methodology paper, Burton Crawford completes the four corners of the Rules-as-Code debate: implementation lineage, DSL design, rule-of-law critique, and compliance methodology. Together they frame the question a director or general counsel can put to any legislation-as-code implementation: not whether the rules execute, but whether the constitutional objection has been answered in operational terms.

Where NETEVO applies this

Who acts on this

Reading this usually means something has forced the question — a listing, an audit finding, a procurement questionnaire, a regulator's letter. The role pages below set out what NETEVO does about it, including where we would tell you not to engage.