Start with an official AGOT Windows release.
The first question is not which marketing version appears in a screenshot. It is which executable you obtained, whether its digest matches the published release and what GIS operations you can actually validate.
Choose and verify the real published installer.
Open the AGOT release panel. It discovers public Windows release metadata from the official GitHub distribution repository. Read the exact release notes and download the relevant asset from that source. Never assume a fixed historical Preview version is current.
- Integrity: compare your downloaded file's SHA-256 against the published checksum for that exact asset, when provided.
- Platform: review Windows requirements, installer and local service prerequisites before installation.
- Evidence: distinguish an uploaded MSI and checksum from code signing, successful upgrades or a tested GIS session.
- Privacy: use non-sensitive data for first-time evaluation and do not paste API keys or protected datasets into public issue reports.
Windows PowerShell hash command: Get-FileHash -Algorithm SHA256 -Path "C:\Path\To\Installer.msi". Replace the placeholder with your actual downloaded filename; compare the returned hash to the release record.
Verify a small georeferenced task.
Choose a licensed vector layer and record its feature count, attributes, geometry type and coordinate reference before import. After loading it, inspect placement and metadata. Try only an operation documented as supported for that installed build, save its output and independently reopen it.
- Record the exact AGOT version and test machine environment.
- Check spatial data source, geometry validity and CRS before processing.
- Capture tool inputs and parameters and distinguish empty results from execution errors.
- Export a supported output format, reopen it and verify feature counts, geometry and metadata.
- Report failures with reproducible non-confidential evidence rather than only screenshots of a green status indicator.
Desktop, GIS host and SDK workflows are separate.
QGIS, ArcGIS Pro and the Python SDK use their own packages, host environments and acceptance tests. Local model discovery and cloud provider selection may vary by release. Package publication is not a statement that all pairing, native tools or automated agent plans work end to end.
Desktop 1.0.8 Preview 1 documentation.
Installation evidence for the owner-waived public preview is supplied with the current release: versioned compatibility, a public manifest and SHA-256 checksums. The installer is a Windows MSI; no signed Desktop auto-updater was published. GeoAI Hosts and Harness require different packages and separate acceptance.
Build against verifiable outcomes.
Describe the target GIS environment, licensed data, required operation and acceptance criteria. Native-host execution and product maturity must be verified independently.