Platform · Autonomous vessels
A crewless ship cannot inspect itself.
Maritime Autonomous Surface Ships (MASS), remotely operated vessels, and defense USVs all share one structural gap: no crew to walk the hull, read the tanks, and file a condition report. Hullproof CoatingPassport is the structured, machine-readable condition-intelligence layer that replaces the missing human loop — IMO MASS Code and DNV AROS aligned.
Edge resilience has two layers
A crewless vessel has to keep deciding correctly when shore connectivity drops and when its own signals can no longer be trusted. The 2024–2025 GNSS-spoofing incidents — 117 vessels falsely placed at Beirut airport, the MSC Antonia grounding off Jeddah, the Front Eagle collision near Hormuz — proved the point. Edge resilience is two distinct layers:
Signal-integrity layer
Is my position real? Is my GNSS / AIS / network feed being spoofed? This is a cyber-physical, RF-domain problem — a specialist field, and not what Hullproof does. Dedicated maritime-cyber players own it.
Condition-integrity layer
Is my hull sound? My coating, my structure, my biofouling — degrading toward a failure no one is aboard to see? This is Hullproof. CoatingPassport is the condition-integrity layer, edge-deployable per CLAUDE.md §10E.
An autonomous vessel needs both, and they are complementary, not competing. Hullproof stays disciplined: we are the condition-integrity layer and a structured input to whatever vessel-decision-support system sits above. We do not build navigation, cyber, or signal processing — that focus is itself the future-proofing.
For autonomous-vessel programs
Operators, ROC builders, autonomous-shipping system integrators, and naval USV programs — the condition-intelligence layer is platform-tier, co-developed with your autonomy + assurance team. The vessels are being built now. The condition layer should be specified into them, not retrofitted.