Read the corridor you already captured through any protocol.

One protocol, one vocabulary.

Each Lens carries a fixed set of categories and labels written for the program it serves. Labels never come from free text, so two people reading the same scene see the same words.

The read has a history.

Schema and prompt versions travel with every result. Recapture the corridor and the same Lens reads it again, so change is measured against a known baseline, not a memory.

Evidence, not findings.

A Lens says what is visible and how confident it is. Your staff confirm it in the viewer or the field. It supports GIS, inspection, sampling, and permit records; it does not replace them.

Evidence boundary

We write the rule set with you: what eye-level imagery can show, what it cannot, and what stays with your records. That boundary is the Lens.

Sample read

A handful of representative scenes are read first. Your staff review each observation, its placement, and the false positives before anything scales.

Corridor read

Every panorama is read against the protocol. Each observation lands in the scene where it is visible, with a confidence and the face it came from.

Verification

Observations stay evidence until a person confirms them, in the viewer or in the field. Reviewed results export to your GIS with their coordinates and bearings.

Not an inventory. A panorama shows what was visible from the path on the day of capture. Anything hidden by vegetation, distance, or a manhole lid is recorded as not assessable, never as absent.

Not a finding. No Lens asserts permit compliance, a discharge, ownership, or water quality. It points a person at the scene and says what to check.

Not a replacement for records. Reviewed observations join your GIS, inspection, sampling, and permit records with their coordinates and bearings. They add a located photograph to each row; they do not overwrite it.