ALL SYSTEMS LIVE·ROBOTICS · AV · ADVISORY EVIDENCE · NEUTRAL WITNESS
DATA WITH RECEIPTS · ED25519 · RFC 3161·--:--:-- UTC
Home  /  Robots  /  Incident context
ROBOTICS · AV · DRONES · CONTEXT-AT-INCIDENT

What did the world look like when it happened?

After a robot, drone or autonomous-vehicle incident, the operator's own logs are the operator's own word. The environmental context, wind, rain, visibility conditions, GPS integrity in the area, is usually reconstructed months later from sources that have long since moved on, by parties who no longer agree on anything. And courts punish gaps in the record: a 2025 US verdict hit a carmaker for hundreds of millions of dollars, partly over withheld crash data. This page mints one signed context snapshot at the time, from named public sources, so every party starts from the same fixed record.

LIVE

A signed snapshot of the scene, right now.

Enter the coordinates of an incident location. Dynamic Feed queries live public sources for the environmental context there, weather, air quality, seismic activity nearby, and returns one Ed25519-signed awareness snapshot from the Awareness API. Nothing is mocked; no account and no personal data, only the signed snapshot itself is kept so it can be re-verified later.

the incident location; try your own. One POST to /v1/awareness, one signed record.
WHY IT MATTERS

Incident disputes are decided on records.

When a delivery robot clips a pedestrian, a drone loses link over a crowd, or an AV disengages into a barrier, three questions arrive within the year: what was the machine doing, what was the operator doing, and what was the world doing. The first two live in onboard logs the operator controls. The third is scattered across public sources that revise, expire and disappear, so each side reconstructs its own version and pays experts to argue about it. A context snapshot minted at the time, signed by a neutral witness, carrying each source's name and observation time, and verifiable years later against a published key, removes that whole argument. Anyone can re-check it, including the other side; our records work against us just as well as they work for you. Fleets already minting a pre-flight record via drone pre-flight receipts can mint the same kind of snapshot at every incident, or at every mission.

Data with Receipts. The snapshot proves what the named public sources reported for that location at that time, and that the record has not been altered since. It fixes the environmental context; it says nothing about the machine.
THE BOUNDARY

Context, not a causation ruling.

held on purpose

Dynamic Feed is a neutral witness, not an investigator, regulator or adjudicator. This snapshot records environmental context from named public sources at query time. It is not the robot's onboard state, not telemetry, and not a fault or causation determination. The value is contemporaneous minting: fleets should mint a snapshot at every incident, and can mint one per mission; the signed archive keeps every snapshot re-checkable later. Advisory evidence, tamper-evident not tamper-proof, zero personal data, and not legal advice.

FOR FLEET OPERATORS, DRONE OPS PLATFORMS, INSURERS & COUNSEL

One API call per incident.

Fleet software can mint a signed context snapshot the moment an incident flag fires, keyless to try, self-serve to scale.