Delivered
Present in the handover package and usable — readable, current revision, matching the agreed document schedule.
Service · Emerging
Know what the yard actually handed over.
A fixed-scope Handover Information Readiness Assessment & Exceptions Register, delivered at new-build handover or during warranty — while the document schedule is still a contractual obligation, and the owner still has leverage.
Produced by Cairn, our offline vessel knowledge system. An onboard deployment is available as a follow-on.
Request a readiness auditThe problem
A new build hands over with thousands of documents — manuals, as-builts, vendor packs, certificates — and nobody can say what is missing until it is needed at 0200 with a system down.
By then the warranty clock has run and the leverage is gone. The time to find the gaps is at delivery, against the document schedule the yard signed.
The deliverable
Every document, in one of four states.
The register scores the delivered package against the yard's contractually agreed document schedule. Each item lands in exactly one column — and the exceptions are the instrument the owner's team takes back to the yard.
Delivered but unusable
Present but failing in practice: scanned pages with no readable content, superseded revisions, files that do not open.
Referenced, never delivered
Documents the package itself points to — drawings cited by other drawings, manuals named in schedules — that are not in the delivery.
Absent
On the contractually agreed document schedule, with no trace in the package at all.
The package evidences its own gaps: on a real 448-document handover package, 49 drawings were cited by other drawings and never delivered — found automatically. Cairn also reads drawing title blocks that contain no machine-readable text, so it can find a drawing by number even when the PDF has nothing to search.
How it works
Four properties, all checkable.
Indexed in place
Your folder structure is not changed, moved, or renamed. Crews keep the folders they know; Cairn reads them where they are.
Every answer cited
Answers point to the source document and where it lives on your file server — not a paraphrase, a location.
Survives reorganisation
Locations resolve by document content, not a stored path. If someone reorganises the folders, answers still point to the right file.
Nothing leaves the vessel
No cloud service, no API calls, no telemetry. Local models throughout — even the report generator runs behind a fetcher that denies all network access. It cannot phone home.
Boundaries
What it is not.
- Not a generic chatbot. Built around your documentation, with citations and explicit unsupported-answer boundaries.
- Not a multi-tenant SaaS product. Each deployment is single-vessel, single-client, and stays under your control.
- Not a replacement for engineering judgement. It makes good engineers faster; it does not substitute for them.
- Not finished security. Access in the current beta is gated by one shared password covering search, questions, and document download. There are no per-user accounts or permissions yet — if you need role-based access, say so and we will tell you honestly where that sits on the roadmap.
Method note
Completeness scoring is documented and disclosed with every report, so each line of the register can be contested against the method rather than against an opinion.
Retrieval currently measures 96.8% recall@8 — against a gold-standard question set written in-house, on one vessel corpus of 448 documents (10.4 GB, 2,099 files). That is one vessel and a self-authored test set, so treat the number as indicative: it is re-measured on each vessel's own documentation as part of the engagement. On the same corpus, the negative-control set — questions chosen to have no answer in the documentation — produced zero unsupported assertions: where the documents cannot support an answer, the system says so.
FAQ
Common questions.
- Do you move our files?
- No. Documents are indexed in place on your existing file server. Nothing is renamed, restructured, or copied into a proprietary store — and answers keep pointing to the right file even after folders are reorganised.
- Does it work offline?
- It only works offline. There is no cloud component to fall back on: models run locally and the system makes no network calls at all. That is an architectural property, not a configuration option.
- What if our documentation is incomplete or wrong?
- That is a finding, not a failure. The system is designed to expose gaps and contradictions rather than smooth over them.
- Who can see what?
- In the current beta, everyone with the shared access password sees everything — search, answers, and downloads. There are no roles or per-user permissions yet. We would rather state that plainly than imply access control that does not exist.
- What does the yard say about the register?
- The register is built to be challenged. How completeness is scored is documented and disclosed with the report, so a yard can contest any line item against the method rather than against an opinion. A documented method is what survives that conversation.