An open format that states under the rule of law can trust.

A RUML file does not describe the wording of a statute but the logical structure laid out in it: the elements of the norm as nodes, connected by six logical operators – AND, OR, EXCLUSIVE OR, and their negated variants – with every node bound to the passage of text from which it is derived. What emerges is not a model alongside the norm but a second representation of the same norm: one that makes its logic visible instead of hiding it in running text.

The Core holds the normative structure: the node hierarchy with dual identifiers – a readable LexID for the file, a UUID for the world – the six operators, and metadata on version and validity. It deliberately contains only what can remain unchanged for years and be certified. A rulemap in the pure Core is complete as a logical structure: it can be walked through, shared, versioned, and signed. It is the explicit form of subsumption, captured in a file.

The Capability layer anchors it in the normative text and makes it machine-evaluable. Standard Capabilities under the ruml: prefix bind every node to the passage of text it represents (ruml:text-reference), and the structure to data sources, evaluation, and reactions: from typed data schemas (ruml:datapoints) through deterministic expressions (ruml:query) to the designated AI-supported assessment of individual nodes (ruml:ai-query) as a marked exception to deterministic evaluation. Arithmetic and thresholds are also in the file, not outside it: a rulemap is not a Boolean skeleton but the complete representation of the norm. Third parties extend it in their own namespaces – the Core remains untouched, and every conformant implementation reads the same file.