law_rules
Read-only
The rules of formalised law put into words: exactly how a predicate is derived (premises, source articles). Call this BEFORE supplying facts to law_ask — the rules say which facts are needed instead of leaving them to be guessed. For large instruments package=… returns a table of contents; the full text comes from predicate=…. The listing by package is paged: limit (20 by default, 500 at most) and offset; the remainder is named in the text (showing a–b of N; k more) and in structuredContent (total, truncated, next — a ready-made continuation call).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | the language the rules are put into (DECISION-0032; the language of the profile by default; the rest are draft packs, with §218 label overlays) | |
| limit | No | package: how many rules per page (20; the budget may lower it) | |
| offset | No | package: from which rule (0) | |
| package | No | every rule of the instrument | |
| predicate | No | the rules that derive this predicate |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| next | No | ||
| limit | No | ||
| rules | Yes | ||
| total | No | ||
| offset | No | ||
| compact | No | ||
| package | Yes | ||
| ruleCount | No | ||
| truncated | No | ||
| factsTemplate | No | ||
| verbalizationGaps | No |