openregs atomize
Propose obligation atoms from a unit, on a branch, for a human to review.
Read a unit of the canon as it stood on a date, ask an extraction model what duties it states, verify every quotation against the real text, and stage the result as atom files on a branch with a generated pull-request description. Nothing is written to the working tree and nothing becomes canon: the model proposes and a person decides, which is what the branch is for. An eId names one text only once a date is beside it, so —as-of chooses the Expression and every offset indexes that text.
openregs atomize [-h] --unit <work-iri> --eid <eId> --model <name> --as-of <date> [--regime <name>] [--canon <path>] [--root <path>] [--remote <path>] [--branch <name>] [--base <name>] [--at <timestamp>] [--dry-run]| Option | |
|---|---|
--unit <work-iri> | the act to read, by Work IRI, for example /akn/eu/act/reg/2024/1 (required) |
--eid <eId> | the unit to propose atoms from; repeat for several (required, repeatable) |
--model <name> | which extraction model to ask (fixture-model) (required) |
--as-of <date> | the day whose text to read, ISO 8601 (YYYY-MM-DD) (required) |
--regime <name> | which regime’s canon and atoms (default: the checkout’s only regime) |
--canon <path> | read this canon directory instead of regimes/<regime>/canon |
--root <path> | read regimes/ under this directory instead of the checkout |
--remote <path> | the repository to push the proposal branch to (default: this checkout) |
--branch <name> | override the branch name (default: atomize/<unit>/<as-of>) |
--base <name> | branch to propose against (default: the remote’s current branch) |
--at <timestamp> | commit timestamp (default: the base commit’s own, so runs are reproducible) |
--dry-run | print the atoms and the request body; touch no repository |
Rendered from openregs/openregs@cbe9615:tooling/openregs/cli/main.py