Representative mission scenarios

Public Scenarios

Public scenarios provide non-sensitive mission examples for ports, offshore energy, subsea routes and protected sites before any private technical or site-specific discussion.

Port ScenarioProcurement Briefing
Public Scenarios
Public Scenarios

Core system banner

Scenarios for public orientation only

Each scenario explains mission logic, platform layer, software layer, evidence route and disclosure boundary without publishing technical specifications or restricted procedures.

Public scenario gatewayDomain: Surface / Subsea / Fixed Site / AirSoftware: ARGUS-NEXUS / SHADOWCORE / VAULTGovernance: Human-commanded, controlled disclosure

Scenario summary

Four public routes into private mission briefing

01Port and Harbour Awareness

Waterside context, restricted water, berths, perimeter zones and operator-reviewed event records.

02Offshore Energy Protection

Remote assets, service routes, maritime approach context and infrastructure-owner reporting.

03Subsea Route Monitoring

Route baseline, change review, anomaly triage and subsea evidence route.

04Counter-UAS Awareness

Protected-site awareness, operator review, escalation governance and evidence-ready reporting.

Public boundary

Scenario visuals are representative

Governance boundary

Public information is deliberately limited

Technical specifications, deployment assumptions, restricted payload details, supplier data, operational methods and sensitive performance claims are available only through controlled review, lawful-use screening and appropriate confidentiality arrangements.

01Human command

Autonomy supports awareness, triage and decision support. Accountable humans remain responsible for review, authorisation and escalation.

02Lawful-use screening

Procurement, partner and public-sector conversations are handled through controlled qualification and mission context review.

03Evidence-ready records

Mission workflows are framed around what was sensed, fused, recommended, decided and reviewed.

04Restricted disclosure

The public website avoids sensitive methods, supplier details, operational procedures and protected technical designs.

Proof and evidence panel

Controlled disclosure route

What is publicMission architecture, operating domains, public-safe software roles, governance posture and representative pilot route.
What is privateTechnical specifications, restricted methods, site assumptions, supplier details, deployment configuration and sensitive performance claims.
What can be shown in briefingMission architecture, pilot scope, evidence workflow, governance route and appropriate non-sensitive configuration material.
What requires NDA or legal reviewRestricted technical review, supplier-enabled production detail, sensitive payload integration and any export-control-sensitive conversation.
What is not publicly disclosedOperational procedures, weaponisation details, cyber techniques, restricted technical drawings and uncontrolled autonomy claims.

Related routes

Continue through the Sky Shadow system

Port and Harbour AwarenessRepresentative port and waterside awareness route.Offshore Energy ProtectionOffshore asset and service-route awareness.Subsea Route MonitoringRoute baseline and anomaly-review scenario.Counter-UAS Protected SitesProtected-site awareness and governance route.Private BriefingQualified route for site-specific discussion.

Next step

Request a private mission briefing

Qualified procurement, partner, public-sector, infrastructure-owner and investor enquiries are routed through controlled review.

Request briefingView procurement briefing