1 · The Agreement Opens

March 2026. A Brazilian coffee exporter — Exporter Ltda — agrees to ship 500 bags of green arabica coffee to Buyer AG in Rotterdam. Two 40-foot high-cube containers, loaded at Santos, sailing on MSC AURORA voyage 2612E. Commercial terms: FOB Santos, USD 180,000, payment net 30 from Bill of Lading date.

This is the first agreement in the coordination field. It generates four obligations — four open loops — that must close for the shipment to be complete.

Coffee Export Contract — Buyer AG normal
commercial · active · 4 loops (3 resolved, 1 open)
All loops resolved: BL original received, customs clearance confirmed, vessel arrived Rotterdam, invoice paid
Cargo Insurance Policy — Porto Seguro internal
insurance · active · 1 loops (0 resolved, 1 open)
Coverage valid while: averbação confirmed per shipment, approved route followed, risk manager active, premiums current

Before departure, the exporter's insurance broker confirms coverage. Policy AP-2026-CARGO-0819 with Porto Seguro, all-risks, 10% deductible. Averbação AVB-2026-04821 activates coverage for this specific shipment.

2 · Operational Movement and Divergence

The booking confirms quickly. MSC allocates two slots on voyage 2612E, ETD April 15. The customs clearance follows — DU-E registered through Siscomex, cleared April 20.

Then the first divergence appears.

timestamp_anomaly

MSC AURORA does not sail on April 15. Port congestion at Santos delays departure by seven days. The vessel sails April 22. BL issued April 24.

Three of four export loops resolve. One remains: payment.

resolved Booking confirmation
operational
Resolved: 2026-03-30
resolved BL original received
documentary
Resolved: 2026-04-24
resolved Customs clearance Santos
documentary
Resolved: 2026-04-20
in progress Invoice payment
financial
cost_mismatchpayment_delay

3 · Financial Pressure and the Payment Gap

On April 24 — BL date — Exporter Ltda issues commercial invoice INV-2026-0471. USD 180,000, FOB Santos, net 30. Due date: May 24, 2026.

May 24 passes. No payment. On June 5 — twelve days late — payment arrives. But it is wrong.

Invoice issuedUSD 180,000
Payment receivedUSD 175,000
Shortfall (buyer withholding)USD 5,000
Payment delay12 days past due
Despachante feeBRL 4,200
cost_mismatch

Invoice: $180K. Received: $175K. Buyer claims a discount for late arrival. Contract includes no such clause.

payment_delay

Due: May 24. Received: June 5. 12 days past net-30 terms.

The invoice payment loop does not close. Payment was received, but it does not match the closure specification: full payment of USD 180,000.

4 · Insurance, Risk, and the Claim

On May 3, somewhere in the mid-Atlantic at approximately 28°N 38°W, the reefer unit on container MSCU-7234810 loses power. Internal temperature rises from −18°C to +8°C over 14 hours before power is restored.

Reefer Monitoring Trace

ContainerMSCU-7234810
Power loss14.42h
Temp set-18°C
Temp peak8°C
Position28.1°N, 38.4°W
LocationMid-Atlantic
Schema-validated evidence artifact

On May 10, the vessel arrives Rotterdam. May 11: 30% of coffee bags show moisture damage. Estimated loss: USD 54,000.

A claim is filed. The insurer partially approves — then a dispute begins.

ClaimedUSD 54,000
Approved (100 bags)USD 36,000
Denied (50 bags)USD 18,000
Deductible (10%)USD 3,600
Net indemnity offeredUSD 32,400

Denial reason: Insurer alleges pre-existing moisture from origin, not reefer fault

context_conflict

Expected: 500 bags intact. Observed: 150 bags damaged. Reefer malfunction suspected.

evidence_quality_insufficient

Insurer requests 3 additional documents before final decision.

5 · What This Proves

2Agreements
5Loops
19Timeline events
6Divergences
19Evidence refs
7Providers

Unrecovered financial exposure

Buyer withholdingUSD 5,000
Insurance deniedUSD 18,000
Insurance deductibleUSD 3,600
Despachante feeBRL 4,200
Total unrecovered~USD 26,600 + BRL 4,200

Every event — from booking confirmation to partial insurance denial — was captured using the same set of primitives: agreements, loops, entries, evidence references, and divergence flags. No special-purpose tables were needed for financial tracking, insurance claims, or reefer monitoring.

All data on this page is synthetic but structurally validated against the hermes schema on live PostgreSQL 16. Every data point traces to a fixture row in the project repository.