IBM Vacation · ARCADIA HORIZON — Security Control Plane

Security control plane · decks 3–11

ENGINE —

AI —

--:--:-- UTC

POS— HDG · SOG— GNSS— SEA— WIND— CURRENT · DRIFT— AIR · VIS— OBJECT— MOB— SIGNALS—

Pos

Motion

Camera

Guest app · push

Camera status

Occupancy

Man overboard

Tracked guests

Selected camera

Click a camera light on the ship

AI analysis ●

Waiting for first analysis…

Server Base URL API key Model Analyse every s

A custom endpoint is called straight from the browser: it has to allow cross-origin requests, and a key entered here is stored in this browser.

Events · outbound

Webhook URL Identity in payloads

Every delivered event is POSTed as JSON (x-arcadia-event and x-arcadia-seq headers). No answer or a non-2xx is retried with back-off, then counted failed. On this dev server /hook accepts and lists them; for any other origin run npm run sink. Payloads never carry a name, cabin or biometric attribute — the opaque track id is the only person reference, and "none" removes it.

Store-and-forward

While the ship–shore link is down, events queue on board (persisted — a reload keeps them) and replay in order when it returns, tagged delivery.replayed with the seconds they waited. With ambient events on, the satellite link also drops by itself now and then.

Machine-readable spec

openapi.json — OpenAPI 3.1: the shipboard REST surface (detections, alerts, events, config, admin) and one webhook schema per event type, generated from the same catalogue this panel shows. Open the shoreside subscriber in another tab to watch delivery, queueing and replay from the receiving end.

Scorecard · ground truth

Per class · every frame scored against the simulation truth

Latency · from the event to each step of the response

Agreement

Method

Event log