Rule Models
Fact Record
A rule model should receive explicit fact inputs. 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.
Structured Visual
Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes a stated structural model, not the law itself. RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF.
RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF: render structure, refuse interpretation, cite provenance, abstain when unsupported, and hand off to human review.
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.
Facts are model inputs
The stated rule asks for notice and timing facts. A rule model should receive those facts explicitly.
Example data can be incomplete
In the toy data, the notice fact is present and the timing fact is missing. Missing data stays visible instead of being guessed.
The trace preserves unknowns
This trace has 2 rows and 1 unknown row.
Diagram note
The diagram is an input audit. It tells the reader which fact row is known and which one remains unknown.
Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes a stated structural model, not the law itself. RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF.
RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF: render structure, refuse interpretation, cite provenance, abstain when unsupported, and hand off to human review.
Narrow summary
Do not hide assumptions in code; make each fact value or missing value an explicit row.