One evidence trail, from upload to checked report.
Use the existing intake, CV, Jev, witness, and report flows in order. The bundled photo pair is a seeded repository test fixture, not verified field evidence.
Selected site
Plot B
plot-b · yamuna-green
Live ledger site
Service availability
A reachability check is not proof a new job completed.
Import this ZIP through Intake with the site assignment pinned to Plot B. The seeded baseline is dated 2026-06-20, before the seeded claim period; the integrity review may flag it as out of period. It can still be selected as the comparison baseline. On a clean ledger, open the site page and choose “Set as baseline.”
Set the baseline first, then import this ZIP. The existing pipeline will attempt alignment and metrics. The comparison page shows its recorded quality and any available change measurements.
Use the camera flow for a real observation of the selected site. The seeded control re-uploads the follow-up fixture and may be flagged as a duplicate; it is not independent testimony. After submission, the witness page links to its ledger record.
Generate a report for the sample period. The judge flow adds one visibly seeded, uncited control sentence; the normal composer records it as struck for having no receipt. Supported facts still require live drafting and Jev checks.
The ledger is reachable; report state will update after composition.
The sample archives include repository test images and their fixture chat dates. They are seeded, not field evidence; their EXIF dates are editable metadata. Evidence writes persist. Re-uploading the same files to this project can trigger duplicate checks, so repeat the walkthrough on a clean/staging ledger rather than deleting records from a shared deployment. If Jev, Cloudinary, or the CV worker is unavailable, the affected step remains pending.
A baseline is currently set for this site. 1 non-witness follow-up evidence item currently in the ledger.