What did the dispatcher know at dispatch?
When a crash, a rollover or a chain-of-responsibility investigation asks what road and hazard conditions the dispatcher knew when the load went out, the honest answer is usually reconstructed months later from sources that have since moved on. Both sides then argue from screenshots. This page mints one signed record at the time: a live go, caution or no-go awareness snapshot for a route point, and a re-verifiable hazard-condition receipt for a corridor city, each from named public sources. A neutral, timestamped record for the fleet file that every party can re-check.
A signed record of the route, right now.
Step 1 · route-point awareness
Enter the coordinates of a route point, a depot, a rest area, a difficult junction. Dynamic Feed queries live public sources for the conditions there, wind, rain, temperature, air quality, seismic activity nearby, and returns one Ed25519-signed awareness snapshot with a go, caution or no-go verdict 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.
full signed snapshot (JSON)
Step 2 · corridor hazard receipt (re-verifiable)
Pin a hazard threshold for a corridor city, say wind at or above 40 km/h, and Dynamic Feed returns a signed trigger receipt: the observed reading, the source of authority, and a deterministic met or not-met determination that any party can re-fetch and recompute. Because this call is a plain GET URL, the exact record you see is deep-linked into /verify so anyone can re-check it later.
full signed receipt (JSON)
Chain-of-responsibility cases turn on records.
In road transport, responsibility for a load runs up the chain, from the driver to the dispatcher, the scheduler and the operator. When something goes wrong, the investigation asks what each party knew and when. The truck's telematics are the operator's own log, and the operator controls it. The road and hazard conditions, whether a wind, heat or flood advisory was in force along the corridor at dispatch, are usually scattered across public feeds that revise and expire, so each side reconstructs its own version and pays experts to argue about it. A record minted at dispatch by a neutral witness, carrying each source's name and observation time, and verifiable years later against a published key, removes that argument. Anyone can re-check it, including the other side; our records work against us just as well as they work for you. Fleets can mint the same snapshot at every dispatch, at every incident flag, or at every corridor handover.
Evidence, not a compliance ruling.
Dynamic Feed is a neutral witness, not a regulator, investigator or adjudicator. These records capture the road and hazard conditions from named public sources at query time. They are not the vehicle's telematics, not the driver's log, and not a chain-of-responsibility, fault or causation determination. The go, caution or no-go verdict is an advisory read of public conditions; your dispatch and safety systems own every decision. Laws, standards and contracts vary by jurisdiction and operator, so this is one independent input beside the fleet's own records and telematics, not a replacement for any of them. Advisory evidence, tamper-evident not tamper-proof, zero personal data, and not legal advice.
One record, across the whole chain.
The same signed-record pattern runs the length of a transport operation. Incident context receipts mint an environmental snapshot the moment a robot, drone or vehicle incident flag fires. The Robot Awareness API is the go, caution or no-go engine behind the route snapshot above, built for autonomous and assisted fleets. Logistics evidence receipts carry the same neutral-witness record along the freight leg. Each is keyless to try and self-serve to scale.
One API call per dispatch.
Fleet and telematics software can mint a signed route-and-hazard record the moment a load dispatches or an incident flag fires, keyless to try, self-serve to scale.