Proof at the handoff — two demos

FlowSense seals what happened at a handoff the moment it happens, then moves that sealed record to whoever needs it — live. Each demo below is a pair of screens that talk to each other. The handoff between them is the thing to watch; that's the product.

Sample data. Everything runs in your browser — no server, no database.

① Driver → Outbound ops

flowsense-demo-

The dock-capture flow, tailored for the Imperial Dade design partner. A driver seals a delivery; the back office sees it land in the same instant.

Best place to start
Split-screen stage — both sides at once →
The driver app and the operations panel side by side, with a live Bridge Event Feed running between them. Press ▶ Auto-play walkthrough and it drives itself: a clean delivery, then an exception with evidence, landing in the Work Queue. Nothing to set up.

Or drive the two screens yourself, in side-by-side tabs:

Start here
Driver app →
Run a stop on route MI-214: scan the load, capture purpose-specific photos and a receipt artifact, flag a discrepancy with the receiver's reason code, then seal the delivery.
Then watch it land
Outbound — Stop Feed →
Sealed stops arrive live in the Stop Feed; anything carrying an exception routes into the Work Queue as a case with its evidence already attached.
fs_packets_v1 →The bridge: sealing on the driver writes the packet and broadcasts it; the Stop Feed is listening and updates with no refresh. Open both in side-by-side tabs and seal a stop with an exception to see it.

② Inbound receiving verification

flowsense-demo-

The receiving view carries the same Imperial Dade UI language into appointments, receipt verification, claim preparation, and the packet vault.

Inbound workflow
Receiving — verification queue →
Review appointments, open verified receipts and exceptions, assemble claim evidence, and search sealed packets from one receiving workspace.
fs_packets_v1 →The bridge: receiving listens to the same sealed packet channel as outbound operations, so driver proof can appear in the queue and packet vault without a refresh.

Because the paired screens talk to each other in the browser, keep each pair in the same browser on this site. These demos exist to show the workflow and the handoff — not the engineering underneath, which is a separate codebase.