Rule Models

Trace, Not Advice

A computed trace is input for human review, not legal advice. Honesty note: US classroom stated-rule model; the pinned first step states the as-of date; not legal advice; code encodes an interpretation of a stated rule, not the law itself.

highlighted = computed this step

Rules as code honesty note

Honesty note: US classroom stated-rule model; as of 2026-06-24; not legal advice; code encodes an interpretation of a stated rule, not the law itself.

classroom model as of 2026−06−24\text{classroom model as of }2026-06-24

Trace captions need discipline

A rule-model pipeline should label the output as a trace, not as advice or a legal conclusion.

trace label discipline\text{trace label discipline}

Example handoff packet

The packet begins with a stated source, then fact inputs, then a rule trace, then human review.

source facts trace review\text{source facts trace review}

The flow governs the handoff

The pipeline ends at human review. This map has 4 nodes and no legal conclusion.

map nodes=4\text{map nodes}=4

Diagram note

The diagram is a review pipeline. The final node is human review, not an automated answer.

review pipeline only\text{review pipeline only}

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

Trace, not adviceTrace, not advicescope: US classroom model | Human review classroom model | as of 2026-06-24Not legal advice; code encodes an interpretation of a stated rule, not the law itself.pinevaluatereviewStated sourcerole start r0 in0 out1 reach3Fact inputsrole step r1 in1 out1 reach2Rule tracerole step r2 in1 out1 reach1Human reviewrole terminal r3 in1 out0 reach0SCC: scc3:source; scc2:facts; scc1:trace; scc0:review

Narrow summary

A legal rules-as-code lesson should show the trace and its caveats before it is used downstream.

trace before use\text{trace before use}