Evidence & audit · defensible alerts

An alert is only useful if it can be defended.

A VESU incident gives the operator more than a label. It shows the observed condition, the region, the coverage state, the clip or keyframes, the explanation, and the evidence timeline that made the alert publishable. If the operator opens the incident, the important context is already there.

01 · The evidence package

One incident. One record. Everything the operator needs.

Schematic artifact. Sanitized fields.

incident_pkg · STOPPED_VEHICLE · PUBLISHED schematic
STAGE 3 · VERIFICATION CLIP
STAGE 0 · t=0 · health OK
STAGE 1 · t=5s · vehicle in shoulder
STAGE 1 · t=10s · vehicle in shoulder
STAGE 1 · t=30s · vehicle still in shoulder
STAGE 2 · t=50s · candidate · persistence met
STAGE 3 · t=51s · verified · sev medium
PUBLISH · t=51.4s · delivered to ATMS
Plain-English reason

"White sedan stationary on the right shoulder for 50 seconds. Traffic flowing in all lanes. View is clear; camera healthy."

provenance
incident_id illustrative
class stopped_vehicle
region shoulder · learned
coverage_state monitored & clear
scene_model_ver scn-2026.04
strategy_ver str-2026.05-a
prompt_ver p-2026.05.02
schema_ver incident.v3
gate_policy gp-2026.04
source_media media chain · verified
02 · Media integrity

One media chain. Three views of it.

The frames that triggered perception, the clip used for verification, and the incident report all point back to the same media lineage. We do not explain alerts with media that is not the media the system reasoned over.

SOURCE MEDIA recorded segment STAGE 1 sampled frames STAGE 3 verification clip INCIDENT evidence in report ALL THREE POINT BACK TO THE SAME MEDIA CHAIN A review months later can reconstruct what VESU saw — exactly.
03 · Replay

Reproduce past decisions. Test changes without rewriting history.

If a strategy, prompt, model, schema, or scene model changes, VESU can still reconstruct what version produced any past alert. Replay is how the system improves without losing the past.

01
Reconstruct

Given an incident ID, the system can re-run the exact strategy, prompt, schema, and scene-model versions that produced it.

02
Compare

A candidate strategy can be run against a corpus of recorded incidents to see what it would have changed — before any operator sees it.

03
Promote

A change reaches operators only after replay gates pass. Promotion is evidence-based, not intuition-based.

04 · Public-sector posture

Designed for audit, retention, and access.

Public-sector traffic operations require disciplined evidence. VESU is designed around audit-discoverable records, role-based evidence access, configurable retention policies, and discoverable incident histories.

01
Audit-discoverable

Every alert is queryable by date, camera, class, and outcome — with the full evidence package.

02
Access controls

Evidence access is role-based. Operators, supervisors, and external reviewers see what they should.

03
Retention policies

Configurable per agency: clip retention, evidence retention, derived-data retention.

04
Versioned context

Every output ships with the strategy/model/schema versions that produced it. The record outlives the model.

Trust is not a single feature.

It is media integrity, provenance, replay, and access control combined. We are happy to walk through the evidence model for the kind of disputes your agency has had to defend.