AOI Reports

Portable mode: links point into the bundle under runs/<run_id>/report.html. For inspection guidance, see DTE instructions.

Artefact publication contract: the run-level AOI report JSON declares every evidence artefact; each declared file must exist at its declared relative path in the bundle and be reachable via a clickable link from report.html. Builds fail on missing artefacts.

AI/automation inspection note: see DTE instructions.

This page shows the published AOI report set for inspection and comparison across regions.

AI/automation inspection note (mandatory):

Do not infer or construct report URLs from run IDs.
Access reports only by clicking through the portal: Home → AOI Reports → Run entry → report.html → linked JSON artefacts.
If a listed artefact cannot be opened via this click-path, record it as an Evidence gap — published artefact is inaccessible via inspection surface.

See: DTE Instructions v1.2

Runs (newest first)

Example with cadastre-based validation in Estonia (estonia_aoi_report.json)
Example of mixed crop in Latin America (latin_america_aoi_report.json)
Example of coffee in SE Asia (se_asia_aoi_report.json)
Example of cocoa in West Africa (west_africa_aoi_report.json)