Docs
Getting started

How Praxis works

Mission Studio runs a five-stage video pipeline. The source stays visible while Praxis detects subjects, preserves identity, applies one operator rule, and retains every matching moment.

The public Mission Studio accepts MP4, MOV, M4V, and WebM files up to 60 seconds and 80 MB. Uploaded sources and completed results expire after 24 hours.
1
Read video
The source is validated, stripped of audio, normalized for processing, and retained with its dimensions, frame rate, duration, byte size, and SHA-256 digest.
2
Detect
YOLO11 runs on sampled frames for the subject family selected by the operator: people, vehicles, people and vehicles, bicycles, boats, or animals. The live stage reports sampled frames and detections as they are produced.
3
Track
Motion prediction and box overlap associate detections into time-ordered tracks. Every observation keeps its source frame, timestamp, class, confidence, normalized box, and stable track ID.
4
Apply rule
A marked area can retain entries, exits, or subjects that remain inside for a configured dwell time. A subject objective instead follows one selected identity through the complete clip.
5
Keep events
Praxis writes the annotated result, exact event frames, event reel, event and track CSVs, run manifest, artifact checksums, and a single downloadable Evidence Pack.

What remains inspectable#

A completed mission is not reduced to a count. Every event opens on the annotated video at its exact time and source frame. The operator can replay the moment, compare the result with the raw source, open its track history, and record a confirmed, not relevant, or unsure review. Reviews are written back into the manifest and rebuilt Evidence Pack.

Sharing and retention#

A result link is read-only outside the browser session that created it. The shared view can play and inspect retained evidence without changing the run. The owner can delete the result and generated artifacts immediately. Anything left in the public beta is removed after 24 hours.

Compute limits#

Mission Studio is a bounded public beta. One analysis runs at a time, each client can submit three runs per hour, and the service applies a global hourly ceiling. These limits keep the public CPU worker usable without turning the interface into a queue.