Persistent context
Ports, protected waters, offshore assets and coastal corridors are difficult to observe continuously. A maritime domain awareness architecture can combine fixed sensors, public data, autonomous surface nodes, satellite context and analyst review into a more persistent operating picture.
The useful output is context: what appears normal, what changed, what needs attention and what evidence supports that view. Keel treats autonomy as one contributor to that picture, not as an automatic enforcement layer.
Sensor and data fusion
A serious maritime awareness workflow may draw on AIS, radar, satellite imagery, optical sensors, acoustic signals, environmental data and taskable robotic sensing. Each source has limits. AIS can be absent or misleading, imagery can be weather constrained, and local sensors need maintenance and calibration.
The design problem is provenance and uncertainty. Operators need to know where a signal came from, how fresh it is, how confident the classification is and which human should review it.
Human approval
Awareness does not equal authority. Any real-world response around protected waters, vessel activity or restricted areas would require the appropriate legal and operational authority.
Keel's current posture is a concept architecture for decision support: better sensing, better evidence trails and better review loops for authorised humans.
Where Keel fits
Keel's research direction is the connection between persistent ocean sensing and trustworthy maritime intelligence. That includes candidate vehicle roles, payload choices, telemetry, tasking, reporting and analyst workflows.
The site does not claim a deployed surveillance system, customer operation or enforcement capability.
Operational caveat
Use cases describe potential applications for autonomous maritime systems and ocean intelligence. Operational claims require verified hardware, software, safety, regulatory and customer evidence.