Evidence-grade by architecture. Auditable by design.
Every capability below maps back to a specific ISM Code element or PSC inspection category. Every answer the crew receives is audit evidence by construction — cited, validated, logged.
Reference · IMO ISM Code 2018
The ISM Code puts the burden of evidence on the Company. Full Fathom produces the evidence for the four elements that most often show up in ISM-related findings.
- Obligation
- Resources & personnel — crew are familiar with rules, procedures and instructions relevant to their duties.
- How Full Fathom supports it
- Crew query the SMS in natural language and receive the exact procedure, in order, with the document/section/page citation.
- Evidence produced
- Query log + cited source per answer
- Obligation
- Shipboard operations — key operations are identified and procedures established and documented.
- How Full Fathom supports it
- Authority hierarchy places vessel-specific and SMS procedures above generic regulation. Answers show the tier that governs.
- Evidence produced
- Tier pill + source chain per answer
- Obligation
- Maintenance of ship and equipment — procedures recorded and followed; deficiencies reported.
- How Full Fathom supports it
- Maintenance and equipment manuals ingested alongside SMS; retrieval favours vessel-specific variants when present.
- Evidence produced
- Cited manual, section, and page
- Obligation
- Documentation — documents are available, current, and controlled.
- How Full Fathom supports it
- Every bundle is versioned and checksummed. The vessel shows which version is running; shore sees the fleet.
- Evidence produced
- Bundle version + SHA-256
The four categories where we most often see fleets want clean evidence in advance of Paris MoU and Tokyo MoU inspections.
- Obligation
- Inspector queries whether crew knew and followed the documented procedure.
- How Full Fathom supports it
- Replay the question the crew asked; show the procedure returned; show the citation validated at the time.
- Evidence produced
- Query + answer + citation + timestamp
- Obligation
- Evidence that crew were familiarised with ship-specific procedures (ISM 6.3).
- How Full Fathom supports it
- Aggregate query log shows per-crew topic coverage without PII; highlights under-queried critical procedures.
- Evidence produced
- Per-vessel familiarisation heatmap
- Obligation
- Procedures for emergencies and drills are available onboard and current (SOLAS / ISM 8).
- How Full Fathom supports it
- Emergency procedures pinned in retrieval priority; refusal-on-insufficient-context catches stale or missing instructions.
- Evidence produced
- Citation chain to current bundle version
- Obligation
- Documented maintenance per manufacturer and SMS (ISM 10).
- How Full Fathom supports it
- Ingested manuals and maintenance procedures cited alongside vessel records.
- Evidence produced
- Cited section of the manufacturer manual
The four artefacts generated for every inspection.
Onboard ledger of every question asked, cited sources returned, confidence score, and timestamp. PII-stripped before any shore-side aggregation.
For every answer: the document name, the section, the page, the bundle version, and whether each bracketed citation validated at display time.
SHA-256 at build, transferred with the artifact, re-verified onboard before apply. Mismatches are rejected and logged.
When the system refused rather than guessed, why: insufficient-context verdict, low-confidence gating, or no grounded source found.
— Evidence over assertion —