Getting started

Mission Studio guide

Give Mission Studio a short video and one concrete question. It returns a playable result, exact matching events, identity histories, and a portable Evidence Pack.

Start with the configured overhead example in Mission Studio. It demonstrates the complete workflow without requiring an upload.

Run the overhead example#

Load the example

Select Load the example in the video workspace. The source, subject family, entry rule, and marked area are configured together.

Check the question

The question above the video should read Who enters the marked area? Play the source and inspect the red polygon before running it.

Find area entries

Select Find area entries. The five processing stages update in order while the current evidence stays visible.

Open an event

Select a red timeline tick or an event in the right panel. The result pauses on that event and the panel shows its time, source frame, identity track, and confidence.

Inspect or export

Replay the event, follow that subject, compare the annotated result with the source, or open Downloads for the complete Evidence Pack.

Choose or create a project first. Sources, reusable objectives, run history, retention, and results belong to that project. API keys belong to the browser workspace and can access its projects according to their scopes. Mission Studio accepts MP4, MOV, M4V, and WebM files up to 60 seconds and 80 MB. Oversized files are rejected in the browser before an upload begins. Choose one of two objectives:

Objective	What to configure	What it returns
Watch an area	A subject family, polygon, and entry, exit, or dwell trigger	Every stable track that matches the spatial rule
Follow one subject	A subject family and one selected box on a clear frame	That visible identity history across the clip

For an area mission, click at least three points around the place to watch. Use Undo to remove the last point or Clear to redraw the polygon. For a subject mission, pause on a clear frame before selecting the subject.

Understand the five stages#

Prepare source

The source is validated, stripped of audio, normalized for processing, and retained with its dimensions, frame rate, duration, byte size, and SHA-256 digest.

Detect subjects

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.

Link identities

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.

Evaluate 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.

Build evidence

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.

If analysis is unavailable#

The website and analysis worker are separate. Mission Studio shows Analysis ready when the worker responds. If it shows Analysis unavailable, the rest of the site is still online. Select Retry before loading or uploading footage.

Accepted missions wait in the compute queue when another run is active, so they do not need to be resubmitted. Per-workspace and global hourly limits return a separate limit message before a run is accepted. A failed request does not retain a partial upload as a completed result.

Share creates a read-only credential rather than exposing the run ID. The shared view can play signed evidence without reviewing, rebuilding, or deleting the run. New links expire after 72 hours by default and can be revoked. The owner can delete the result and generated artifacts immediately. Each project controls its source and result retention window.

Compute limits#

Mission Studio is a bounded public service. Accepted runs enter a durable database queue and one CPU analysis executes at a time. Each workspace can submit three runs per hour and the service applies a global hourly ceiling. A worker interruption is recovered once before the run is marked as failed.