Source Records

Scope Fields

Jurisdiction and date are part of the model input, not afterthoughts. Honesty note: jurisdiction US; the pinned first step states the as-of date; not legal advice; code encodes the stated-rule interpretation.

highlighted = computed this step

Render honesty note

Honesty note: jurisdiction US; as of 2026-06-24; not legal advice; code encodes the stated-rule interpretation for this lesson.

US as of 2026−06−24\text{US as of }2026-06-24

Scope is part of the rule model

The source model is tied to explicit scope fields. Jurisdiction and as-of date are inputs, and this lesson uses as-of date 2026-06-24.

as-of=2026−06−24\text{as-of}=2026-06-24

Example data has two fields

The example has a jurisdiction field and an as-of field. The rendered graph keeps those fields separate before they define the scoped model.

jurisdiction field plus date field\text{jurisdiction field plus date field}

Changing scope changes the model

The scoped graph is recomputed from 3 nodes and 2 directed edges. No prior result is reused across a different scope.

nodes=3,edges=2\text{nodes}=3,\quad \text{edges}=2

Diagram note

The diagram is a scope check, not a legal conclusion. It shows which input fields define the model boundary.

scope fields define model boundary\text{scope fields define model boundary}

Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes the stated-rule interpretation.

Scope fieldsjurisdiction->model definesdate->model definesAs of fieldid date in0 out1 deg1 reach1Jurisdiction fieldid jurisdiction in0 out1 deg1 reach1Scoped modelid model in2 out0 deg2 reach0