Six missions that need more than one machine
Each is set out as a concept of operations — the problem, the sequence, the force mix, and what degrades it. No case studies, because we have not earned any yet.
The asset that finds something and the asset that acts on it are usually the same machine, which means the decision to act is taken by whoever happens to be overhead. Observation, authorisation and action are three different responsibilities, and collapsing them into one platform collapses them into one moment.
Observation, authorisation and action held apart
An observing aircraft holds the target and maintains the track. It carries no effector.
A separate asset is positioned to be able to act, without being tasked to.
The operator authorises. No action is available to the system without this gate, and it cannot be delegated to an asset.
The acting asset executes against the track held by the observing asset.
The observing aircraft remains on station through and after the action.
The same observing asset reports the outcome, so assessment is not taken from the asset that acted.
5 assets, one operator
What degrades this, and what the system does about it
Stated plainly because an evaluator will find these anyway. Mitigations are design decisions, not guarantees.
An identification made at sensor range can be wrong, and the consequence is not recoverable.
Identification is presented with its evidence and its confidence, and the authorisation view states plainly what the system does not know.
If the link drops between authorisation and action, the acting asset is holding an instruction it cannot confirm.
Authorisation expires rather than persists. An asset that loses the link before acting returns to holding, and re-authorisation is required.
The target state the acting asset holds is as old as the last update it received.
Track age is shown at the authorisation gate, and authorisation is withheld by the system beyond a stated age rather than silently acted on.
The system cannot assess proportionality, necessity or the presence of non-combatants.
It does not attempt to. These are operator judgements, and the interface is built to present what is known rather than to recommend.
Take this mix into the fleet builder
Bring a mission, not a shortlist
We will walk the concept of operations against your requirement and say plainly where it does not fit.