UAV operations
Infrastructure-inspection UAV missions generate imagery and sensor data that needs interpreting mid-mission, without that interpretation ever gaining authority over flight control. This page sets out how such a workflow would be planned and run on inTheEU Assist, not a record of a completed deployment.
How the workflow would be structured
A mission would be submitted by an authorised operator and decomposed into a defined sequence of stages, survey, analysis, closer inspection where warranted, reporting. Imagery and sensor data collected during the mission would be indexed on premises, feeding a knowledge pack scoped to the operator's own tenant. An agent configured for the workflow would compare observations against approved reference material and propose a candidate finding, entered with a status of proposed and tied to the specific mission it came from. A request for closer inspection would follow the same proposed-to-approved path before the UAV is repositioned.
The UAV's own flight controller, stabilisation, navigation, geofencing, return-to-home and emergency procedures, collision avoidance where implemented, would remain entirely outside this workflow. The platform would never hold, request, or execute authority over those systems, and no manoeuvre reaches the aircraft until it has passed through an explicit approval.
Where human approval sits
Every finding or repositioning request would require explicit approval from a named operator before it is treated as established or acted on. This is not a policy layered on top of the workflow. It is the mechanism by which the workflow proceeds at all: an unapproved stage simply does not execute the next step.
What this draws on today, and what it does not
The mission-decomposition workflow, the proposed-to-approved review lifecycle, and the signed audit chain behind every action are working parts of the platform. What is not yet part of this: a mission-specific perception model trained on a given operator's own assets and terrain, which is exactly what an initial pilot would build. The UAV's deterministic flight controller remains outside the platform's scope entirely, by design. The operational judgement in a UAV deployment would remain with the operator's own team throughout, and any mission-specific perception skill would be developed alongside them, not supplied as an off-the-shelf model.
Some of the architecture underlying this capability set is documented in filings still in progress. This page describes what the platform is designed to do, at a level appropriate for planning a pilot, not an implementation specification.
Platform features and interface are subject to continuous improvement. Descriptions in this guide may not reflect the exact layout or wording of the latest released version.