Demo hub

Five screens from the corridor walk that closed Slice 7, run live on two physical phones (an iPhone and an Android device) against the real backend on 2026-09-14.

Synthetic data only. The reference SLICE7WALK-CORRIDOR-001 names a test fixture, not a real shipment. GPS coordinates reflect where the walk was actually run, not Port Saint Croix.

Screen by screen

iPhone screen, shipment SLICE7WALK-CORRIDOR-001 in state FILED, with the commercial invoice, packing list, and bill of lading attached, and an empty custody chain.

1. Filed

The shipper's device, moments after filing. All three pre-arrival documents are attached; no custody events exist yet.

iPhone screen, shipment UNDER_REVIEW, showing a landed-cost estimate of $386.19 and a Simulated ACE submission with an entry reference, submission time, ITN, and status, plus Approve and Hold buttons.

2. Under review

The customs reviewer's device. The landed-cost estimate ($386.19: subtotal, duty, tariff, tax) is computed on-device from the pinned SAMPLE rule. The ACE submission is labeled Simulated and carries a synthetic ITN; no live filing occurred.

iPhone screen, shipment CLEARED, same packet and landed-cost estimate, with the message Approved, shipment cleared.

3. Cleared

Same device, after Approve, confirmed with the reviewer's own biometric or device passcode. The shipment state is now CLEARED.

iPhone screen, shipment RECEIVED, showing a payment milestone eligible since a given timestamp and not yet acknowledged, and an authoritative server-computed landed cost of $386.19, with an Acknowledge button.

4. Payment eligible

The broker/finance device. Once the shipment reached RECEIVED, the payment-eligibility milestone was created automatically. The landed cost shown here is computed server-side, not on-device, and is labeled authoritative. No money moves at this step; acknowledging it requires a biometric confirmation.

Android phone screen, shipment RECEIVED, showing the same three documents and a custody chain with two events: Pickup and Receipt, each with a timestamp, GPS coordinates, and a hash.

5. Custody chain

The port operator's device (a second, different phone, to prove the record is shared, not local to one device). Two custody events, Pickup and Receipt, each carrying a real GPS fix and a hash chained to the one before it.

What this walk did not cover

One operator drove both devices in this run, not two distinct people. The state machine and role gates behave identically either way, since roles are enforced server-side regardless of who is holding which phone, but a true two-person walk is still worth doing before beta.

Read the field-level detail behind these screens in the developer docs.