This is where the open ecosystem for digital law is taking shape.
Laws exist today as text. In the open ecosystem, they also exist as Rulemaps: visual models that people can read and review and that software can execute. The format behind them, RUML, is open, and the Rulemapping Workspace is free to use after registration – so legislators, administrations and developers work on the same models.
Law as Code means writing law so that people can review it and machines can execute it. Rulemapping puts this into practice: a law becomes a decision model in which every step traces back to the legal text. Administrations can apply such a model digitally, and every decision remains explainable and open to challenge.
Register for the Rulemapping Workspace and model a law, a guideline or an internal policy as a Rulemap – visually and without programming. The Rulemapping Academy teaches the method in short video lessons. Anyone who models with Rulemapping today helps bring Law as Code into practice.
The Rulemapping Workspace is the place to create, review and apply Rulemaps. Laws are modelled visually in the Rulemap Builder. The Rulemapping Cockpit is the chat-based way in and carries all Rulemapping Tools: it turns a legal text into a first Rulemap, compares two Rulemaps or checks a concrete case against a Rulemap – each tool is described further down. Combined with a language model, Rulemaps form Rule AI, the neuro-symbolic system of the Rulemapping Group: the Rulemaps carry the logic, the model works on it.
The Rulemapping Workspace is in a test phase: every function is available to everyone after registration. The phase shows how the Workspace is used in practice, and that shapes its further development. Later, some functions will be part of a paid plan.
The Rulemap Builder is the application for creating and editing Rulemaps. A law, a regulation or an internal policy is modelled as a visual structure of conditions and legal consequences – in the browser, without programming. Nodes are linked to the passages of the legal text they come from: by hand when a Rulemap is built manually, pre-filled by ARUM and ready to be refined.
The Rulemap Catalog is the collection of Rulemaps in the Workspace, available after sign-in. It contains Rulemaps of laws as well as Rulemaps created in the Rulemap Builder. Rulemaps can be shared within an organisation.
RUML (Rulemapping Logic Format) is the open, JSON-based file format for Rulemaps. It represents laws, regulations and other rule sets as decision logic that software can execute – without altering their legal meaning.
What problem does RUML solve?
Laws are mostly available as plain text, so every application starts with manual interpretation. RUML holds the rules in a standardised form that can be evaluated automatically, the same way every time.
Who is RUML designed for?
For developers who build parsers, validators, editors and other software for legal logic – and for legislators, administrations and businesses that model their rules digitally and apply them automatically.
Is RUML freely available?
Yes. Using the format is free of licence fees. The specification is published by the Law as Code Institute under CC BY-SA 4.0.
Where can RUML be used?
Wherever decisions follow rules: tax law, social benefits, building permits, compliance checks, insurance or internal policies. RUML is independent of jurisdiction and industry.
The Rulemapping Tools take over individual steps in working with Rulemaps: drafting a Rulemap from a legal text, turning a Rulemap back into text, comparing, assessing and applying Rulemaps. Most of them are AI-supported, and their results are drafts and findings that remain open to review. All tools are available in the Rulemapping Cockpit.
ARUM (Automated Rulemap from Unstructured Material) turns laws, regulations and internal guidelines into a first Rulemap that is refined in the Rulemap Builder. It also updates an existing Rulemap from an amending text and reads BPMN and DMN. ARUM provides the starting point; the finished model comes from modelling.
MURA (Machine-generated Unambiguous Regulatory Articles) generates natural-language text from the logic of a Rulemap: legal provisions, draft legislation and documentation in an editable format. Every condition, exception and legal consequence of the Rulemap is covered. The result is an editorial draft; the final wording remains with the author.
CIRA (Comparison & Inconsistency Recognition Analyser) compares two Rulemaps. For two versions of the same Rulemap, it shows which nodes were added, removed, changed or moved; for independent Rulemaps on similar rules, it finds overlaps, redundancies and contradictions. The result is a text or a list with references.
REIA (Rule Effect Impact Analyser) assesses how a change to a Rulemap affects its decision logic and its results. It shows which paths run through the changed condition, which legal consequences depend on it and which paths remain untouched.
RAMP (Rulemap Automation Maturity Profile) checks a Rulemap for completeness, consistency and clarity, for gaps and open discretion, and for the degree of automation it can reach. The result is a score and a text with references.
FIRA (Fact Impact Rulemap Assessment) checks a concrete case against a Rulemap. The case is described in the Cockpit chat and supplemented with data and documents. FIRA returns the overall result and the Rulemap with a justification for every node.
















