What you can do with geo.qa.

Six capabilities, each useful on its own. You pick a place; geo.qa keeps the record, watches it with every sensor pointed at it, and answers your team or your agent with what was actually observed and the receipt to prove it: a canonical-CBOR fact, BLAKE3-hashed and ed25519-signed, you can verify offline.

Request a tenancy →Read the protocol

Ask · a place, a question

Get back · a signed fact

Cite · public & private alike

Capability 1

Watch a place over time.

Forest cover, vegetation health, water level, urban growth, a mining footprint. You name the place once. geo.qa files an observation against it every time a sensor passes over, so the trend is already there when you ask, not assembled on the spot.

# what you ask ask show forest loss in district 04 since 2020 # what you get back → 8.3% canopy loss · 142 km² cleared largest patch 11 km² contiguous bands indices.ndvi · hansen.loss_year · surface_water window 2020-01 … 2026-02 · annual + 8-day ◇ receipt 0x71d4…0a90 signed

Spec. 1. Sourced from Sentinel-2 NDVI at 10 m and the annual Hansen Global Forest Change layer. Exportable as CSV or GeoJSON, every row carrying its provenance.

Who uses it	For what
Conservation	Protected-area watch, deforestation, illegal clearing.
Forestry & carbon	Annual cover, biomass trajectory, regrowth verification.
Insurance	Crop, flood and wildfire exposure against current ground truth.
Utilities	Vegetation encroachment on transmission corridors.
Agriculture	Field-level greenness, water stress, and harvest progress.

Capability 2

Spot what is new.

Draw a polygon, set a cadence, and geo.qa flags what was not there last time: new construction, vehicles, infrastructure, an encampment. Detection runs the SAM3 / SAMGeo head across 186+ object categories on the fused imagery.

# what you ask ask detect new structures in this 5 km area since last quarter # what you get back → 27 new buildings vs. baseline densest cluster 27.485, 51.531 bands optical (S2) + drone overflight 04 detector SAM3 / SAMGeo · 186+ categories ◇ receipt 0x4c1e…77ab signed

Spec. 2. Change is computed as a DerivativeFact against an earlier tslot: the baseline was real, dated, and stays queryable. Nothing is overwritten.

Who uses it	For what
Defence & intelligence	Pattern-of-life and order-of-battle change in an AOI.
Urban planning	Informal construction, illegal extensions, zoning compliance.
Logistics	Yard inventory, equipment movement, lot occupancy.
Humanitarian	New camps, displacement, post-event damage assessment.
Mining	New access roads, pit expansion, unlicensed activity.

Capability 3

Watch live cameras.

Connect a fixed camera, a drone feed, a dashcam, even a public YouTube live stream. geo.qa watches the frames against the same memory and pages you when a truck crosses a line you drew, not every time a cloud moves.

# what you ask ask page me if a vehicle enters Sector 7 between 02:00 and 05:00 # what you get back, when it fires → CRITICAL · vehicle in Sector 7 camera cam.07 · RTSP at 2026-04-12T03:14:09Z · conf 0.94 frame attached + cell address ◇ receipt 0x9af2…be21 signed

Spec. 3. Ingest over RTSP, ONVIF, HLS, RTMP or WebRTC. A detection becomes a fact at the camera’s cell, with the frame as evidence, so the page can survive a later review.

Who uses it	For what
Critical infrastructure	Perimeter intrusion, restricted-area entry, gate events.
Transport & ports	Yard activity, dock occupancy, gate throughput.
Retail & venues	Crowd counts, queue lengths, throughput anomalies.
Smart cities	Civic feeds, traffic patterns, incident review.

Capability 4

Run a monitoring loop.

A place, a condition, a cadence. Then an email or a webhook the moment the condition fires. Every alert ships with the evidence it used and a signed receipt, so the delivery itself is auditable.

# what you ask watch our 1,420 km pipeline corridor alert if vegetation drops 3σ cadence daily notify pager + webhook # what you get back → daily corridor scan armed this month 3 alerts · all cited webhooks CHANGE_DETECTED · ANOMALY_DETECTED delivery every payload signed ◇ receipt per alert · verifiable offline

Spec. 4. Conditions read across bands and tslots. A quiet day returns a signed NegativeFact, not silence, so you can tell “nothing happened” from “nobody looked.”

Who uses it	For what
Pipelines & transmission	Right-of-way encroachment, vegetation, ground state.
Mining	Tailings-dam geometry, haul-road wear, illegal access.
Agriculture	Field-by-field water stress, pest outbreaks, harvest timing.
Maritime	Vessel presence, oil-sheen detection, port congestion.

Capability 5

Ground your agents.

Your agent recalls before it answers. Connect over MCP or call the REST API directly; it gets dated, multimodal observations with an audit trail, never a guess about a place it has never been.

agent.py

# recall before you answer · MCP or REST
from geoqa import Memory

mem = Memory(tenant="acme")

evidence = mem.recall(
    cell = mem.locate(lat=27.485, lon=51.531),
    window = "-24h",
    k = 12,
)

evidence.sources    # S1 SAR · drone.04 · cam.18 · weather
evidence.receipt    # 0x71d4… signed · verifiable

Who uses it	For what
Operations agents	On-call agents that page humans with cited evidence.
Customer agents	“Where is my shipment, and what is the weather there?”
Research agents	Long-horizon recall over years of observations.
Robotics	Real terrain and recent ground state before action.

# the same call over the open MCP tool surface emem_locate { "lat": 27.485, "lon": 51.531 } → cell emem_recall { "cell": …, "window": "-24h", "k": 12 } → 12 signed facts emem_verify_receipt { … } ◇ verified offline

Spec. 5. Reads carry the readOnlyHint; writes are capability-bound under your attester key and signed. On one reference deployment, illustrative only, a top-k recall returns in single-digit milliseconds. Your numbers depend on your fleet and hardware.

Capability 6

Cite the public ledger.

Every tenancy comes pre-wired to query emem.dev, the open Earth memory. Public facts are free to cite and arrive in the same signed receipt format as your private memory, so one answer can quote both.

# what you ask ask most recent water recurrence at this cell? # what you get back, from the open ledger → 78% recurrence band surface_water.recurrence · JRC GSW · 30 m signer emem.dev public key verify /.well-known/emem.json · offline ◇ receipt 0xeme0…dev7 · ed25519 + BLAKE3

Spec. 6. emem speaks the open protocol with no keys: canonical CBOR, a BLAKE3 hash, an ed25519 signature you check against the public key at /.well-known/emem.json. No callback home.

Public Earth data is a commons. A JRC water reading or a Hansen loss year should not sit behind a per-query fee, so the open ledger stays open. Anyone can cite the same facts with the same proofs, including teams who never sign up for geo.qa.

geo.qa is the upgrade on top: H3-resolved addressing, your own capture devices, the full multimodal fleet, a private airgapped tenancy you own, and your own world models trained on the unified memory. It still speaks emem, so the boundary stays clean.

publicflows in · emem.dev, cited freely

privatenever flows out · your tenancy, your keys

one receipt format · public & private cite the same way

Capability 7

By industry.

The same six capabilities, mapped to the question each domain actually asks. Pick the row that sounds like your day.

Industry	The question we answer	Primary capability
Aviation operators	Is anything wrong along our 1,420 km corridor today?	monitoring loop
Mining	Has tailings-dam geometry moved beyond tolerance?	watch a place
Forestry & carbon	How much canopy did we lose this quarter, and where?	watch a place
Defence & GEOINT	What is new inside the AOI since the last sweep?	spot what is new
Insurance	What was the ground state at the policyholder the day before the claim?	recall / cite
Robotics	What does the place look like before I get there?	ground your agents
Civic & government	What does the public ledger say about flood recurrence here?	cite emem.dev

Tab. 1. A growing list. If your domain is not here and you think it fits, tell us. Most rows started as one operator’s question.

Try the capability you need.

Wire one real workflow first. The rest stays available; turn it on when you outgrow the first.

Request a tenancy →See pricing

geo.qa · a vortx ground decoder · emem.dev open protocol