Proof Models

Chain of Custody Flow

Chain of custody can be modeled as a sequence of event records. Honesty note: simplified evidence and proof model; jurisdictions and rules vary; 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.

Simplified chain of custody event flowSimplified chain of custody event flowscope: US classroom evidence model | Chain of custody event model | as of 2026-06-24Simplified evidence and proof model; jurisdictions and rules vary; not legal advice; codeencodes a stated structural model, not the law itself.Item loggedCollection eventSeal eventTransfer eventStorage eventHuman reviewedge=item->collect label=recordedge=collect->seal label=recordedge=seal->transfer label=recordedge=transfer->store label=recordedge=store->review label=reviewSCC: scc5:item; scc4:collect; scc3:seal; scc2:transfer; scc1:store; scc0:review
highlighted = computed this step

Evidence model honesty note

Honesty note: simplified evidence and proof model; jurisdictions and rules vary; as of June 24, 2026; not legal advice; code encodes a stated structural model, not the law itself.

evidence model as of June24,2026\text{evidence model as of }June 24, 2026

Custody is modeled as events

The stated process treats custody as an ordered event chain: item logged, collection, seal, transfer, storage, and human review.

event chain before review\text{event chain before review}

Example custody data

The toy file records a collected item, a seal event, a transfer event, and a storage event before review.

collect to seal to transfer to storage\text{collect to seal to transfer to storage}

The flow recomputes structure

The procedure flow recomputes 6 nodes and 5 edges from the authored event graph.

nodes=6,edges=5\text{nodes}=6,\quad \text{edges}=5

Diagram note

The diagram shows custody event order. It does not decide reliability, completeness, or an evidence ruling.

event order only\text{event order only}

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.

Simplified chain of custody event flowSimplified chain of custody event flowscope: US classroom evidence model | Chain of custody event model | as of 2026-06-24Simplified evidence and proof model; jurisdictions and rules vary; not legal advice; codeencodes a stated structural model, not the law itself.Item loggedCollection eventSeal eventTransfer eventStorage eventHuman reviewedge=item->collect label=recordedge=collect->seal label=recordedge=seal->transfer label=recordedge=transfer->store label=recordedge=store->review label=reviewSCC: scc5:item; scc4:collect; scc3:seal; scc2:transfer; scc1:store; scc0:review

Summary

A custody map helps reviewers see the event path and the handoff point without turning the path into a legal conclusion.

path plus handoff\text{path plus handoff}