Proposed

COLREG-compliant hardware interlock the model cannot reason around

Stand-on/give-way and grounding envelopes in a certified box. The agent may propose; it may not disable the interlock.

No compiled flow or public database names this control yet.

Who should own it

Flag states and MASS vendors

Regulators

How quickly it can land

Weeks

A dedicated squad can land it inside two months.

Expedited implementation

6 weeks

45 calendar days with a crash team

Normal implementation

6 months

180 calendar days as a planned program

Risk this mitigates

MASS autonomy on spoofed seas

Given that the IMO MASS Code is in force for cargo ships, GNSS/AIS spoofing is an operational fact in several seas, and language models are being wired onto ECDIS, remote-ops, and port automation, there is a possibility of an autonomous or remotely operated ship acting on a confident false fix, a ghost AIS contact, or a prompt that reaches steering resulting in collision, grounding, a blocked strait or port, pollution, and casualties — plus a trade shock if the failure clusters.

Residual composite 24 · still above the threshold

Effect if implemented

Applied to every failure scenario on that risk, then re-ranked. Axes are clamped at 1.

Likelihood: −0
Consequence: −1
Urgency: −1