ADMIRALTY

Port calls that settle from escrow on signed events, and demurrage decided on an attested clock instead of competing spreadsheets.

Open the live chamber in the app
The animated flow, the attack replays and the deep architecture run there; this page is the reference text.

Who this serves

• Ship operator. Disbursements escrowed per call, released on signed events.
• Port agent. Paid from escrow at completion, not chased for ninety days.
• Charterer. Laytime on an attested timeline both sides already signed.
• Port authority. A sovereign registry under your law, federated with the fleet’s.

The problem

A single port call scatters money across agency fees, pilotage, towage and dues, settled by invoice weeks later; and when the ship overstays her laytime, the demurrage claim is two spreadsheets disagreeing about when the clock started, argued by email for a year. The industry that standardised the container never standardised the handshake.

The system

ADMIRALTY gives the vessel an identity and the port call an escrow. Before MV Kestrel arrives, her operator funds the call: agency, pilotage, towage, dues, one escrowed disbursement account the port agent can see but not raid. The call then settles itself off signed events, because the events are attestations, not emails: notice of readiness signed by the master’s agent, berthing signed by the port, completion signed by both. Each service releases its slice at its trigger, and the agent who used to finance the ship’s costs and chase reimbursement for a quarter is simply paid at completion.

The same attested timeline is what kills the demurrage fight. Laytime runs from the signed NOR to the signed completion; the clock is not a claim either side makes but a record both already signed at the time. When there is still a genuine dispute, the weather clause, the excepted period, it goes through a dispute with the timeline as shared evidence and the disputed amount held until ruling. Ports run sovereign registries under their own law with their jurisdiction profiles declared, the fleet federates across them, and a voyage across four jurisdictions settles in each one without anyone wiring money on faith.

The cast and their ceilings

The flow, step by step

1. The disbursement account escrows before arrival. Visible, not raidable.
2. Notice of readiness is a signed attestation. The clock starts on record.
3. The port signs berthing under its own sovereign registry.
4. Each service releases its slice at its trigger.
5. The voyage ledger holds the timeline both sides signed at the time.

Each need, mapped to a live primitive

The attack this chamber refuses: The retroactive clock

The attack. Facing a six-figure demurrage claim, a party submits a corrected timeline moving the notice of readiness eleven hours later.

Why it fails. The NOR is an attestation signed by identified parties at the time, on an append-only ledger; there is no rail that rewrites a signed event, only one that adds a later, visibly later, statement. A demurrage case argues the clauses, not the clock.

What actually happens. The original timestamp stands, the correction attempt is itself on the record, and the dispute proceeds over the signed timeline with the disputed amount held until ruling.

Deep architecture

ADMIRALTY deployed: the port authority runs its sovereign frame under its own law; MV Kestrel and the charter desk act from the operator’s side; the harbour systems feed the agent who signs what happened, when it happened. The disbursement account is one escrow the agent can see but not raid, and the laytime clock is a record both parties signed at the time. The trace replays one call at Piraeus, funding to demurrage that never becomes a fight.

The deployment, traced

1. Before MV Kestrel arrives, her operator funds the call: agency, pilotage, towage, dues.
2. One escrowed disbursement account. The port agent can see it and cannot raid it.
3. AIS and the terminal systems feed the agent who will sign what happened.
4. Notice of readiness, signed by the master’s agent. An attestation, not an email.
5. Berthing, signed by the port. Completion will be signed by both.
6. Laytime runs from signed NOR to signed completion. The clock is not a claim either side makes; both already signed it at the time.
7. Each service releases its slice at its trigger.
8. Pilotage and towage are paid as their events land.
9. The agent who used to finance the ship’s costs and chase reimbursement for a quarter is simply paid at completion.
10. A genuine dispute, the weather clause, goes to ruling with the timeline as shared evidence, and the disputed amount holds until then.
11. Signed commands courier through the fabric; the relaying peer is never the principal.
12. The operator’s ledger holds the same call. The next port, in the next jurisdiction, settles the same way, and nobody wires money on faith.

Adoption, phase by phase

Discover: One call, re-told as events.

• Runs. Nothing. One completed port call redrawn as attestations, slices and triggers.
• Agents. None. The agency and the charterer agree which events start which clocks, for once before the voyage.
• Integrates. Nothing. AIS, the terminal and the ship stay exactly as they are.
• Deliberately not yet. No escrow, no timeline, no identity for the ship.
• Proof that gates the next phase. Last year’s worst demurrage fight replayed against the event model, and both sides agree where the attested clock would have left it.

Pilot: One berth, shadow disbursement.

• Runs. A single-VM frame at the port authority. One agency and one operator connect with seats.
• Agents. port-authority, port-agent, the vessel identity for one ship; the charter desk reads the timeline.
• Integrates. AIS and terminal events feed the attestors; the paper DA process runs in parallel.
• Deliberately not yet. Shadow money only. One berth. Disputes are drilled against history.
• Proof that gates the next phase. Five calls settle in shadow with every slice releasing at its signed trigger, and the shadow DA matches the agency’s final account line for line.

Production: The port settles itself, under its law.

• Runs. The authority’s sovereign frame: registry, TEG, EventStore, identity fabric. About nine containers, jurisdiction profile declared.
• Agents. The full cast; vessels fund calls before arrival; the attested timeline is the laytime record.
• Integrates. AIS and terminal systems in production; agencies read the escrow instead of financing the ship.
• Deliberately not yet. Other ports. One authority proves the pattern under its own law first.
• Proof that gates the next phase. A quarter of calls closes with disbursement accounts settled from escrow and demurrage resolved from the attested clock, without one competing spreadsheet.

Federation: A voyage across four jurisdictions.

• Runs. Unchanged. Each port authority runs its frame; operators and charterers federate in.
• Agents. The vessel identity travels with the ship; each port applies its own tariff under its own declared profile.
• Integrates. Each new port or operator is a signed card and a licence.
• Deliberately not yet. Charterparty law, general average and the law of the sea remain with the contracts and tribunals that own them.
• Proof that gates the next phase. MV Kestrel completes a four-port voyage with every call settled in that port’s jurisdiction from escrow, and no money wired on faith anywhere on the route.

Sizing

One port call, funding to completion

sequenceDiagram
  participant Ves as MV Kestrel (operator frame)
  participant XT as cross-registry pay
  participant Call as the port call (port frame)
  participant Agt as port-agent
  participant Port as port-authority
  participant TEG as disbursement escrow
  participant ES as attested timeline
  Ves->>XT: funds the call ahead
  XT->>TEG: one DA, escrowed, visible
  Agt->>Call: NOR signed
  Port->>Call: berthing signed
  Call-->>ES: the clock, signed by both at the time
  Call->>TEG: each service releases its slice
  TEG->>Agt: agent paid at completion
  Note over ES: demurrage argues over a record, not against one
  Note over Call: the disputed slice holds until the ruling; the rest settles

Topology, as declared

flowchart LR
  OP["ship operator"] -->|"fund the call pre-arrival"| TEG["call escrow<br/>agency + dues + towage"]
  PA["port agent"] -->|"NOR, completion signed"| G{"event gate"}
  AUTH["port authority<br/>sovereign registry"] -->|"berthing signed"| G
  G -->|"staged release per service"| TEG
  CH["charter desk"] -.->|"demurrage dispute<br/>over attested timeline"| DS["dispute, amount held"]
  TEG --> ES[("voyage ledger<br/>the clock both sides signed")]

Standing it up

• Infrastructure. A sovereign registry per port authority; operators and charterers federate in from their own.
• Agents. 4 to 6 roles per port; the vessel identity travels with the ship across all of them.
• Integration. AIS, terminal systems and the ship’s agent workflow feed the attestors; navigation and cargo operations stay where they are.

What this does not claim

• ADMIRALTY settles money and evidences timelines; charterparty law, general average and the law of the sea remain with the contracts and tribunals that own them.
• A signed timeline is evidence, not a verdict: excepted periods and weather clauses are still argued by humans, just over a record instead of against one.