Does it match the task?
Check the proposed mission against the requirements and examine the waypoint edits.
The mission workflow
NORM / 02Draft. Review.
Decide what proceeds.
Follow the planning process from the mission brief to operator approval and mission records. Each stage has a distinct purpose.
The mission workflow
From a brief
to a reviewed plan.
One thing matters to us: the original requirements must not get lost along the way. AI helps organize, interpret, and suggest. People still check conditions on the ground and approve actions involving a device.
Illustrated workflow · 01
Start with the task.
Bring the mission requirements into the workspace so the proposed plan can be reviewed against the original request.
Illustrated workflow · 02
Turn the brief into a proposal.
AI helps interpret the request and propose a mission plan. The proposal remains a draft for the operator to examine.
Illustrated workflow · 03
Review the route in detail.
Review and edit the proposed waypoints before deciding whether the plan is ready for approval.
Illustrated workflow · 04
Keep the decision with the operator.
Actions involving a vehicle require human approval. Approval is separate from the AI’s suggestion and from verification of the device result.
Illustrated workflow · 05
Keep the task and its records together.
Keep device mission records alongside the planning workflow. Full real-device transfer, verification, and limited control are still undergoing acceptance testing.
The mission workflow
From a brief to a reviewed plan.
One thing matters to us: the original requirements must not get lost along the way. AI helps organize, interpret, and suggest. People still check conditions on the ground and approve actions involving a device.
01 / Mission brief
Start with the task.
Bring the mission requirements into the workspace so the proposed plan can be reviewed against the original request.
02 / AI-assisted planning
Turn the brief into a proposal.
AI helps interpret the request and propose a mission plan. The proposal remains a draft for the operator to examine.
03 / Waypoint editing
Review the route in detail.
Review and edit the proposed waypoints before deciding whether the plan is ready for approval.
04 / Operator approval
Keep the decision with the operator.
Actions involving a vehicle require human approval. Approval is separate from the AI’s suggestion and from verification of the device result.
05 / Mission records
Keep the task and its records together.
Keep device mission records alongside the planning workflow. Full real-device transfer, verification, and limited control are still undergoing acceptance testing.
Review the plan.
Verify the result.
The planning workflow and the device result answer different questions. A plan can be ready for review while hardware acceptance remains incomplete.
Has the operator approved it?
Approval is a human decision. An AI suggestion does not grant itself permission to act.
What happened on the device?
Mission retrieval, independent upload verification, and limited control still need their applicable acceptance checks.
The illustration describes the workflow.
It does not show a completed hardware upload or flight. The real-flight-controller path is still undergoing acceptance testing.
See the current integration scope