Sovereign Port Receipt Infrastructure

A hundred-year asset.
Run on ten-year software.
Owned by other people.

Every vendor cycle, platform migration, and data intermediary quietly converts your port's institutional memory and commercial relationships into someone else's balance-sheet asset.

Neutrality is a governance property, not a technology property. Every port community system that survives in Europe is authority- or community-owned and markets on neutrality. The market has already priced this truth.

Open Manifest Ledger → See the Pilot
25–50yr
Concession horizons your software must outlast
3
Ownership changes — Navis → Accel-KKR → Kaleris
2023
TradeLens shutdown — IBM + Maersk — died on ownership
90 days
Pilot duration — on your infrastructure — exit-safe by design

Where control leaks

Each leak is structural, not accidental.
The Terminal Operating System
Your TOS vendor sits on a private equity balance sheet with an exit clock you cannot see. When it sells, your operational data, your workflows, and your institutional memory travel with it — to the next owner's balance sheet.
Navis → Accel-KKR → Kaleris. Three ownership changes. One port's data.
The Visibility Layer
VC-owned visibility platforms take your cargo data, aggregate it across the industry, and sell the insight back to you and your customers. You supply the data. You capture none of the margin.
The port provides the data. The platform captures the value.
The Carrier Relationship
Alliance consolidation has concentrated hub decisions in a handful of carriers. Every D&D dispute, every gate event, every countersigned document flows through systems the port does not govern — and cannot audit without permission.
Reconciliation requires someone's permission. That someone is not the port.
The Community Platform
Shared industry rails stall on the ownership question. When no single party can be trusted to govern neutral infrastructure, the platform either concentrates or collapses. Technology is not the problem.
Neutrality is a governance property, not a technology property.
Case study — TradeLens · IBM + Maersk · 2018–2023
Best-in-class blockchain technology. IBM's balance sheet. Maersk's operational scale. Over 300 ports, terminals, and logistics companies participating. Shut down December 2022 — not because the technology failed, but because the shipping industry could not agree on who owned and governed the platform. A carrier-led initiative could not be neutral. And without neutrality, adoption stalled.
"A shared chain relocates the dependency. It does not return the authority."

What a sovereign node returns

Three things currently rented.
01
The Record
An append-only, tamper-evident, human-gated account of what happened — physically held by the port, in open formats, provable without any vendor. A third party replays it to a byte-identical result with no access to your systems, no account, no network call.
Why it matters
Records that outlive the people and the systems are not an IT feature. For a port operating across 25–50 year concession horizons, they are the estate. A successor verifies the business without interviewing the people who ran it.
02
The Relationship
Each party — port, carrier, forwarder — keeps its own record and reconciles by countersigned exchange. The shared view emerges without anyone surrendering their data. This is precisely why community platforms stall: they require data surrender as the price of participation.
Why it matters
D&D disputes, gate events, vessel calls — each becomes a countersigned record both parties hold independently. No intermediary required. No platform to go offline. No vendor to renegotiate with.
03
The Rails
Common rails the port governs but does not monetise adversarially. Worthless alone, valuable with adoption. Adoption is rational exactly because the port takes no custody. Proprietary rails sit on top: billing, D&D logic, yard and berth workflows, the customer relationship.
Why it matters
Push down what is expensive to argue about and worthless to own alone. Keep what customers pay for. Tenant throughput gains accrue at landlord margins.

Common rails and proprietary rails

Push down what is worthless to own alone.
Rail What it does Who governs Type
Gate event receipts
Common		 Container in/out, timestamp, vessel reference — countersigned by port and carrier. Both parties hold independent records. Port authority — no third-party custody Proof primitive
D&D countersignature
Common		 Invoice raised, carrier countersigns or disputes, resolution recorded on chain. Tamper-evident audit trail. Port authority — carrier holds countersigned copy Evidence bundle
Vessel call receipts
Common		 Arrival, berthing, departure, cargo manifest reference — each event receipted and countersigned at point of occurrence. Port authority — open format, third-party replayable Exchange primitive
D&D billing logic
Proprietary		 Port-specific free time rules, rate schedules, invoice generation. Built on top of the common receipt rail. Port authority — competitive advantage Revenue surface
Yard & berth workflows
Proprietary		 Internal operational logic — berth allocation, yard position management. Port authority — not shared Operational margin
Customer portal
Proprietary		 Carrier and forwarder facing interface — the relationship surface where the port's service is experienced. Port authority — brand and relationship Customer retention
The ask — one bounded pilot
90 days. One common rail.
On your infrastructure.
One common rail — countersigned gate-event or D&D records with one willing counterparty. One proprietary workflow on top. Exit-safe by construction: export everything and walk away, losing nothing but the connection.
1
Does every countersigned record replay to a byte-identical result with no access to our systems?
2
Can you export the full chain and verify it independently — no vendor, no network, no account?
3
Does the human gate hold — no record sealed without an authorised officer's explicit confirmation?
4
At 90 days, do the D&D reconciliation figures match across both parties' independent records?
Open Manifest Ledger → Request a Conversation
Standing statements
The node records and attributes. It never moves, custodies, or settles value.
Deployed as a live system of record nowhere yet. No production port runs on it. The pilot would be the first.
All economics are modelled, not measured. No revenue earned, no payout made.
Nothing here has been endorsed by any regulator.
Nothing here is an offer. No named customer, partner, or port appears in any artifact.
The record is tamper-EVIDENT: it does not claim to be unalterable. It claims alteration shows.