Task Photo Verification
Overview
Tasks can require photo proof before they count as completed. Open the assigned task's panel and submit proof there; sending a picture in coach chat does not submit it for task verification.
For recurring proof that a lock is still being worn, see Daily Verification. It has its own submission windows, review settings, and missed-window consequences.
For choosing tasks, managing multiple assignments, timers, and completion consequences, start with Tasks & Task Queue.
Read the task instructions, minimum timer, completion deadline, and review destination before starting. Bot Coach and AI Coach assignments show one of these review labels in the task panel:
- Bot verification: a vision-capable Bot Coach is assigned to review the photo.
- Community verification: the photo is added to the Community Verification queue.
- Private verification: the task is assigned to the lock's private review flow, normally its keyholder.
Tasks assigned by a regular keyholder, the wheel, random selection, or the wearer do not show this automated-assignment banner. Review labels currently have an important privacy limitation.
Submit proof
- Open the correct task under Selected task. Each task has its own timer and verification progress.
- Read Verification required and any task-specific instructions.
- If the task requires a minimum time, select Start Timer and wait for it to finish. For before-and-after proof, save the before photo first.
- Use Capture or upload photo or Capture or upload after photo, check the preview, and submit the verification.
- Wait for the review result. An uploaded file is not an approval.
The upload accepts JPEG, PNG, GIF, WebP, HEIC, and HEIF images up to 10 MB per photo. If an image cannot be processed, try a smaller JPEG or PNG.
Camera and verification code
The task panel prepares a verification code. For gallery, file, pasted, or dropped images, make that code physically visible in the photo. Copying it into a message or adding it digitally is not the requested proof.
Where the native in-app camera option is available, the control says Camera - no code needed. That exception applies to the photo captured through that option. A photo taken elsewhere and later uploaded through Gallery - include code still needs the code. If the code fails to load, use Try again before taking the gallery photo.
Before and after photos
Some tasks require two photos:
- Take and upload the Before photo before doing the task. Wait for Before photo saved.
- Start the minimum timer if the task has one. The before photo cannot be replaced after that timer starts.
- Complete the task, then capture the After photo once the minimum time has elapsed.
- Submit the after photo. Chastify combines both images into a labeled comparison for review.
Include the task's code in each image uploaded from the gallery or another file source. The comparison's timestamps record when the photos were uploaded, not independently verified capture times.
How the destination is selected
| Assignment | Photo verification | Vision support | Destination |
|---|---|---|---|
| Bot Coach | Not required | Any | No photo review |
| Bot Coach | Required | Available | Bot verification |
| Bot Coach | Required | Unavailable | Community verification |
| AI Coach | Required | Unavailable | Community verification |
| AI Coach | Required | Available | The lock's configured private/community verification policy |
Vision support is determined from the active model and provider configuration. OpenRouter models use their reported capabilities. Custom model endpoints use the vision option configured for that endpoint.
Ordinary self-lock task proof uses Community Verification. On shared locks, Public task verification gallery controls the ordinary public/private choice. Calendar tasks can have an explicit review choice. AI Coach having a vision-capable model does not by itself mean it will personally review a task photo.
For AI and ordinary assignments, the current lock/gallery policy can affect submission routing even if the task was created earlier. Check those settings as well as the banner before submitting. Changing the model later does not automatically move an existing Bot verification task to a different review path.
Predefined and ad-hoc tasks
Predefined tasks use the Require photo verification, single/before-and-after mode, and instructions saved on that task. The assignment keeps a snapshot of those requirements; editing the task definition is not a way to rewrite proof requirements for an already assigned task.
Ad-hoc tasks invented by a Bot Coach or AI Coach use that coach's separate Require photo verification for ad-hoc tasks setting. Enabling it does not change predefined tasks. Linked writing tasks and quizzes use their own completion flow and cannot also require task-photo proof.
Waiting, approval, and rejection
| Status | What it means |
|---|---|
| Verification pending | Proof was submitted and is awaiting review. Do not submit another photo for the same run. You can work on another available task while waiting. |
| Approved / completed | Approval normally completes the task automatically once its minimum duration is satisfied, applying its configured reward and points. |
| Approved (waiting duration) | Approval is recorded, but the duration requirement still needs to finish. Use the completion control when it becomes available. |
| Verification rejected | That task run has ended as rejected. Read the reason in task history; the same run does not currently accept replacement proof. A new attempt needs a new assignment or selection when available. |
The minimum timer and Time left to complete are different. The first controls when proof can be submitted; the second is the deadline for completing the work or submitting proof. A successful submission clears the completion deadline while review is pending.
Rejected proof can trigger the task's configured consequences, including added time, a freeze, or a device action. A Bot Coach's review can also include an allowed time reward or punishment. Check the task result and lock history rather than assuming the review is only a message.
Temporary model failures
Community Verification is not a runtime fallback after a task has already been routed to Bot verification.
The Bot verification worker retries failed requests and can try another available vision configuration after an empty model response. The review may use the configured provider or an available hosted vision provider; Bot verification does not mean the photo stays on your phone.
If review still fails, the result can be review_failed. This is a model-review failure, not proof that you failed the task. The task stays open without rejection consequences. Submit the proof again from the task panel; a saved before photo and verification code are retained. A genuine rejection of the proof still ends the attempt and can apply configured consequences.
Privacy
Self-lock photo proof uses Community Verification. Shared locks with the public task gallery enabled also allow community reviewers to see and vote on pending proof. These lock settings apply even when community verification is unchecked for an individual task. A bot can review its assigned proof while community review is also available. The task panel explains the audience before upload; keyholder-only review requires a shared lock with its public task gallery disabled and community verification unchecked for the task.
Community submissions can be viewed and voted on by eligible reviewers. Bot review sends the photo and task context to a vision provider; private keyholder review is separate from that automated model review. Submit only proof appropriate for the applicable audience.
Task history retains review details. Photos from older completed or rejected runs can be removed as newer verifications replace them; the history UI describes a limit of the three most recent verifications per task. A Photo unavailable entry does not mean its review result disappeared. Pending reviews and unfinished runs are handled separately, so this is not a promise that every older photo is deleted immediately.