Skip to main content

Operational Interface

The corridor ships with a real-time operational interface built on the standardized corridor events. It serves two audiences: border officers, who monitor, interpret, and respond to pedestrian movement and identity outcomes inside the corridor, and travelers, who receive live instructions and feedback during their journey.

Two standalone applications​

The interface consists of two standalone, Docker-containerized web applications — one for officers, one for travelers. Both connect exclusively to the Hub's GraphQL API, which acts as their only source of notifications and data. No direct connection to internal source systems is needed, so the apps deploy anywhere the /graphql endpoint is reachable.

Real-time with persistent state​

Both applications display events in real time as they are published. The officer application additionally restores its state from the event store after a reload, so a browser refresh or workstation restart never loses the operational picture. See Event Storage & Retention for how that history is kept.

Display targets​

The primary display target is a standard desktop monitor (20–27″) at the officer's workstation; tablets are optionally supported. Smartphone screens are not an expected use case. The traveler-facing application targets screens positioned along or at the end of the corridor.

In this section​