A point is not a decision record
Latitude and longitude tell a system where to look, but not whether the input resolved to the intended building, street segment, parcel, or city centroid. That distinction matters whenever a downstream workflow assumes precision. A place-aware system should preserve the method used to resolve the location and give reviewers a way to stop when the result is too coarse.
Every field has a different clock
Elevation, boundaries, infrastructure inventories, and hazard layers do not refresh on one schedule. Treating them as a single current snapshot hides material differences. Source identity, retrieval time, available dataset vintage, and quality notes belong beside each field rather than in a remote methodology page.
Absence should remain visible
A missing value can mean the feature is absent, the source has no coverage, the query failed, or the dataset uses a different definition. Those are not interchangeable outcomes. Agent interfaces should encode the distinction and avoid turning silence into a confident negative.
Provenance supports review; it does not replace it
A cited value can still be stale, misclassified, licensed for limited uses, or inappropriate for a particular decision. The right goal is a reviewable evidence trail: enough context for a person or another system to understand what was used, what was not found, and where further verification belongs.