A vessel or a port terminal operates under a dense stack of documents: class society rules, SOLAS and MARPOL provisions, ship and equipment manuals, dangerous-goods codes, and port-specific regulations that differ at every call. No single officer holds it all, connectivity at sea is intermittent, and a misread regulation at the gangway is a detention, a fine, or worse.
How OEP fits
- Rules and manuals become packs. Class rules, conventions, equipment manuals, and port regulations are page-anchored and versioned; the provision that applies is retrievable by exact reference.
- The answer carries the regulation. A dangerous-goods or procedure question returns the controlling text and its source, so the officer acts on the document, not recollection.
- Built for the bridge and the quay. Intermittent or absent connectivity is the normal case; packs run fully offline, which is the only honest design for a ship at sea.
- Per-port packs. Local regulations vary by call; a terminal or port-state pack carries exactly what applies there.
- Knowledge survives crew rotation. The pack is the operation’s memory across changing crews and shoreside staff.
What exists today
An architecture-relevant direction. OEP’s offline-first, page-fidelity, and versioned-corpus foundations fit the maritime constraint set unusually well; the work to make it real is the rules and regulation corpora, packaged and validated with a partner.
What we won’t tell you
We won’t claim a classed or flag-approved system, navigational authority, or any standing in safety-of-life decisions. It puts the controlling rule in the officer’s hands, offline, with its source. See how we bound our claims.