Evidence
Mission Studio keeps the result video, exact event frames, track observations, run manifest, and checksums together so an operator can inspect how a result was produced.
A completed Mission Studio run remains more than a count. Each matching event links to its time, source frame, stable track, confidence, and evidence image. The result timeline, event list, raw comparison, and exported files all read from the same retained manifest.
Files retained by Mission Studio#
| Artifact | What it contains |
|---|---|
| Annotated result | The complete playable source with boxes, identities, the marked area, and events |
| Event reel and frames | A condensed replay plus one evidence image for every matching event |
| Event and track tables | CSV rows for matching events and normalized identity observations |
| Run manifest | Source digest, objective, geometry, builds, stage metrics, events, reviews, and artifact checksums |
| Evidence Pack | A ZIP containing the complete run, its data exports, event frames, and manifest |
Operator review does not replace an event. Confirmed, not relevant, or unsure is appended to the manifest with the optional note and review time. Mission Studio then rebuilds the Evidence Pack so the review travels with the original result.
Track histories#
Follow this person reconstructs one selected identity from the retained observations. If the operator confirms that two separated track segments belong to the same subject, the correction preserves the source track IDs and records the linked segments instead of rewriting history.
Retention, sharing, and the Challenge boundary#
Each project sets the retention window for its uploads, results, and generated artifacts. The owner can delete a run earlier. Share creates a separate read-only link that expires, can be revoked, and does not allow reviews, rebuilds, or deletion. Artifact URLs are signed and expire independently of the owning run.