Liability Models
Duty Scope Label
Duty scope can be stored as actor, claimant, context, jurisdiction, and as-of labels. Honesty note: simplified classroom tort model; jurisdictions vary; contested facts and standards matter; the pinned first step states the as-of date; 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.
Tort model honesty note
Honesty note: simplified classroom tort model; jurisdictions vary; contested facts and legal standards matter; as of June 24, 2026; not legal advice; code encodes a stated structural model, not the law itself.
Duty scope is a label record
The stated process stores actor, claimant, context, jurisdiction, and as-of labels. The source label is Toy Tort Record 1.
Example scope fields
The toy record names a system operator, a visitor, a sidewalk context, and a classroom jurisdiction label.
The table recomputes tokens
Duty scope is modeled as record data, not a conclusion. This table has 1 record and 12 recomputed tokens.
Diagram note
The diagram is a scope-label record. It does not decide whether a duty exists in any real matter.
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
Scope labels make later review inspectable because the actor, claimant, context, and jurisdiction slots are visible.