SATQUERY — Analyze

Analyze

Session SQ-LOCAL-—

Observation

none

Upload imagery Drop a scene here or browse — the protagonist goes centre-stage.

No image uploaded. The centre plate shows an illustrative reference frame so the instrument is legible — it is not a SatQuery result.

Filename, dimensions, size and modified date are read from the file you select. Sensor, platform, modality, CRS and acquisition date are not present in a generic upload — left as “Metadata unavailable” rather than invented.

Router interpretation

pending

awaiting query

Slots shown are the deterministic mock router’s reading of the question — the schema-shaped Intent (task, modality, temporal, spatial output, evidence, source). Replaced verbatim by the live intent classifier; no measurement is implied.

Temporal pair

none

Add T0 (earlier) Optional — enables the comparison slider.

Co-register T0 yourself before upload; the instrument does not register pairs. Until then the comparison view stays empty.

Illustrative frame

Illustrative reference observation — not a SatQuery result

Illustrative Reference imagery · ESA / Copernicus — not a SatQuery result

Answer

awaiting

No answer yet

The answer is assembled by the result schema only after real specialists return. Nothing is synthesised here.

Evidence

0 regions

no evidence yet

Evidence records follow the schema Evidence / Region / ChangeRegion shape (type, source specialist, coordinate system, score, artifact). Empty until a specialist produces them.

Confidence

calibrated

—calibrated

Calibrated confidence is reported only with a real result. Until then it reads “—” — not a placeholder number.

Provenance

Run: awaiting backend
Policy: —
Protocol: —
Schema: 1.0

Report

The report carries the full result schema (PDF / JSON). The button stays disabled until a real report exists — it never fabricates one.

Execution trace — ControllerState idle

The eight production events (QUERY_RECEIVED → RESULT_ASSEMBLED) drive these states through SQ.run().ingest(). The local mock emits them with empty payloads: RECEIVE / PARSE / PLAN are exercised by the deterministic router; PREPROCESS → RESPOND show “awaiting backend” because no model is connected. No execution is simulated.

Event stream Same names, same payload shape as production — swap the mock for a live feed and nothing else changes.