How the law format models an Awb procedure: what an article establishes, the hooks on an application, the stages of a decision, an objection that takes a decision again, and the appeal to the court.
A specific law says that someone may apply for something. The procedure around that application comes from the Algemene wet bestuursrecht (Awb), from what the application must contain up to the objection against the decision. The rulework of the specific law does not have to name the Awb. The Awb articles attach themselves to every application through hooks.
RFC-045 gives the design and its reasons. Chronolexography shows how a cell, the organization that keeps a chronicle of its legal facts, records the procedure.
An article that establishes an application and decides on it lists both under produces:
outputs. derived holds values that follow from the decision but are not part of it, such as the end date of a permit.established_by limits a hook to the application of one article.produces.moment).Hooks and Reactive Execution covers hooks in general.
A procedure has stages (RFC-008). When the engine runs an article at one stage, it computes only that stage:
| Stage | What runs |
|---|---|
| AANVRAAG, BEZWAAR, BEROEP | The hooks on that kind of submission: Awb 4:2 and 4:13 on an application, 6:5 and 6:9 on an objection and an appeal, and 7:10 on an objection. The decision computes no output yet |
| BESLUIT | The decision, with Awb 3:46 and 6:7 |
| BEKENDMAKING | Awb 6:8: the decision is made known and the objection period starts |
| UITSPRAAK, TOEZENDING | In the procedure beroep: the judgment on an appeal, and sending a copy of it to the parties (Awb 8:79) |
Without a procedure, as in a scenario or the editor, every hook fires at once.
The law says what the decision needs. The process supplies it from three places:
implements (Inversion of Control). A policy may use the answer that a cell gives from its own records (Chronolexography);decided_per_case_by. The authority gives a finding: what it decides itself on an open norm in a single case. The finding is keyed by the term’s id.When a policy fills an open term, the term gets the policy’s value. The engine does not ask the authority for a finding. If the policy wants the authority to judge a case itself, the policy says so with an open term of its own (Inversion of Control). Cross-Law References says when the engine refuses a finding.
An objection is a second submission. Awb 7:11 establishes it and also decides on it. The objection holds the contested decision. To decide on the objection, Awb 7:11 takes the contested decision again:
This call runs on the day of the decision on the objection. It uses the fields and findings of the contested decision, plus any new findings of the authority. Cross-Law References describes the decision value.
The authority judges two questions of admissibility case by case, as open terms of 7:11 with decided_per_case_by. Is the objector an interested party (Awb 7:1 lid 1 with 8:1 and 1:2)? And for an objection that came in late, can the objector reasonably not be held at fault (Awb 6:11)? 7:11 tests the period first, then the contested decision, then the interested party, and the engine stops at the first test that fails. The cell still refuses a decision without a required finding of the deciding article, also one the engine would not reach. So the authority gives both findings on every objection, and the one under 6:11 only counts when the objection is late.
| Situation | Result |
|---|---|
| Late (Awb 6:9), and the authority finds the objector at fault | Not admissible; no reconsideration |
| Late, but the authority finds the objector not at fault (Awb 6:11) | Admissible as far as the period goes |
| Against a decision on objection (Awb 7:1 lid 1 onder a) | Not admissible. The engine sees this because the contested decision’s taken_on is 7:11 |
| The authority finds the objector no interested party (Awb 7:1 lid 1 with 8:1) | Not admissible; no reconsideration |
| Admissible, and the outputs are the same | Unfounded; the decision stands |
| Admissible, and an output differs | The decision is revoked; nieuw_besluit holds the new decision, which is part of the decision on the objection and has no record of its own |
Only outputs count. A derived end date that shifts because the day is later does not make the objection founded.
In the Awb of the chronolexography PoC, 7:11 declares the effect revokes: bestreden_besluit when bestreden_besluit_herroepen is true. A reduction that plays the chronicle then no longer counts the contested decision (Which records count).
Against the decision on the objection, an interested party (belanghebbende) can go to court (Awb 8:1). Awb 8:70 establishes the appeal and decides on it, as 7:11 does for the objection.
The judgment has the kind UITSPRAAK. A court is not an administrative body (Awb 1:1 lid 2 onder c), so what it decides is not a besluit. The appeal follows a procedure of its own, beroep, with the stages BEROEP, UITSPRAAK and TOEZENDING.
termijn_einddatum, bezwaar_of_beroepschrift_tijdig_ingediend. On a decision on objection, termijn_einddatum is the last day for lodging the appeal.taken_on is 7:11, Awb 7:1 lid 1);decided_per_case_by, and the court gives them as findings.uitspraak_in_de_plaats.| Situation | Result |
|---|---|
| Late (Awb 6:9), and the court finds the appellant at fault | Not admissible; the court judges nothing |
| Late, but the court finds the appellant not at fault (Awb 6:11) | Admissible as far as the period goes |
| Against a decision on an application, without objection (Awb 7:1 lid 1) | Not admissible |
| No rule breached | Unfounded; the decision stands |
| A rule breached, legal effects not kept | Well founded: the decision is annulled, with an order for a new decision |
| A rule breached, legal effects kept | Well founded: the decision is annulled, and no new decision is needed |
| A rule breached, and the court decides the case itself | Well founded: the decision is annulled, and the judgment holds the decision in its place. There is no order |
A party records the receipt of the copy of the judgment (8:79) as a fact (Cell::record_receipt). In the Awb of the PoC that fact revokes the decision it refers to when the court annulled it with its legal effects (rechtsgevolgen_vernietigd). A judgment that keeps the legal effects revokes nothing. When the court decides the case itself, the copy holds the decision in its place (uitspraak_in_de_plaats) as an object, not a decision: the receiving cell reads it and does not take it anew.
A provisional measure of the voorzieningenrechter lapses as soon as the objection, or the appeal against the decision on it, is withdrawn (8:85 lid 2 onder b). The PoC records the withdrawal as a fact of 6:21 that refers to the objection or to the decision on it, so a reduction finds it beside the decision. Under a, where the period for appeal passes unused, the measure does not lapse yet in the PoC (open questions).
RFC-053 gives the design. packages/poc-chronolexografie/corpus/regulation/nl/wet/algemene_wet_bestuursrecht/scenarios/beroep.feature plays these cases.
A question is listed only when a choice is still to be made, when it needs investigation first, or when it needs a large refactor or a breaking change to the schema. Open Questions in Chronolexography gives the rule.
| Question | Why open |
|---|---|
Stages are an Awb detail built into the format. The schema calls procedure Awb-defined, and the stage of a hook defaults to BESLUIT. The engine uses BESLUIT and the submission kinds (AANVRAAG, BEZWAAR, BEROEP) as stages. The cell runs two pairs of stages by name: BESLUIT and BEKENDMAKING, or UITSPRAAK and TOEZENDING (RFC-053). Should stages stay, as a free field whose values come from the law that defines the procedure? A run without a stage, such as a scenario, counts as BESLUIT. A procedure without that stage, such as beroep (UITSPRAAK, TOEZENDING), then fires no stage hooks. No such hooks exist yet. | Choice; breaking schema change |
decision_type is fixed per article, while one article can both grant and refuse. The value says nothing about the outcome, and no hook in the corpus filters on it. RFC-022 proposes an open vocabulary. Should the field go, be derived from the outcome, or stay as a free field? | Choice; breaking schema change |
| Awb 8:72 lid 4 says the court “kan” (may) order a new decision. The model always orders one when the court annuls, does not keep the legal effects and does not decide the case itself. It does not model the court’s instructions. Should the order be a finding of the court instead? | Choice |
The court can decide the case itself and grant a parking card. The municipality’s reduction then counts that card as an earlier card. But the reduction is silent on whether the card is still valid, so the college judges that. The row of the decision the court set in place holds kaart_geldig_tot as null, because only the college derives that date when it decides. Should the court’s decision value carry the derived data too? | Choice |
| An appeal against the judgment (hoger beroep, Awb 8:104 and 8:105) is recorded as text only. How the judgment of a higher court would reach the cells of the lower court and the administrative body is not designed yet. | Investigation |
| Which article 7:11 calls is known only at run time. So the dependency graph, the editor and the type checker do not see that link. | Large refactor |
| Of the motivation requirements in Awb 3:46 to 3:50, only 3:46 is modeled, as a flag that the decision needs a motivation. These are not modeled: 3:47 (state the motivation and its statutory basis when the decision is made known), 3:48 (when the motivation may be omitted), 3:49 and 3:50 (referring to an advice and departing from one), and 3:45 (the notice of legal remedies). The engine already knows much of a motivation: the legal basis, who filled each open term, and the trace. Should that go into the decision record? The answer bears on the Awb 4:84 question in Open Questions in Chronolexography, because a departure from policy must be motivated. | Choice |
Each substantive article establishes its own application (produces: AANVRAAG). Awb 4:1 says that an application for a beschikking goes to the competent body. So 4:1 could establish every such application once, and the substantive article would only say what is decided. The Awb would then say in one place what an application is. Awb 4:5 (not processing an incomplete application) would hook onto that one article. | Choice; breaking schema change |
An exploration into transparent, executable legislation, and one of the three projects in the starting selection of the Nederlandse Digitale Dienst.
GitHub repository
How it works
Demo walkthrough
Stay informed
Roadmap (Dutch)
Documentation
Research
Basiswerk recht (Dutch)
Nederlandse Digitale Dienst
Ministry of Economic Affairs and Climate Policy