← Products
Operational Evidence Record Profile · Physical-world location claims

Location Operational Evidence Record Profile

Real-time operational evidence records for physical-world location claims. GeoClear verifies location-related claims against available signals, policy context, and customer rules, then issues a customer-held operational evidence record for audit-heavy workflows.

Truth boundary: GeoClear™ verifies the claim against available signals. It does not claim to verify the physical world with absolute certainty.

↓ Download sample bundle (40 KB) See drone-delivery use case → Solution overview
Operational evidence record Operational evidence record for a location.verify action under policy airspace_policy_v3. Result: authorized. Verified independently and retained customer-side. OPERATIONAL EVIDENCE RECORD OR-2026-05-14-A4F3 ACTION location.verify POLICY airspace_policy_v3 RESULT authorized VERIFICATION independent RETENTION customer-held RETAINED EVIDENCE · VERIFIABLE OFFLINE no network required for verification
Location claim + available signals + zone/policy → operational evidence record. The record is the artifact; any map context is supporting evidence.

Who this is for

One platform, multiple profiles

GeoClear is real-time operational evidence record infrastructure for machine-driven systems. Location Operational Evidence Record Profile is the reference implementation of the platform applied to physical-presence claims. The same record substrate also powers the Flood & Census, Decision, and other record profiles.

What the record captures

The operational evidence record captures the location-substrate fields. For deployments that overlay the drone_deliverability tool path on /agent-protocol, the record additionally captures the airspace + landing-zone fields:

full_address
USPS-canonical address that authorized the action
lat / lon
Rooftop-precision coordinates of the landing zone or asset
airspace_class
FAA Class B / C / D / E / G (when overlay applied)
airspace_restrictions
Active NOTAMs, TFRs, prohibited zones at the timestamp
landing_zone_confidence
0-1 confidence the address has a viable landing surface
drone_deliverable
Boolean dispatch decision
geofence_zones
HOA / school / hospital / federal-property exclusions
weather_at_decision_time
Weather snapshot at the record’s iat

The record is bound to the recorded fields at decision time. Change a value, and the verification fails.

Sample bundle

AZ-0001, 46801 West Aguila Valley Road, Congress AZ Customer-held evidence bundle · offline-verifiable
↓ Open sample gallery Verify it now

A real arid-zone parcel in Yavapai County, Arizona, the kind of geography where autonomous logistics actually flies. Verification uses customer-held verification material; no GeoClear server is required for the verification result.

Integration

What this verifies, and what it doesn’t

What this verifies

  • GeoClear issued this location record at the timestamp inside it.
  • The recorded payload has not been mutated since issuance.
  • The verification material traces to a stable, customer-verifiable trust anchor.
  • The customer can re-verify the record later without contacting GeoClear servers.

What this does not verify

  • That FAA airspace classification was current to-the-minute.
  • That the landing was physically safe.
  • That the dispatch decision was the right one.
  • That the package or asset arrived intact.

Sister record profiles: Flood & Census Record Profile · Decision Record Profile. Underneath them all: the Record Engine and Operational Evidence Records.