# Drone navigation **Workload class:** vision–language-driven autonomous flight. Operators issue **text missions**; miners compete on **navigation and execution policies**; validators score whether the run matches the **task instruction** (safety, task match, geospatial correctness). [Proof-of-Physical-Work (PoPW)](/understand-konnex/contracts-and-popw.md) binds the instruction hash, policy trace, and hardware-attested sensor data. ## Testnet The public dashboard URL for this workload will be announced with the testnet release. ## Task shape (illustrative) Users typically send natural-language instructions such as: *"Fly to the red-brick building and photograph the roof."* The exact schema (fees, rewards, attachments) is defined by the live subnet UI and chain integration. ## Why this matters Aerial data often underwrites insurance, maintenance, and engineering decisions. A self-reported log from the same party that operated the aircraft is not a substitute for independently scored evidence tied to a signed, onchain instruction. ## See also * [OpenFly & OpenFly-Agent](/supported-ai-models/openfly.md) — aerial VLN / language-driven flight * [Subnets overview](/subnets-workload-classes/subnets.md) * [Proof-of-Physical-Work](/understand-konnex/contracts-and-popw.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.konnex.world/subnets-workload-classes/drone-navigation.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.