Concepts

Evidence

An event is easier to audit when its timestamp and source record can be checked against the supporting artifacts that actually exist.

The intended Praxis event model can refer to supporting artifacts generated or retained when a rule fires. Availability depends on the implementation, capture settings, and retention policy. An event record by itself is not proof that every artifact below exists.

The current challenge is narrower. Its prepared static event rows contain a timestamp, normalized position, and track ID. Prepared detections and per-frame zone geometry are separate files. It does not publish per-event crops, version records, or a durable evidence API.

Possible supporting artifacts#

Artifact	Contents
`crop`	Frame crop of the object at fire time, with the detection box
`track_history`	The retained position history available before and at the event
`zone_geometry`	The zone polygon as registered on that exact frame
`context`	Feed ID, frame index, timestamp, rule and runtime versions

A retained zone-geometry artifact can record the polygon used for a particular frame. The challenge publishes prepared geometry for every frame in one static file, rather than a separate evidence object attached to each entry.

Replay as proof#

The challenge replay loads the clip plus prepared static detections, per-frame zone geometry, and scored entry rows. It draws those records over the footage and shows a timestamped log. This makes the prepared result inspectable, but it is not a live event stream or a hosted evidence store.

When evaluating a result, ask which source files and per-event artifacts are available, how they were prepared, and how long they are retained.