VoyageMV Helios
DischargingDemurrage exposure?
ArtifactDRAFT
Laytime statement — MV Helios
ExposureUSD 78,400
Every voyage, every document, every decision — coordinated by AI, approved by you.
A single voyage touches fifteen systems. IMOS for the P&L, Q88 for the vetting, DA-Desk for disbursements, email for the charterparty, AIS for the position, spreadsheets for every figure that doesn’t fit anywhere else.
Every question — is the laycan still clean? what’s our demurrage exposure? did we ever sign the addendum? — means opening four tabs and reconciling them in your head.
Sephra sits above IMOS, Q88, DA-Desk, email, and every spreadsheet — the agentic layer that reads from your systems, writes back to them, and handles the voyage-level busywork on your behalf. Your systems of record stay where they are. Your team stops opening them.
Ask a question. Sephra queries the stack and cites the source. Ask for a draft. Sephra composes it from the IMOS P&L, the SOF entries, and the CP. Kick off a workflow. Sephra runs it across every system it needs — and routes every output through your approval before anything ships.
Every fixture gets its own scoped workspace — context, memory, and document hold included.
Yes. NOR was tendered on 15 Apr 11:00, within the laycan window CP_Athena.pdfp. 6 (13–17 Apr).
Master’s acceptance logged in SOF_Athena.pdfp. 1.
A small set of composable parts, each doing one thing with craft. Scroll to see them work.
Fixing, loading, at sea, discharging, closing. Every stage of the voyage has its own memory, its own documents, its own agents — scoped to the cargo in motion.
Every chat assembles the right context automatically — voyage documents, global memory, relevant skills. Ask a question, get a grounded answer with citations.
Three material deviations from your standard template:
Laytime statements, handover notes, commercial summaries — composed row by row, cited to source, ready for your edits and your signature.
| Date / Time | Event | Hours | Counted | Cumulative |
|---|---|---|---|---|
| 16 Apr 08:00 | NOR tendered | — | — | 0.00 |
| 16 Apr 14:00 | Laytime commences | +6.00 | 0.00 | 0.00 |
| 17 Apr 00:00 | Discharging | 24.00 | 24.00 | 1.00 |
| 18 Apr 00:00 | Discharging | 24.00 | 24.00 | 2.00 |
| 18 Apr 09:15 | Rain stoppage | 4.25 | 0.00 | 2.38 |
| 19 Apr 00:00 | Discharging resumed | 19.75 | 19.75 | 3.20 |
| 20 Apr 12:00 | Allowed laytime expires | — | — | 4.50 |
| 23 Apr 18:30 | Discharging complete | 78.50 | 78.50 | 7.77 |
Close this voyage. Summarize the CP. Reconcile the SOF. Named, structured, auditable workflows run step by step with progress you can watch and approve.
Reusable orchestrations built on the open Agent Skills standard. Advanced operators trigger them with slash commands. Your team authors them, owns them, and extends them.
Upload once. Sephra classifies every file — CP, SOF, NOR, BL, email, invoice — with a confidence score you can audit. Voyage-scoped or fleet-wide, searchable in plain English.
Yes — MV Athena’s NOR was tendered at 15 Apr 11:00 Rotterdam, within the laycan window of 13–17 Apr specified in CP_Athena.pdfp. 6 · clause 4CP_Athena.pdfp. 6 · clause 4"Laycan: 13th April 2026, 00:01 hrs, through 17th April 2026, 23:59 hrs, at discharging port.". Master’s acceptance was logged in SOF_Athena.pdfp. 1SOF_Athena.pdfp. 1NOR received and accepted by Master at 15 Apr 11:00 local time. No free pratique remarks. with no objection.
The BL instructions were issued by Nikos Papadakis, Trafigura chartering, on 14 Apr 16:22 UTC, per email_npapadakis_2026-04-14.emlFrom: Trafiguraemail_npapadakis_2026-04-14.emlFrom: TrafiguraSubject: MV Athena — BL instructions. Please issue BLs to order, blank endorsed, three originals, notify Sasol Rotterdam., and countersigned by your operator Dara Chen at 14 Apr 18:05 UTC in approval_log.jsonentry #1842approval_log.jsonentry #1842{"actor":"dchen","action":"approve_bl_instructions","voyage":"VOY-2026-0176","at":"2026-04-14T18:05:11Z"}.
No hallucinated clauses. No invented timestamps. Every assertion in this reply is grounded in a document you uploaded.
Hover any highlighted citation — Sephra shows you the exact source line from the document you uploaded.
No. Sephra sits on top — it reads the documents and data you already produce in IMOS, Q88, DA-Desk, email, or any in-house system you run. Your systems of record stay where they are.
Yes. SDAs, port logs, NORs, statements of facts, broker emails — in any language, in any format they arrived. Sephra reads, normalizes, and shows you the source line so you can verify.
It drafts, summarizes, and flags. It does not practice law. Every output is grounded in your documents and marked with its sources so your team — or your counsel — can verify.
You'll see the source. You'll see the reasoning. You'll catch it before it ships, because nothing ships without you. That's the whole point of the human-in-the-loop design.
Yes. Sephra's skills are built on an open, markdown-based standard. Your team authors them. Your team owns them.
Sephra works with a handful of operators today. If you run voyages and you’re tired of running them across fifteen tools, we’d like to talk.