01 / Assembly
The port call is assembled, not typed
Vessel particulars, movements, the declaration on file, the ship's own record and the port profile are joined into one canonical record aligned to the IMO FAL forms. Coverage is stated as two numbers: what the authority's feeds can give, and what the whole set needs.
02 / Provenance
Every field says where it came from
The authority's movements feed, the ship's master, the port profile, or absent. A master's figure outranks a feed; a stale default never silently outranks a live record. The provenance travels into the filing evidence.
03 / The human gate
Nothing is filed unconfirmed
A declaration is drafted, validated against the authority's own published schema and code sets, then stopped. A person echoes a confirm phrase bound to that exact payload. A different payload has a different phrase; a confirmation cannot be reused.
04 / Evidence
Every exchange is a record
Request, response, the risk screen and the voyage as they stood, who confirmed, and a hash of the payload — kept per filing, backed up, and readable later as "filed with this ETA, at this speed, this far out". The pilot suite keeps a hash-chained trail of its own, anchored off-site.
05 / Agent-native
An MCP server, not a chatbot
The engine exposes its capabilities over the Model Context Protocol — assemble, draft, screen, file, amend, the voyage, the clock, the record. The agent that uses it holds no port logic of its own. Any agent, system or AI can call the same tools; the gate applies to all of them.
06 / Offline where it matters
The bridge has no signal. The page still works.
The pilot's core flow and the master's pack both run with no connection — the plan, the under-keel clearance from embedded data, the figures, the documents — and lodge when the link returns, without filing twice. Shore roles use live data; the rule is per context, not a slogan.