The DPA's job is to prove the SMS is followed. Ours is to give you the evidence.
Every crew answer maps back to a document, a section, and a page. Every citation is validated against the retrieved source before it reaches the bridge. When the system cannot answer from your SMS, it says so rather than guess.
Every query and every answer is logged onboard with its cited source and confidence score. Hand your inspector the log, not the excuse.
The runtime executes on the vessel. It works when the link drops, in restricted waters, or when SMS data cannot leave the ship.
Retrieval ranks by authority — SMS outranks regulation, vessel outranks reference. The crew sees the tier, the document, and the page.
Your SMS leads. Regulation corroborates.
Every document in the bundle carries its authority tier — vessel-specific, company SMS, fleet-type, regulation, or reference. Retrieval and reranking weigh tier into the final score; near-ties break in favour of higher authority.
- SMS outranks generic regulation; vessel-specific procedures lead every answer where they exist
- Tier pill visible on every cited source, for every answer
- Configurable per fleet — if your fleet uses a different tier ordering, the bundle encodes that
Every citation checked against the source.
When the model generates an answer with inline citations, every bracketed number is validated against the chunks actually retrieved. A citation that does not pass the check is surfaced as a warning, not a confident fact.
- No more invented references to documents that do not exist
- Missing-citation cases inject a Sources block automatically so every non-refusal answer carries provenance
- A sufficient-context autorater independently checks whether the context could even support the answer
What shore sent is what ship runs.
Every bundle is SHA-256 checksummed at build, transferred with its checksum, and re-verified before apply. Verification failure rejects the update and keeps the previous bundle running. Automatic rollback on any post-apply failure.
- No partial-update state exists — either a verified bundle applies or the previous one continues
- Fleet manager dashboard shows which version every vessel is running
- Every failed apply is logged with the checksum mismatch details
The SMS data never leaves the ship.
Inference executes on the vessel. Query content stays onboard. Only anonymous aggregates flow shore-side, and only when the operator has opted in. Crew PII is stripped before any upload.
- No external API calls during a query
- Crew identifiers are stripped before any shore-side aggregation
- Shore-side analytics show topic coverage and frequency, never individual identities
Three different inspections. The same product.
When an inspector asks whether the crew knew the procedure, you show them the query log, the cited source, and the confidence score the crew saw. Evidence, not argument.
Pull the log per-vessel per-quarter. Show frequency of queries, share of SMS sources cited, and the near-zero rate of ungrounded answers. Map directly to ISM Elements 6, 7, 10 and 11.
Retrieve every question asked in the 72 hours before and after the incident. Which procedures were consulted, which documents were cited, where the SMS was reachable and where it was not.
Straight answers. No hand-waving.
Is this just another chatbot?
No. A generic chatbot has no idea what your SMS says. Full Fathom ingests your actual documents, ranks by authority (your SMS over generic regulation), validates every citation against retrieved context, and refuses when the context is thin. If you have ever seen a chatbot invent a clause, you have seen why this matters.
What about offline and bandwidth?
Inference is onboard. There is no cloud call during a query. Bundle updates travel shore-to-ship on VSAT, port broadband or USB — your choice. The product is designed around the link dropping, not around it working.
What about our charterers and class?
We share the query and citation log with flag, class or charterers only at your direction. The architecture keeps SMS data on the vessel by default; your counsel decides what moves off.
How do we retire it if we need to?
The onboard binary is a single file and the bundle is a single file. Remove both and the vessel is where it started. No hidden state, no lock-in, no background sync to a cloud you can't disable.
— Two vessels. Two months. Free. —