KATLAS · FreightCierge
Cierge Labs · Journey Storybook · port-corridor exceptions
Cierge Labs / Journey Storybook / FreightCierge

The FreightCierge Journey

A port-corridor exception, stage by stage. Each card shows one role doing one thing well — KATLAS applies Custody, Authority and Receipts at the moment of decision, then hands off to the next role.

STAGE 01 / 05

Vessel Operations — exception detected

The corridor signal arrives from existing vessel and port systems.

Role
Vessel Operations
Incoming request
Storm narrows the tidal window into Greenport. MV Northern Wave reports an ETA slip of approximately 4 hours.
Evidence available
  • · Vessel telemetry · weather feed
  • · Berth window held by Port Operations
  • · Onward cut-offs flagged by Compliance
Local assessment
Vessel Ops can confirm the slip and propose a berth-window adjustment. It cannot decide yard reslotting or compliance release on its own — those sit with other roles.
Permitted action
Raise a bounded exception event with the proposed adjusted ETA and request a coordinated response.
Receipt issued
Exception raised — signed receipt records the source, the proposed adjustment and which roles are now in the loop.
Next handoff
Hands off to Terminal Yard for operational picture.