Skip to content
docs
Arxo ↗

RegelRecht

For LLMs7 sections

In short: RegelRecht writes the executable regulation next to the Dutch article; Arxo pins the article and executes a model of it. On the same objection-deadline articles they predict an exactly-one-day divergence — with the cause still open. This page is for readers of Dutch administrative automation who want that story told precisely.

What RegelRecht is for

Section titled “What RegelRecht is for”

RegelRecht publishes open machine-readable versions of Dutch laws, each file and article machine-linked to the official gazette publication. Its strengths are date-versioning by file with a harvester that tracks the official XML, acceptance scenarios in behavior-driven form beside the law with a grammar dictionary lawyers can read, procedural stages with article hooks, and an evaluation binary with an explanation trail.

Where it meets Arxo

Section titled “Where it meets Arxo”

The executable overlap is the General Administrative Law Act: the duty to motivate decisions, the start of the objection term, and the six-week term — their regulation file against an Arxo package, with the pinned official text as arbiter. Coverage differs honestly on both sides: Arxo models neighboring articles the file lacks; the file has procedural stages and hooks Arxo lacks. Both remainders are non-comparable, not missing.

Key differences

Section titled “Key differences”
  • A predicted one-day divergence. Their end date reads publication plus 42 days; Arxo’s deadline reads start plus 42, which lands one day later. The text’s “six weeks” plus “the day after” does not settle whether the start day counts inclusively. The verdict on the boundary cases is mismatch-with-open-cause until an arbiter (the act plus the general time-limits statute) settles it — the most worked example in this section of an honest open question.
  • Flag versus duty. Their file sets an unconditional motivation-needed flag; Arxo models an enforceable duty plus an external court judgment on adequacy, undecided without it. Different tasks — a signal versus an obligation — not a defect on either side.
  • Calendar days are pure. Their date arithmetic is plain calendar days with no roll; Arxo declares an explicit no-roll calendar. Weekend-shift behavior under the time-limits statute is not established on either side and stays open.
  • Lineages stay separated. Proof-of-concept claims from an archived Python line belong to that archive, not the current engine; a separate controlled-language line from the tax authority is a different project with no confirmed link. The page does not borrow their credit.

A concrete scenario

Section titled “A concrete scenario”

Twelve base cases — term start, plus-and-minus-one-day deadline boundaries, timely receipt, flag-versus-duty, non-comparable controls, null semantics, a schema-drift control — plus four edits covering further term-start paragraphs, a leap day, a cross-edition case, and the weekend-shift question. The same inputs run through the pinned evaluation binary and the Arxo package; one side’s end date below is reviewer arithmetic from file rules, not engine output, and must be rechecked at run time.

Choosing and combining

Section titled “Choosing and combining”

Choose RegelRecht when the work is Dutch agency regulations with gazette linkage, lawyer-readable acceptance scenarios, and procedural stages. Look to Arxo when neighboring articles, judgment-routed adequacy, and edition-pinned provenance carry the case. Combined, the regulation file can serve the operational computation while Arxo holds the contestable reading — with the one-day divergence as the documented place to watch.

Evidence and open questions

Section titled “Evidence and open questions”
  • Sources checked: September 2026 (repository, language-choice record, format docs, the studied regulation file, the evaluator source, and the controlled-language paper; one cited report was unreachable and is marked as such).
  • Studied profile: the engine crate and toolchain at pins, the regulation file in its schema version.
  • Basis: confirmed by documentation plus a prepared protocol with a frozen case bank; comparative run not performed.
  • Open: the one-day cause, gazette-slice reconciliation across different slice dates, weekend shifts, and the run itself.

Sources and reproducible materials

Section titled “Sources and reproducible materials”

Documentation for Arxo. Writings — blog.arxo.io.

Anonymous visit counts on stats.arxo.io, no cookies.