Statute Slices
Subsection Path
Parent ids produce subsection paths and depths. 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.
Parent ids define the path
The stated process does not hand-author a path. It uses parent ids to place a child unit under its section.
Example parent and child
The slice has 2 units. The child unit is Toy Code sec. 10(a).
The compiler derives depth and path
The subsection path is recomputed from parent ids. The slice has 2 units, and the child depth is 1. The derived path is sec. 10/(a).
Diagram note
The diagram shows hierarchy metadata. It does not decide what the subsection means.
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
Subsection paths should be derived from the tree, so the displayed path can be audited from parent links.