Statute Slices
Amendment and Version Slice
Version slices depend on effective and end dates. Honesty note: simplified statutory-data model; source text, version, and as-of date matter; the pinned first step states the as-of date; jurisdictions vary; not legal advice.
Structured Visual
Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes the stated structural model, not the law itself.
RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF: render structure, refuse interpretation, cite provenance, abstain when unsupported, and hand off to human review.
Statutory data honesty note
Honesty note: simplified statutory-data model; source text, version, and as-of date matter; as of June 24, 2026; jurisdictions vary; not legal advice; code encodes a stated structural model, not the law itself.
Version slices depend on dates
The stated process compares effective and end dates against the as-of date. It does not decide which text governs a real dispute.
Example old and new units
A new unit effective January 1, 2026 follows an old unit ending December 31, 2025.
The as-of filter recomputes active rows
At the as-of date, the slice has 2 active units and 1 inactive unit.
Diagram note
The diagram shows active and inactive version rows for the toy model only. Source version must still be checked in real research.
Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes the stated structural model, not the law itself.
RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF: render structure, refuse interpretation, cite provenance, abstain when unsupported, and hand off to human review.
Summary
Version slices are safer when old text, new text, effective dates, end dates, and as-of date are all visible.