Skip to content
finwave Docs

Confirming Predictions

What you’ll learn

Section titled “What you’ll learn”
  • When the Confirm button is offered and when it isn’t
  • What confirming actually does to the annotation record
  • The Set-as-Profile button next to it and how its rules differ
  • Where bulk review lives (it’s not in the annotator)

When the Confirm button appears

Section titled “When the Confirm button appears”

Each annotation in the right-hand list has a row of action buttons. The Confirm button — a check_circle icon — only renders when both of the following are true on the annotation:

  • It is machine-generated (isMachine is true)
  • It is not already confirmed (confirmed is false)

That means: a fresh ML detection that no human has reviewed yet. Manually drawn annotations are confirmed at create time, so they never show this button. Already-confirmed annotations also don’t show it.

The button is disabled when the annotation has no animal assigned to it. You can’t confirm an unidentified box — confirm it as what? Pick an animal first via the Edit (relabel) action, then return to confirm.

What confirming does

Section titled “What confirming does”

Clicking Confirm runs onListConfirm(id) in the workspace. The annotation record gets two field updates:

  • confirmed is set to true
  • annotatedByUser is set to your user record

The change is persisted via the annotation store’s updateMeta mutation, which the persistence service batches and ships to the server. A annotation_confirmed usage event fires for ML Center metrics, the annotation list re-renders to reflect the new state, and selection / hover styles are reapplied.

That’s it on the client. Whatever evidence-tier promotion or downstream effects happen are server-side and aren’t documented here — see the Evidence Tiers page for the conceptual model.

Set as Profile (the button next to Confirm)

Section titled “Set as Profile (the button next to Confirm)”

There’s a separate portrait icon button — Set as Profile — that picks the annotation’s image as the active profile crop for that animal. Its visibility rules are stricter than Confirm:

RequirementWhy
Annotation has an animal idProfile images belong to an animal
confirmed is trueOnly confirmed annotations are promoted to profile
Side is Left or Right (not Unknown)Profile images are bucketed by side
Category is not unknownProfile images are bucketed by category (dorsal fin, fluke, etc.)

If the annotation fails any of those, the Set as Profile button doesn’t render.

What’s not in the annotator

Section titled “What’s not in the annotator”

The annotator deliberately does not include:

  • Bulk confirm — there’s no select-multiple-and-confirm here. Each annotation is confirmed individually.
  • Reject / Skip / Mark as disputed — those are review affordances on the Confirmation Queue, not in the annotator. The annotator’s nearest equivalent is the Delete button (warn-coloured trash icon), which removes the annotation entirely rather than marking it for later review.

If you’re working through a queue of annotations across many encounters, use the Confirmation Queue. The annotator is for reviewing the annotations on a single photo or encounter you’re already looking at.

Section titled “Related”