The IMO's Maritime Safety Committee meets this month (MSC 111, May 13-22) to finalize and adopt the MASS Code, the non-mandatory regulatory framework for Maritime Autonomous Surface Ships. Eighteen of its chapters are done. The human element chapter is the last holdout. When the final text is adopted, it will formalize something yacht and cruise operators should pay close attention to.
An autonomous vessel must be able to operate safely without a continuous connection to shore.
That is not a ShipboardAI talking point. That is a regulatory position, written into the code that will shape classification standards, insurance requirements, and flag state expectations for the next decade.
What the code actually requires
The MASS Code is goal-based. It defines outcomes, not specific technologies. The required outcomes include collision avoidance, situational awareness, emergency response, and safe navigation. Each of those capabilities must function when the satellite link is degraded or absent.
If you have been following the sovereign AI case we have been making for the past year, this should sound familiar. The code does not use the phrase "sovereign AI." It does not need to. The functional requirement is identical: the vessel's intelligence must live on board, because a shore-side dependency that fails when the link drops is not a capability. It is a liability.
The timeline is worth your attention. MSC 112 in December 2026 will establish the experience-building phase, a structured period where operators demonstrate compliance and regulators collect data on what works. By July 2030, the committee targets adoption of a mandatory version. Entry into force: January 2032. That is not a distant horizon. In vessel procurement timelines, it is roughly one refit cycle away.
Why this changes the conversation
Until now, the sovereignty argument has been a design philosophy. A good one, but a philosophy nonetheless. The MASS Code shifts it from "smart architecture" to "regulatory trajectory."
Classification societies (DNV, Lloyd's, Bureau Veritas) will build their autonomous vessel notations on top of this code. Insurers will reference those notations when writing policies. Flag states will use the framework when issuing operating permits for vessels with autonomous functions.
If your vessel depends on a cloud API for any safety-relevant function (collision avoidance, stability monitoring, fire detection, man-overboard response) and that API requires an active satellite link, you are building against the direction this framework is heading. Not immediately. Not next quarter. But within the time horizon that matters for a vessel you are commissioning today.
The connectivity argument does not hold
I've watched this pattern before in military systems. A new operational requirement arrives. Half the industry responds by adding connectivity redundancy (a second Starlink terminal, a backup VSAT). The other half puts the capability on the platform.
The second group is always the one that passes the operational test.
The MASS Code will create the same split. Some operators will argue that dual-redundant satellite links satisfy the "operate without continuous shore connection" requirement. Regulators will counter that redundancy does not equal independence. Two links to the same cloud still fail in the same conditions: severe weather, geopolitical interference, provider outages. The Starlink outage that grounded Pentagon drone tests proved the point: when the single-provider link goes down, everything downstream stops.
The code's requirement is functional autonomy, not connectivity redundancy. Those are different things.
The build-or-wait question is answered
If you have been debating whether to invest in on-vessel AI infrastructure this year versus waiting for satellite bandwidth to improve, the MASS Code gives you your answer. Bandwidth is not the constraint. Autonomy is.
A vessel with local inference, local knowledge retrieval, and local sensor processing is already aligned with the code's direction. A vessel that routes everything through a shore-side data center will need a redesign before the mandatory version takes effect.
The experience-building phase starts in December. Operators who want to be in that first cohort, and want the classification advantages that come with early compliance, need local AI infrastructure on board before the window opens.
The knowledge ark earns its name
For the first time, an international regulatory body has codified the principle that a vessel's critical intelligence cannot depend on an external connection. The MASS Code didn't use our language. It didn't need to. The requirement speaks for itself: the vessel must think for itself when the link is gone.
That is the knowledge ark, written into regulation.
Evaluating how the MASS Code applies to your vessel's AI architecture? Let's talk. We design sovereign AI deployments that are ready for the regulatory framework today, not catching up when the mandatory code drops.