Skip to main content

Review Recording Evidence

Authorized observers can review completed vessel recordings, inspect accepted AI evidence, and maintain draft observer marks on the source timeline.

Review a recording​

  1. Open Human Analysis.
  2. Select an accessible vessel.
  3. Choose a date or inclusive date range containing completed recordings.
  4. Open a recording from the review-session list.
  5. Use the timeline to inspect AI events and tracker observations.
  6. Create or update a draft mark with species, handling, life status, length, weight, count, and notes as applicable.
  7. Link a mark to the supporting AI event when the mark was derived from that evidence.

For multi-day work, use the continuous recording review timeline. It plays two-minute cloud chunks as one virtual source-time range and keeps marks anchored to the underlying chunk rather than creating a stitched long video. 8. Refresh the session and confirm that the timeline and mark editor agree.

AI overlays appear only during their recorded evidence interval. Selecting an event outside the current playback time does not draw a misleading box on the video.

Interpret visual evidence​

New Edge candidates can include visionEvidence version 1. Edge selects a representative observation using image visibility before detector confidence, while retaining the actual tracker observations for review. The selected detector score is an uncalibrated engineering score. It is not the probability that a fish species is correct; speciesStatus: not_assessed and requiresHumanReview: true make this boundary explicit. A detector label such as fish is a candidate label, not a species determination or an official catch count.

The image-quality assessment may flag low detail, underexposure, overexposure, a small subject, or clipping at the frame boundary. measured with no flags means only that these heuristics did not trigger. It does not establish that an image is suitable for species identification. unavailable always has no flags and means that quality was not measured. Legacy events omit visionEvidence; their missing assessment must not be displayed as a clean quality result.

selectedTimestampSec stays on the primary source-camera segment timeline, including for a multi-camera candidate. Review archives may have a different playback origin. Use the review event's translated timestampSeconds for navigation, rather than seeking the source timestamp directly in an archive. The API preserves the evidence through local and cloud storage and exposes it to authorized review and live clients.

Enable the prototype upgrade​

  1. Release the API that accepts and preserves visionEvidence.
  2. Release Web support for the evidence card and legacy fallback.
  3. Update Edge, then enable INFERENCE_VISION_EVIDENCE_UPLOAD_ENABLED only after verifying the API accepts the new contract. Set it for both inference and uploader roles, then restart those services with the updated configuration (recreate their containers if using Compose). The flag defaults to disabled to support older API installations.
  4. Verify a newly analyzed event in both review and live responses. Confirm that human review is still required and that species is not assessed.

Each retry checks the uploader's loaded configuration; editing an environment file alone does not reload a running service. During rollback, disable the switch and restart with that configuration so queued events use the older upload shape without discarding recordings or detector observations. Enabling the switch does not backfill metadata omitted from older queue items; verify a newly analyzed event after restarting both roles.

Permissions​

Reading sessions requires review-data access to the vessel. Creating, updating, or deleting marks requires observer-review permission. Vessel access is checked for every request.

Observers may edit only eligible draft marks. Completed source video and accepted AI evidence remain unchanged when a human mark is corrected.

The observer review API lists sessions, opens a playable session, and creates, updates, or deletes draft marks. Use the API Reference for field-level schemas and error responses.