The context we bring — six ship-side workflows on Class NK data
Before any of the patterns on this site, we have been operating on Class NK data for several years — on the ship-operator side, for ship-operator clients who interact with Class NK every day.
This page documents that work. It exists so the rest of the site reads as it was meant: derived from operational context, not from outside speculation.
Workflow 1 — Class NK portal data ingestion
We pull certificate status, survey records, and defect entries from the Class NK portal on behalf of ship operators. The data lands in their LifeOS AI workspace, indexed and searchable. Agents track changes between portal visits and surface new events.
Coming this page: screenshot of the portal data agent at work — to be added by Sriram, Wed 27-May.
What this proves to Class NK: we know your portal shape. We know the data fields. We know the update cadence. When we talk about the inside of Class NK systems, we are not guessing.
Workflow 2 — Certificate lifecycle tracking
For every vessel a ship-operator client manages, we track all Class NK certificates: issue date, expiry date, renewal triggers, evidence requirements. Agents send renewal alerts to the technical superintendent at the right time. Evidence is gathered automatically from related casefiles.
Coming this page: screenshot of a certificate dashboard with renewal alerts.
What this proves to Class NK: we already operate on your output stream, daily. We see the experience of being on the receiving end of Class NK’s process.
Workflow 3 — Defect tracking and follow-up
When a Class NK surveyor raises a defect, we capture it into the vessel’s casefile. Agents follow up on rectification timelines. Status changes propagate back. Audit trail is preserved.
Coming this page: screenshot of a defect casefile in flight.
What this proves to Class NK: we already coordinate around your defect workflow — we know its rhythm and pain points.
Workflow 4 — Docking schedule coordination
Docking is when most major Class NK survey work happens. We coordinate vessel docking schedules around survey windows, contractor availability, port slot availability, and crew rotation. Agents flag scheduling conflicts before they become operational problems.
Coming this page: screenshot of a docking schedule view with survey overlay.
What this proves to Class NK: we sit in the operational planning seam where Class NK schedule intersects everything else.
Workflow 5 — Email coordination with Class NK surveyors
Ship-operator clients send and receive a constant stream of email with Class NK surveyors — survey scheduling, defect clarifications, evidence requests, follow-up. Our agents draft replies, track open threads, and remind humans when a Class NK surveyor is waiting on a response.
Coming this page: anonymised example of an email thread being managed by an agent.
What this proves to Class NK: we already help operators communicate with you. We see what makes those communications easy and what makes them hard.
Workflow 6 — End-to-end issue lifecycle
When something goes wrong on a vessel — equipment failure, audit finding, incident — Class NK is one of many parties involved. We manage the full issue lifecycle: open the casefile, gather evidence, coordinate with Class NK and other stakeholders, close the loop with documented resolution.
Coming this page: screenshot of an issue casefile spanning multiple stakeholders.
What this proves to Class NK: we already orchestrate work where Class NK is one of several parties — exactly the muscle needed to run an orchestration layer inside Class NK itself.
A natural symmetry
What we do on the operator side mirrors, in shape, the work Class NK does on the institutional side. The orchestration layer is the same; what differs is whose desk it sits on.
| On the operator side (today) | On the Class NK side (the patterns on this site) |
|---|---|
| Pulling data from Class NK portal | Validating data clients push into Class NK systems |
| Tracking certificate lifecycle | Surveyor support around certificate issue and management |
| Defect tracking + follow-up | A defect casefile pattern inside the class society |
| Docking schedule coordination | Survey workflow at the class side |
| Email coordination with surveyors | Surveyor productivity surfaces |
| Issue lifecycle across stakeholders | Department agent teams |
Coming this page: a single diagram showing the external↔internal symmetry.
The shape carries across. That is why the three patterns elsewhere on this site are written as patterns derived from operational context rather than as features designed in a vacuum.
Notes on data access
All the workflows above operate on data the ship operator is already entitled to access — the operator’s own portal account, their own emails, their own casefile contents. MetaWeave does not have privileged Class NK access. We are agents on the operator’s side, doing what an operator would do — faster.
That is precisely why we know the outside view of Class NK so well. And why we believe the inside view will reveal even more.