law-generate

name	law-generate
description	Generates machine_readable execution logic for Dutch law YAML files through an iterative generate-validate-test loop. Creates machine_readable sections, validates against the schema, runs BDD tests, and iterates until correct (up to 3 iterations). Use this skill proactively when: editing or creating machine_readable sections in law YAML files, working with corpus regulation files, or when user mentions 'generate', 'machine_readable', or wants to make a law executable. Activate automatically when user discusses law YAML files that need executable logic.
allowed-tools	Read, Edit, Write, Bash, Grep, Glob
user-invocable	true

Law Generate — Generate→Validate→Test Loop

Generates machine_readable sections for Dutch law YAML files through an iterative cycle of creation, validation, and BDD testing.

CRITICAL: All generated YAML MUST pass just validate <file>. The schema is the single source of truth. When in doubt, consult schema/latest/schema.json and study working examples in the corpus.

Setup

1. Read the target law YAML file
2. Read reference examples as few-shot context:
   • corpus/regulation/nl/wet/wet_op_de_zorgtoeslag/2025-01-01.yaml — basic patterns, IF/cases, cross-law references
   • corpus/regulation/nl/wet/algemene_wet_bestuursrecht/2026-01-01.yaml — hooks, procedures, DATE_ADD
   • corpus/regulation/nl/wet/vreemdelingenwet_2000/2026-01-01.yaml — overrides (lex specialis)
3. Read the schema reference: .claude/skills/law-generate/reference.md
4. Read the examples: .claude/skills/law-generate/examples.md
5. Read an existing feature file as Gherkin reference: features/bijstand.feature
6. Count articles; if >20 articles, process in batches of ~15

Explicit article subset (chunked enrichment): when the enrichment prompt supplies an explicit list of article numbers to process, that subset defines your entire scope. The internal batching above applies within that subset only, and every article outside the subset must be left completely untouched — do not add, edit, or remove machine_readable sections elsewhere in the file. The pipeline processes the remaining articles in later runs.

FUNDAMENTAL RULE: Stay Within Scope

Each machine_readable section must faithfully interpret ONLY the legal provision it belongs to — nothing more, nothing less. The scope is defined by the text field of the article, lid, or provision that the machine_readable is attached to.

Why this matters: The purpose of machine-readable law is to execute what the law says, not what an engineer thinks is efficient. It is very tempting for the engineering mind to optimize: to combine conditions from multiple articles into one check, to pull in eligibility rules from elsewhere "because they're needed anyway", or to hardcode values that technically come from another provision. Resist this temptation. The whole point is to follow the law very strictly, even when the law is illogical, redundant, or inefficient.

Scope violations to avoid:

• Do NOT add conditions from other articles. If article 2 says "de verzekerde heeft aanspraak op zorgtoeslag" and the age requirement comes from article 11 of another law, do NOT put leeftijd >= 18 in article 2's machine_readable. Instead, use a cross-law reference (source.regulation) to let the other article determine eligibility.
• Do NOT hardcode values that come from other provisions. If article 2 uses "drempelinkomen" but the amount is set by a ministerial regulation, declare it as an open_term or input with source, not as a definition.
• Do NOT combine multiple leden into one action unless the law text explicitly combines them. If lid 1 sets a base rule and lid 4 adds an exception, model them as separate outputs or use the structure the text prescribes.
• Do NOT add "obvious" conditions that aren't in the text. If the article doesn't mention an age check, don't add one — even if you know it's required by another article.

What to do instead:

• Use input with source.regulation to reference other laws
• Use input with source.output to reference other articles in the same law
• Use open_terms for values delegated to lower regulations
• If an article is a pure orchestration point (like "het college stelt het recht vast"), model it as cross-law references to the articles that define the substantive rules, not as a reimplementation of those rules

The law may be inefficient. That's fine. Model it as written.

Phase 1: Generate machine_readable Sections

For each article with computable logic, generate the machine_readable section.

Action Format (CRITICAL — two valid patterns)

Actions are the core of the execution logic. Each action MUST have an output field. There are two valid patterns for specifying what to compute:

Pattern 1: value — for assignments, comparisons, conditionals, and logical ops

actions:
  - output: heeft_recht
    value:
      operation: AND
      conditions:
        - operation: GREATER_THAN_OR_EQUAL
          subject: $leeftijd
          value: 18
        - operation: EQUALS
          subject: $is_verzekerd
          value: true

Pattern 2: value — for direct literal/variable assignment

actions:
  - output: wet_naam
    value: Wet op de zorgtoeslag
  - output: constante
    value: $SOME_DEFINITION

Pattern 3: Open terms (IoC) — higher law declares, lower regulation fills

The higher law declares an open_term and references it as $variable:

# In the higher law (e.g., wet_op_de_zorgtoeslag article 4)
machine_readable:
  open_terms:
    - id: standaardpremie
      type: amount
      required: true
      delegated_to: minister
      delegation_type: MINISTERIELE_REGELING
  execution:
    output:
      - name: standaardpremie
        type: amount
        type_spec:
          unit: eurocent
    actions:
      - output: standaardpremie
        value: $standaardpremie

The lower regulation registers as implementing it:

# In the lower regulation (e.g., regeling_standaardpremie article 1)
machine_readable:
  implements:
    - law: wet_op_de_zorgtoeslag
      article: '4'
      open_term: standaardpremie
      gelet_op: Gelet op artikel 4 van de Wet op de zorgtoeslag
  execution:
    output:
      - name: standaardpremie
        type: amount
        type_spec:
          unit: eurocent
    actions:
      - output: standaardpremie
        value: 211200

Operation Syntax by Category

Arithmetic — use values array (NOT subject/value):

operation: ADD          # or SUBTRACT, MULTIPLY, DIVIDE, MIN, MAX
values:
  - $operand_1
  - $operand_2

Comparison — use subject + value:

operation: EQUALS       # or GREATER_THAN, LESS_THAN,
                        # GREATER_THAN_OR_EQUAL, LESS_THAN_OR_EQUAL
subject: $variable      # MUST be a $variable reference
value: 18               # literal or $variable

Membership — use subject + value or values:

operation: IN
subject: $status
values: ["ACTIEF", "GEPAUZEERD"]
# OR with a single reference:
# value: $allowed_statuses

Logical — use conditions array:

operation: AND          # or OR
conditions:
  - operation: EQUALS
    subject: $a
    value: true
  - operation: EQUALS
    subject: $b
    value: true

NOT — negation, use value:

operation: NOT
value:
  operation: EQUALS
  subject: $is_verzekerd
  value: true

Conditional IF — use cases/default (NOT when/then/else):

operation: IF
cases:
  - when:
      operation: EQUALS
      subject: $heeft_partner
      value: true
    then: $bedrag_partner
  - when:
      operation: EQUALS
      subject: $categorie
      value: "B"
    then: 75000
default: $bedrag_alleenstaand

Date: AGE — calculate age in complete years:

operation: AGE
date_of_birth: $geboortedatum
reference_date: $peildatum

Date: DATE_ADD — add duration to a date:

operation: DATE_ADD
date: $bekendmaking_datum
weeks: 6              # optional: years, months, weeks, days

Date: DATE — construct date from components:

operation: DATE
year: $jaar
month: 1
day: 1

Date: DAY_OF_WEEK — get weekday (0=Monday, 6=Sunday):

operation: DAY_OF_WEEK
date: $datum

Collection: LIST — construct an array:

operation: LIST
items:
  - $item_1
  - $item_2
  - "literal_value"

Hooks — Reactive Execution (AWB cross-cutting concerns)

Hooks allow articles (typically from the AWB) to fire automatically when matching lifecycle events occur. Used for cross-cutting legal requirements like motivation obligations and appeal deadlines.

machine_readable:
  hooks:
    - hook_point: pre_actions    # or post_actions
      applies_to:
        legal_character: BESCHIKKING
        stage: BESLUIT           # optional: AANVRAAG, BEHANDELING, BESLUIT, BEKENDMAKING, BEZWAAR
  execution:
    output:
      - name: motivering_vereist
        type: boolean
    actions:
      - output: motivering_vereist
        value: true

Overrides — Lex Specialis Declarations

When a specific law overrides a general law's output (e.g., Vreemdelingenwet overriding AWB's appeal deadline):

machine_readable:
  overrides:
    - law: algemene_wet_bestuursrecht
      article: '6:7'
      output: bezwaartermijn_weken
  execution:
    output:
      - name: bezwaartermijn_weken
        type: number
    actions:
      - output: bezwaartermijn_weken
        value: 4

Procedures — AWB Lifecycle Stages (top-level)

Procedures define the lifecycle stages for administrative decisions. They are declared at the top level of the YAML file (not inside articles):

procedure:
  - id: beschikking
    default: true
    applies_to:
      legal_character: BESCHIKKING
    stages:
      - name: AANVRAAG
        description: Belanghebbende dient aanvraag in (AWB 4:1)
        requires:
          - name: aanvraag_datum
            type: date
      - name: BEHANDELING
        description: Bestuursorgaan onderzoekt de aanvraag (AWB 3:2)
      - name: BESLUIT
        description: Bestuursorgaan neemt besluit (AWB 1:3)
      - name: BEKENDMAKING
        description: Besluit wordt bekendgemaakt (AWB 3:41)
      - name: BEZWAAR
        description: Bezwaarperiode (AWB 6:4 e.v.)

Produces — Legal Character and Decision Type

Articles that produce binding decisions should declare what they produce:

execution:
  produces:
    legal_character: BESCHIKKING    # BESCHIKKING | TOETS | WAARDEBEPALING |
                                    # BESLUIT_VAN_ALGEMENE_STREKKING | INFORMATIEF
    decision_type: TOEKENNING       # TOEKENNING | AFWIJZING | GOEDKEURING |
                                    # GEEN_BESLUIT | ALGEMEEN_VERBINDEND_VOORSCHRIFT |
                                    # BELEIDSREGEL | VOORBEREIDINGSBESLUIT |
                                    # ANDERE_HANDELING | AANSLAG
    procedure_id: beschikking_uov   # optional: selects specific procedure variant

Cross-Law References (source)

Input fields reference other laws via source. Use regulation + output, NOT url:

input:
  - name: toetsingsinkomen
    type: amount
    source:
      regulation: algemene_wet_inkomensafhankelijke_regelingen
      output: toetsingsinkomen
      parameters:
        bsn: $bsn
    type_spec:
      unit: eurocent

For internal references (same law, different article), omit regulation:

input:
  - name: vermogen_onder_grens
    type: boolean
    source:
      output: vermogen_onder_grens

For delegated values (filled by lower regulations via IoC), the higher law declares an open_term and the engine resolves it automatically:

# Higher law declares the open term
machine_readable:
  open_terms:
    - id: verlaging_percentage
      type: number
      required: true
      delegated_to: gemeenteraad
      delegation_type: GEMEENTELIJKE_VERORDENING
  execution:
    output:
      - name: verlaging_percentage
        type: number
    actions:
      - output: verlaging_percentage
        value: $verlaging_percentage

Binding purity — NEVER leave a cross-law input as a plain-param placeholder

Every input that references a concept owned by another legal provision MUST carry a real source: block. A description is documentation, not a binding — it does not make the engine resolve anything.

Forbidden pattern: an input whose description names another regulation, or uses words like "conceptueel", "forward naar", or "tijdelijk als directe parameter", but has NO source: block. This is a plain-param placeholder: it silently turns a cross-law value into a free input the caller must supply by hand, and real cross-document resolution never happens. If the target law does not yet produce the needed output, FIRST add that output to the target law (a machine_readable action on the correct article), then bind to it — do not leave the reference stranded in a description.

Never use "the engine cannot resolve multiple source bindings per article" as a reason to fall back to a plain param. That assumption is false: schema v0.5.2 supports multiple source: bindings per article, and they resolve fine. When in doubt, bind for real and prove it with a BDD scenario.

Section placement — a source: MUST live under input:, NEVER under parameters:. This is the single most common way a binding looks real but silently does nothing. The engine has two distinct structs: Parameter (the items under parameters:) has no source field, while Input (the items under input:) is the only one that carries source. A source: block placed under parameters: is therefore dropped at parse time — the value degrades to a plain caller-supplied parameter and cross-law resolution never fires. It will still "pass" any BDD scenario that injects the value directly, which hides the defect. Rule of thumb:

• The cross-law-resolved value (the thing the other law produces) → declare under input: with its source:.
• The leaf parameters that FEED that binding's source.parameters mapping → stay under parameters: as direct inputs.

A binding only truly resolves when its input: entry is reached AND no overriding parameter of the same name is supplied. Verify with a BDD scenario that loads the target law and sets the leaf inputs (not the bound value), then asserts the dependent output flips.

Name-mismatch rule: if the local input name differs from the target output name, put the target's output name in source.output and the local name in name, and note the difference in the description:

input:
  - name: lokaal_inkomen           # local name used by this article's logic
    type: amount
    description: "bindt aan output 'toetsingsinkomen' van de andere regeling (naam wijkt af)"
    source:
      regulation: algemene_wet_inkomensafhankelijke_regelingen
      output: toetsingsinkomen     # the name the TARGET law actually produces
    type_spec:
      unit: eurocent

Field Types

Context	Valid types
parameters	string, number, boolean, date
input	string, number, boolean, amount, object, array, date
output	string, number, boolean, amount, object, array, date

For monetary values, use type: amount with type_spec: { unit: eurocent }.

$referencedate Is NOT a Built-in Variable

$referencedate is NOT automatically available. It must be declared as a parameter with type: date if used. The engine resolves it from whatever the caller passes for that parameter name. Some corpus files use it as a convention, but it has no special status in the engine.

When to Skip Articles

Skip articles that have no computable output. Heuristics for non-computable articles:

• Pure definitions — "In deze wet wordt verstaan onder..." (definition articles)
• Procedural — describes who must do what, deadlines for filing, appeal procedures
• Delegation — "Bij of krachtens algemene maatregel van bestuur worden regels gesteld..." (delegates to AMvB without computable logic)
• Scope/applicability — "Deze wet is van toepassing op..." (unless it has testable conditions)
• Transitional provisions — "overgangsrecht" articles about old-to-new transitions

Articles that SHOULD be made executable:

• Eligibility checks ("heeft recht op ... indien")
• Calculations ("bedraagt", "wordt berekend", "vermenigvuldigd met")
• Thresholds ("niet meer dan", "ten minste")
• Conditional amounts (IF patterns based on categories)
• Age-dependent rules ("de leeftijd van X jaar heeft bereikt")
• Deadline calculations ("binnen X weken na")

Untranslatables — When to Flag Instead of Approximate (RFC-012)

When the engine's operation set cannot faithfully express a legal construct, do NOT approximate. Instead, add an untranslatables entry and skip the inexpressible part.

Flag as untranslatable when you encounter:

• Rounding — "afronden", "naar boven afgerond", "afgerond op hele euro's"
• Aggregation over collections — "het totaal van", "de som van" over a variable-length set
• Table/bracket lookups — multi-dimensional tables that would need >8 IF cases
• Date differences — "het aantal maanden/jaren tussen X en Y"
• String manipulation — concatenation, pattern matching, substring extraction
• Domain-specific formulas — "berekend volgens de actuariële methode"
• Ambiguous conditions — "redelijke termijn", "zo spoedig mogelijk"

Format:

machine_readable:
  untranslatables:
    - construct: "afronden op hele euro's"
      reason: "Rounding is not available as an engine operation"
      suggestion: "Add ROUND/CEIL/FLOOR operation to engine"
      legal_text_excerpt: "Het bedrag wordt naar boven afgerond op hele euro's"
      accepted: false
  execution:
    # Only the parts that CAN be expressed

Required fields: construct, reason. Optional: suggestion, legal_text_excerpt, accepted (boolean, default false — set true only after human review).

Rules:

• Do NOT build a 10+ case IF tree to simulate a table lookup
• Do NOT use arithmetic tricks to approximate rounding
• Do NOT hardcode pre-computed aggregation results
• An article CAN have both untranslatables AND execution — flag what you can't express, implement what you can

Other Rules

• Convert monetary amounts to eurocent (€100 = 10000)
• Use $variable references for inter-action dependencies
• subject in comparisons MUST be a $variable, never a nested operation
• Operations can be nested: a value in an arithmetic array can itself be an operation
• endpoint on machine_readable makes an article callable from other regulations

Available Operations

Category	Operations
Arithmetic	ADD, SUBTRACT, MULTIPLY, DIVIDE, MIN, MAX
Comparison	EQUALS, GREATER_THAN, LESS_THAN, GREATER_THAN_OR_EQUAL, LESS_THAN_OR_EQUAL
Logical	AND, OR, NOT
Membership	IN
Conditional	IF (with cases/default)
Collection	LIST
Date	AGE, DATE_ADD, DATE, DAY_OF_WEEK

Common Legal Text → Operation Mappings

Legal Text	Operation
"heeft bereikt de leeftijd van 18 jaar"	AGE + GREATER_THAN_OR_EQUAL, value: 18
"niet meer bedraagt dan X"	LESS_THAN_OR_EQUAL
"ten minste X"	GREATER_THAN_OR_EQUAL
"indien ... en ..."	AND with conditions array
"indien ... of ..."	OR with conditions array
"niet ..." / "tenzij"	NOT wrapping the positive condition
"gelijk aan"	EQUALS
"vermenigvuldigd met"	MULTIPLY with values array
"verminderd met"	SUBTRACT with values array
"vermeerderd met"	ADD with values array
"binnen X weken na"	DATE_ADD with weeks
"in afwijking van artikel X"	overrides declaration

Phase 1.5: Capture BDD Baseline

Before modifying the law file, capture the current BDD state so you can distinguish pre-existing failures from newly introduced ones:

just bdd 2>&1 | tail -100

Note the summary line and any pre-existing failures. This baseline is your reference for all subsequent Phase 3 runs.

Phase 2: Validate (with repair sub-loop)

Run validation:

just validate <file_path>

• If OK → proceed to Phase 3
• If errors → Repair (up to 2 rounds per iteration):
  1. Read error output, identify broken articles/fields
  2. Fix with Edit tool
  3. Re-run just validate
  4. If still failing after 2 repair rounds: stop and report the validation errors to the user. Do NOT proceed to Phase 3 with invalid YAML — BDD tests against a schema-invalid file will produce misleading failures that look like logic bugs, wasting iterations on the wrong problem.

Phase 3: Run BDD Tests

Run the Gherkin scenarios against the machine_readable logic:

just bdd

This runs ALL feature files (in features/) including any generated by /law-mvt-research. The command is equivalent to:

cd packages/engine && cargo test --test bdd -- --nocapture

Important: Only investigate failures that are NEW compared to the baseline. Pre-existing failures from other laws are not your problem — do not attempt to fix them.

Creating New Step Definitions

If the feature file uses Given/When/Then steps that don't exist yet, you must add them before running just bdd. The BDD harness lives in:

packages/engine/tests/bdd/
├── main.rs              # Test runner (finds features/, runs cucumber)
├── world.rs             # RegelrechtWorld state struct
├── steps/
│   ├── mod.rs           # Module exports
│   ├── given.rs         # Setup steps (data input)
│   ├── when.rs          # Action steps (law execution)
│   └── then.rs          # Assertion steps (output checks)
└── helpers/
    ├── regulation_loader.rs  # Loads all YAML from corpus/regulation/nl/
    └── value_conversion.rs   # Gherkin string → Value conversion

Adding a Given Step (data setup)

For simple parameter tables (| key | value |), reuse the existing step:

Given a citizen with the following data:
  | leeftijd | 35 |
  | inkomen  | 2000000 |

For external data sources (RVIG, Belastingdienst, etc.), reuse existing steps like:

Given the following RVIG "personal_data" data:
  | bsn | geboortedatum | land_verblijf |
  | 999993653 | 1990-01-01 | NEDERLAND |

If a new external data source is needed, add a step in steps/given.rs following the existing pattern.

IMPORTANT: All BDD steps MUST be synchronous fn, NOT async fn. The cucumber-rs harness in this project uses synchronous world execution. Using async fn will compile but cause runtime panics or silent test hangs.

#[given(regex = r#"the following NEWSOURCE "newsource_field" data:"#)]
fn set_newsource_data(world: &mut RegelrechtWorld, step: &Step) {
    if let Some(table) = &step.table {
        parse_external_data_table(table, &mut world.external_data.newsource_field);
    }
}

And add the corresponding field to ExternalData in world.rs:

pub struct ExternalData {
    // ... existing fields ...
    pub newsource_field: HashMap<String, HashMap<String, Value>>,
}

Adding a When Step (law execution)

Each law needs a When step that triggers execution. Use concrete law names in the regex, not placeholders. All steps are synchronous fn. Example from the actual bijstand step:

#[when(regex = r"^the bijstandsaanvraag is executed for participatiewet article (\d+)$")]
fn execute_bijstand(world: &mut RegelrechtWorld, _article: String) {
    // Register any external data sources if this law uses them
    register_if_present(&mut world.service, "rvig_personal_data", &world.external_data.rvig_personal_data);

    // Execute the law for the desired output
    world.execute_law("participatiewet", "bijstandsnorm");
}

The register_if_present helper (already defined in when.rs) takes 3 arguments:

fn register_if_present(
    service: &mut regelrecht_engine::LawExecutionService,
    name: &str,
    data: &std::collections::HashMap<String, std::collections::HashMap<String, Value>>,
)

Adding a Then Step (assertions)

For checking output values — use the concrete output name in the regex:

#[then(regex = r#"^the my_output is "(-?\d+)" eurocent$"#)]
fn assert_my_output(world: &mut RegelrechtWorld, expected: String) {
    assert!(world.is_success(), "Expected success, got error: {:?}", world.error_message());
    let expected_amount: i64 = expected.parse().expect("Invalid eurocent value (must be integer, may be negative)");
    let actual = world.get_output("my_output");
    match actual {
        Some(Value::Int(n)) => assert_eq!(*n, expected_amount),
        Some(Value::Float(f)) => assert_eq!(f.round() as i64, expected_amount),
        _ => panic!("Expected number, got {:?}", actual),
    }
}

For boolean checks:

#[then("the citizen has the right to my_benefit")]
fn assert_has_right(world: &mut RegelrechtWorld) {
    assert!(world.is_success());
    let output = world.get_output("heeft_recht");
    assert!(matches!(output, Some(Value::Bool(true))), "Expected true, got {:?}", output);
}

Key World Methods

• world.execute_law(law_id, output_name) — runs the engine, stores result/error
• world.get_output(name) — retrieves a named output from the last result
• world.is_success() — true if execution succeeded
• world.error_message() — error string from last failed execution (Option<String>)
• world.parameters — HashMap<String, Value> for simple inputs
• world.external_data — ExternalData struct with fields: rvig_personal, rvig_relationship, rvz_insurance, bd_box1, bd_box2, bd_box3, dji_detenties (each HashMap<String, HashMap<String, Value>>)

Prefer Reusing Existing Steps

Before creating new steps, check if existing patterns cover your case. Read the existing step files first:

• packages/engine/tests/bdd/steps/given.rs
• packages/engine/tests/bdd/steps/when.rs
• packages/engine/tests/bdd/steps/then.rs

Many scenarios can be expressed using the existing generic steps. Only add new steps when the law requires a genuinely different execution pattern or data source.

If no MvT feature file was generated

Fall back to ad-hoc testing: for each article with execution.output, build the evaluate binary and pipe a JSON payload to it:

cargo build --manifest-path packages/engine/Cargo.toml --bin evaluate --release

Important: Do NOT use echo to pipe JSON — Dutch law YAML contains quotes, newlines, and special characters that will break shell escaping. Instead, use the Write tool to create a temp file, then pipe from it:

cat /tmp/eval_payload.json | ./target/release/evaluate

The JSON payload format (written to the temp file):

{
  "law_yaml": "<full YAML content of the law file>",
  "output_name": "heeft_recht",
  "params": {"bsn": "123456789", "peildatum": "2025-01-01"},
  "date": "2025-01-01",
  "extra_laws": []
}

Cross-law Dependencies

• If the law references other laws via source.regulation, find those law files in corpus/regulation/nl/ and include their YAML content in extra_laws:

  "extra_laws": [
    {"id": "wet_op_de_zorgtoeslag", "yaml": "<content>"}
  ]
  

• Use Glob to find referenced law files

Phase 4: Iterate (up to 3 total iterations)

• All BDD scenarios pass → proceed to Phase 5
• Failures → analyze each failure:
  • Logic bug in machine_readable: fix the YAML actions/operations
  • Wrong step definition: fix the BDD step code
  • NEVER change the expected values in MvT-derived scenarios — these are the legislature's intended outcomes and serve as ground truth
  • Go back to Phase 2 (validate → test again)
• After 3 iterations: stop and report remaining issues. Each iteration includes its own Phase 2 validation cycle (up to 2 repair rounds per iteration). For large laws (>20 articles), this limit applies per batch — each batch of ~15 articles gets its own 3-iteration budget

Phase 4.5: Write the related-legislation result envelope

After the machine_readable sections are final, write a sibling result envelope so the pipeline can auto-harvest the legislation this law depends on (delegated regelingen and cross-law references the extref-only harvester misses).

Write it next to the law YAML as .enrichment-result.yaml (same directory, e.g. corpus/regulation/nl/wet/wet_op_de_zorgtoeslag/.enrichment-result.yaml). Use the Write tool — no new agent tools are needed.

# .enrichment-result.yaml — result envelope, NOT part of the law schema
law_id: wet_op_de_zorgtoeslag
related_legislation:
  - name: Regeling vaststelling standaardpremie en bestuursrechtelijke premie
    relation: delegated_regeling      # source_regulation | legal_basis | delegated_regeling
    bwb_id: BWBR0037841               # optional, best-effort
    slug: regeling_standaardpremie    # optional, best-effort
    open_term: standaardpremie        # optional, only for delegations
  - name: Algemene wet inkomensafhankelijke regelingen
    relation: source_regulation

Coverage: add one entry for every source.regulation you bound, every legal_basis you anchored on, and every open_term delegation you declared. Fields:

• name — required; the human-readable law/regeling title (used for search fallback when no id/slug is given).
• relation — one of source_regulation, legal_basis, delegated_regeling.
• bwb_id, slug, open_term — optional, best-effort. Supply what you know (a known bwb_id resolves fastest); leave the rest out.

CRITICAL — this MUST NOT go in the law YAML. The law file stays strictly schema-conformant (just validate must still pass). The related-legislation list lives only in the .enrichment-result.yaml sidecar, which the pipeline reads separately. Do not add a related_legislation: key anywhere inside the law YAML.

Phase 5: Report

Report to the user:

Interpreted {LAW_NAME}

  Articles processed: {TOTAL}
  Made executable: {EXECUTABLE_COUNT}
  Validation: {PASSED/FAILED}

  BDD scenarios: {PASS}/{TOTAL} passing
  (from MvT feature file and/or ad-hoc evaluate tests)

  Iterations needed: {N}

  Untranslatables: {N} construct(s) in {N} article(s)
  - Article {N}: {construct} — {reason}

  Remaining issues:
  - {description of any unresolved failures}

  TODOs:
  - {external laws that need to be downloaded/implemented}
  - Review untranslatables and set accepted: true for verified gaps