A statute a computer can apply and a lawyer can read

Picture applying a statute to a client's facts and getting the same answer every time, traced to its provision, with "what if" tried before you advise. Rules as code promises that: law written so a computer can apply it. It helps only if lawyers can follow the code.

The question. A university research programme asked: can lawyers read and write law in this form?

The work. We read a real statute and its instruments as lawyers. Before any code, we sorted every provision into three layers: definitions; duties and powers; changes to official records. Each rule, in an open-source rules-as-code language, has a plain-word name and a reference back to that map.

What made it readable. The map leads from provision to rule and back. A seven-part tutorial builds from one rule, tried on sample facts, to the whole scheme, and ends with common pitfalls.

Where it stands. The code passes a machine check that its parts fit together, but its tests have never run: it is a draft for study, not yet a tool to rely on. The programme has a worked example, and a way in for the next lawyer.