Liability Models
AI Incident Handoff
AI incident records should preserve evidence packets for review. 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.
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.
AI incident records need a handoff path
The stated process captures system, event, claimed harm, use label, evidence packet, and human review as separate records.
Example incident packet
The toy packet separates the AI system from the event record and from the claimed harm label.
The flow preserves review order
An AI incident handoff keeps system, event, claimed harm, use label, and evidence separate. The map has 6 nodes.
Diagram note
The diagram is an evidence handoff map. It does not decide cause, fault, or case result.
Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes the stated structural model, not the law itself.
Summary
AI incident data should preserve provenance and evidence packets before any tort analysis happens.