Rule Models

Exceptions

An exception can be modeled as its own expected-absence prong. 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

Exceptions are separate rows

A stated rule with an exception should not hide the exception inside prose. The exception becomes its own row where absence is required.

exception row explicit\text{exception row explicit}

Example exception data

The base prong is present in the toy data, and the exception fact is also present. That creates a separate exception row in the trace.

base plus exception fact\text{base plus exception fact}

The row changes the trace

In this classroom model, the exception prong expects absence. When the exception fact is present, 1 row is not satisfied.

not satisfied rows=1\text{not satisfied rows}=1

Diagram note

The diagram shows base and exception rows separately. It does not decide any real-world defense or exception.

exception trace only\text{exception trace only}

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

Exception prong trace base: satisfied via base=True compare=True exception: not_satisfied via exception=True compare=False

Narrow summary

Exception logic is safer when the exception row is visible and reviewable.

visible exception row\text{visible exception row}