A documentation blind spot

Your fleet has a documentation blind spot.
We close it.

Cited answers. Verified citations. Transparent confidence. Onboard every vessel.

Works when the link drops · SMS data stays on the ship

↓ DESCENDING

Chatbots hallucinate. RAG approximates.
We retrieve, cite, and refuse when we can't.

LAT 51° 29′ NLON 0° 00′ WBEARING 180°
Full Fathom AI — Crew AssistantOnboard · Offline
What do I do in a man overboard situation?
HIGH CONFIDENCE
Immediate actions — complete in order:
  1. 1.Mark position — activate MOB waypoint on GPS[1]
  2. 2.Throw lifebuoy with light and smoke marker[1]
  3. 3.Post lookouts — minimum two, continuous visual[1]
  4. 4.Sound general alarm — three long blasts[1]
  5. 5.MAYDAY / PAN-PAN on VHF 16 if required[1,2]
  6. 6.Launch rescue boat with trained crew[1,2]
  7. 7.Notify Coast Guard and nearby vessels[2]
  8. 8.Continue search until located or officially suspended[2]
  9. 9.Headcount and muster — verify all crew[1]
1Safety Management Manual — §7.2, p.11SMS
2Bridge Emergency Procedures — §2.4, p.8Vessel
Citations verified · 9 / 9 claims grounded in retrieved context

Running onboard. No internet required.

The ISM gap

The SMS only works if the crew can find the right procedure in time.

4,103

ships detained by Paris MoU Port State Control in 2024 — a 4.03% detention rate, up from 3.81% the year before.

Source · Paris MoU 2024

17.2%

of Paris MoU deficiencies in 2024 fell in fire safety — the single largest category. ISM-related deficiencies appear in 4.6% of cases.

Source · Paris MoU 2024

77,526

deficiencies recorded by Tokyo MoU across 26,140 inspections and 1,189 detentions in 2024. 54% fell in just four categories.

Source · Tokyo MoU 2024

70–78%

of maritime accidents analysed in peer-reviewed HFACS studies of MAIB, TSB and NTSB casework are attributed to human factors — with a recognised class characterised by non-compliance with the SMS.

Source · MDPI 2023 HFACS analysis · Taylor & Francis 2025

“The procedure existed. The crew could not find it in time.”

That is an ISM finding, not a technology problem — and it's what we help you close.

The problem

A single vessel carries 1 pages.The crew sees one at a time.

SMSSMS §8.1

Fire Response

1
2
3
4
VesselBEP §2.4

Bridge Emergency

1
2
3
4
RegulationSOLAS III

SOLAS III — LSA

VesselMUST-01

Muster List

RegulationRR 19

COLREGs Rule 19

SMSSMS §11.3

Enclosed Space Entry

1
2
3
4
VesselSTB-09

Stability Booklet

SMSSMS §7.2

Man Overboard

1
2
3
4
ReferenceRef §4

Bridge Team Mgmt

SMSSMS §6.4

Anchor Watch

1
2
3
4

Full Fathom sees every page at once — and ranks SMS above regulation, vessel above reference, by design.

Four steps to operational safety intelligence

01

Upload

Upload your SMS manuals, procedures, and regulatory references. We parse, chunk, and build an AI knowledge index — preserving tables, numbered procedures, and cross-references.

02

Deploy

Download a 5GB bundle to each vessel. Runs on any mini-PC. Zero internet required. Crew access it through a browser on any device connected to the vessel network.

03

Trust

Every answer shows its source tier (SMS, vessel, regulation, reference), a High / Medium / Low confidence badge, and whether each citation is verified against what was actually retrieved. Crew see at a glance whether to act or verify.

04

Learn

See what your crews are asking. Find documentation gaps. Identify procedure hotspots and confusion signals. Fix them before the next audit.

Same prompt, three systems. One survives scrutiny.

Crew prompt“Man overboard?”
Generic chatbot
Cloud · Trained on web

Sure! Man overboard is a serious situation. Stop the vessel as quickly as possible, throw a life ring or flotation device, and keep the person in sight at all times.

Alert all crew and begin a rescue operation. You may want to contact the coast guard on VHF channel 16 if needed. Remember to maintain situational awareness and ensure the safety of your crew during the rescue.

Hope this helps! Let me know if you have any other questions.

No sources provided · Not grounded in vessel documentation
Source cited
Verifiable
Actionable
Hallucinated
Invented generic advice. No procedure ID. Vessel has no record of these steps.
Enterprise RAG
Cloud · Document search

Based on your documents, responding to a man overboard situation involves stopping the vessel, marking the position, deploying rescue equipment, and notifying authorities. The master and crew should follow your vessel's specific MOB procedure.

Please refer to your Safety Management Manual and applicable regulations for the complete procedure.

1smm.pdfUNVERIFIED
2emergency_procedures.docxUNVERIFIED
Source cited
~Verifiable
Actionable
Summary only
Paraphrased nine critical steps into prose. Not ordered. Not actionable. Citations unverified.
Full Fathom AI
Onboard · Offline
Complete in order immediately. Based on vessel SMS §7.2 and Bridge Emergency Procedures §2.4.
  1. 1.Mark position — activate MOB waypoint on GPS[1]
  2. 2.Throw lifebuoy with light and smoke marker[1]
  3. 3.Post lookouts — minimum two, continuous visual[1]
  4. 4.Sound general alarm — three long blasts[1]
  5. 5.MAYDAY / PAN-PAN on VHF 16 if required[1,2]
  6. 6.Launch rescue boat with trained crew[1,2]
  7. 7.Notify Coast Guard and nearby vessels[2]
  8. 8.Continue search until located or officially suspended[2]
  9. 9.Headcount and muster — verify all crew[1]
1Safety Management Manual — §7.2, p.11SMS
2Bridge Emergency Procedures — §2.4, p.8Vessel
3COLREGs — Rule 2 (Responsibility)Regulation
Citations verified · 9 / 9 claims grounded in retrieved context
Source cited
Verifiable
Actionable

In a fire, one missed step is a life. Only grounded answers belong at sea.

The pipeline

Fifteen stages. Every question.

No single model answers your crew. Every question passes through an engineered pipeline before a word reaches the bridge.

01

Question Sanitisation

Production-hardened input handling

“Fire drill…”

Strips typographic characters that would break downstream processing.

02

Query Decomposition

Compound questions split into retrieval paths

"man overboard in TSS?" MOB procedure query A · SMS TSS navigation rules query B · COLREGs merged · RRF

Two-part questions become two searches whose results are merged.

03

Domain Vocabulary Expansion

Bridges crew language to regulatory text

“night transit”darknessnav lightssunset

Twenty curated maritime mappings so phrasing never blocks the right document.

04

Multi-Signal Retrieval

Semantic + keyword, mathematically fused

BM25 · keyword semantic · vector scanning 18,432 chunks top 20

Two independent searches converge via Reciprocal Rank Fusion.

05

Relevance Feedback Expansion

Second-pass retrieval at zero LLM cost

The system searches again using the best first-pass results as seeds.

06

Neural Reranking

Cross-attention precision scoring

cross-attention score ↑ top 3 rise

Twenty candidates re-scored by a dedicated model; the top three rise.

07

Authority Hierarchy

SMS outranks regulation, by design

VesselSMSFleetRegulationReference

Tier multipliers nudge rerank scores so your procedures lead and regulations corroborate.

08

Confidence Gating

Multi-threshold quality control

hardsoft

Scores below hard threshold are discarded; below soft, the model is told to flag uncertainty.

09

Self-Correcting Search

Detects its own failures and retries

“what's MOB?” “man overboard procedure”

Rewrites in formal regulatory vocabulary and runs a second retrieval pass.

10

Intelligent Context Assembly

Parent-child expansion, diversity enforced

MOB procedure §7.2step 7 of 9+ steps 1-6, 8, 9

Retrieved chunks pull in their parent section so procedures never arrive truncated.

11

Attention-Optimised Ordering

Matching how language models actually read

bestbest

Most relevant material placed at start and end of context -- the high-attention zones.

12

Cited Answer Generation

Every claim traced to its source

[1][2][3][4]every claim cited

Inline numeric citations generated with the answer, resolved to doc/section/page.

13

Citation Validation

The hallucination guard

[1] Activate MOB waypoint on GPS [2] Throw lifebuoy with light and smoke [3] Post minimum two lookouts [4] Sound general alarm — three blasts [5] Auto-launch rescue drone [6] Launch rescue boat [7] Notify Coast Guard on VHF 16 [8] Headcount and muster 7 / 8 grounded · 1 flagged

Every citation number is checked against the chunks that were actually retrieved.

14

Sufficient-Context Autorater

Based on Google ICLR 2025 research

contextsufficientpartialinsufficient

A second model checks whether the context actually contained enough to answer.

15

Confidence Scoring

High / Medium / Low with transparent reasoning

rerankdiversityverifiedself-correctHIGH

Four signals combine into the badge the crew sees. Refusals are length-aware.

All fifteen stages run per question — offline, on vessel hardware. 290 tests gate every build.

What we stand behind

Four things we'll commit to in writing.

Two quantitative facts about the runtime itself. Two qualitative facts about how it behaves. The numbers you really want — latency, retrieval quality, corpus performance — we measure per build on the reference rig and publish under pilot.

0

engineered stages per answer

Sanitise · decompose · retrieve · rerank · rank by authority · gate · self-correct · assemble · order · generate · validate · autorate · score.

0 MB

runtime binary, one file

The onboard server. Statically linked. Cold-start under two seconds on the reference build. No internet required.

Every

citation validated before the crew sees it

If the answer cites a source, the validator checks it against the chunks actually retrieved. If it does not pass, the crew sees a warning — never a confident fabrication.

Refuses

when the context is insufficient

A Google ICLR 2025-style sufficient-context autorater inspects the retrieved context independent of the generated answer. If the context cannot support the question, the system says so.

Internal measurements refer to the current reference build on the Propel Group engineering rig. They are representative, not contracted. Your fleet measurements will differ; we size hardware as part of the pilot.

The artefact

27 megabytes. One file. One ship.

Everything you have seen so far — the retrieval stack, the authority hierarchy, the citation validation, the confidence scoring — ships as one statically-linked binary. This is the real startup sequence, with real latencies, from the runtime on a vessel.

ubuntu@mv-oceanic-test : ~
$ fullfathom serve --bundle /opt/fullfathom/bundle
fullfathom 2.1.0 (Darwin / Metal)
Loading bundle from /opt/fullfathom/bundle
Verifying SHA-256 checksum...ok(0.12s)
Loading vector index...3,717 chunks(0.21s)
Loading keyword index...3,717 entries(0.08s)
Loading vessel config...ok(0.02s)
Initialising RAG pipeline
Embedding model loaded1024-dim(0.41s)
Reranker loadedok(0.30s)
Semantic cache opened0 entries
Query logger opened0 entries
RAG pipeline ready
FullFathom AI server starting0.0.0.0:8080
FullFathom AI is ready -- open http://localhost:8080 in a browser
290 tests passed. 0 failures.
binary size 27 MB · cold start < 2s · no internet required

Category comparison

Why Full Fathom vs. general AI assistants

The maritime safety stakes are different. The requirements on the AI have to be different too.

Cites sources
Generic chatbot
No
Enterprise RAG
Document-level
Full Fathom AI
Chunk-level with page numbers
Verifies citations
Generic chatbot
Enterprise RAG
Full Fathom AI
Yes — flags unverified
Shows confidence
Generic chatbot
Enterprise RAG
Full Fathom AI
High / Medium / Low with reasoning
Shows source tier
Generic chatbot
Enterprise RAG
Full Fathom AI
Vessel / SMS / Regulation / Reference
Safety-critical completeness
Generic chatbot
Summarises
Enterprise RAG
Summarises
Full Fathom AI
Full mandatory procedure enforced
Refuses when uncertain
Generic chatbot
Enterprise RAG
Sometimes
Full Fathom AI
Always, with transparent rationale
Runs offline
Generic chatbot
No
Enterprise RAG
Varies
Full Fathom AI
Fully offline by design
Ingests your procedures
Generic chatbot
No
Enterprise RAG
Yes
Full Fathom AI
Yes
Maritime-aware ranking
Generic chatbot
No
Enterprise RAG
No
Full Fathom AI
Yes — SMS outranks regulation

Built for three roles

The crew asks. The DPA audits. The fleet learns.

Onboard
Onboard crew assistant welcome screen with suggested safety-critical questions.

For crew onboard

  • Ask in plain English — no training required
  • Every answer cites the source document, section, and page
  • Works when the link drops; runs on the vessel network
  • Accessible from any browser — desktop, tablet, phone
See the onboard assistant
Accountable

For the DPA / HSEQ team

  • Prove your SMS is followed with a query + citation log per vessel
  • Map every answer to an ISM Code element and a PSC category
  • Authority hierarchy ensures your SMS leads, regulation corroborates
  • Refuses rather than guesses when context is insufficient
See the DPA page
Ashore
Shore-side analytics dashboard showing query volume and knowledge gaps across a 12-vessel fleet.

For fleet managers & superintendents

  • Deploy once, update on port calls
  • See what crews ask, and what the system couldn't find
  • Documentation gaps surface as unanswered questions
  • Filter by vessel, vessel type, and time period
See the shore-side dashboard

Built for safety-critical operations

Fully Offline

All inference happens onboard. No cloud processing of queries.

No Crew PII

Query logs contain no personal data. Zero crew identification.

Verified Citations

Every citation is checked against what was actually retrieved. Invented or mismatched citations are flagged with a warning — not shown as facts.

Confidence Transparency

Every answer shows High, Medium, or Low confidence with a tooltip explaining why. Crew know when to trust and when to verify.

Authority Hierarchy

Your SMS procedures outrank generic regulation by design. Vessel > SMS > Fleet > Regulation > Reference, with every source tagged.

Safety-Complete Procedures

Man overboard, fire, enclosed space: we return every mandatory step, not a summary. Completeness enforced by design, not hoped for.

ISM Aligned

Supports ISM Code compliance evidence across Sections 6, 7, and 12.

Tamper-Evident Bundles

SHA-256 checksums on every bundle. The runtime refuses to load a file that has been altered in transit.

Your Data, Isolated

Full multi-tenant data separation. No cross-tenant access.

Hardware requirements

Runs on hardware most vessels already have. No GPU required.

 MinimumRecommended
CPUx86_64, 4 coresx86_64, 8 cores
RAM16 GB32 GB
Storage100 GB SSD256 GB SSD
GPUNot requiredNot required
NetworkVessel LANVessel LAN
Pricing · one plan, four bands

One Fleet plan. Per vessel, annual.

USD, annual billing, volume bands by fleet size. Setup fee scales with Band A and is waived for design partners. Premium features priced per fleet per month.

Band A
≤ 10 vessels
$100/vessel/mo
Band B
11–25 vessels
$85/vessel/mo
Band C
26–99 vessels
$70/vessel/mo
Band D
100+ vessels
from $55/vessel/mo

— The deep end —

Bring certainty onboard. Prove it ashore.

Two months, two vessels, no card. Your SMS ingested, your crew using the real product onboard. Decide at the end of month two.

© 2026 Full Fathom AIBuilt for vessels without internet