Arrival and completion evidence, deduplicated and owned.
Status at ebf7cf0: Partial — upload, deduplication and soft deletion exist; the completion endpoint does not enforce the full evidence package.
The technician captures evidence during a visit.
Story. As a Technician, I want to attach up to three arrival and three completion photos, so that the visit has useful evidence without excessive duplication.
Acceptance. Arrival is optional. Normal completion expects at least one completion photo.
Story. As a Technician, I want to remove my own proof before completion, so that accidental uploads can be corrected.
Acceptance. A Technician cannot remove another person's proof or proof from a completed visit.
Story. As the system, I want proof identified by Job Log, kind, uploader, capture time and content hash, so that retries do not create duplicates.
Acceptance. A duplicate upload for the same visit and kind is deduplicated.
Proof upload, deduplication, soft deletion and the completion-photo UI expectation exist.
The completion endpoint itself does not enforce the full photo set or the structured Customer Not On Site evidence package — see Customer preview and signature.
Each visit keeps its own evidence. A continuation or recheck visit never inherits the previous visit's photos.
New to these terms? See the Glossary.