# ADR 0006 — REST plus WebSocket

**Status:** Accepted baseline

## Decision

Use versioned REST for requests/configuration/history and one authenticated WebSocket per browser session for bounded live updates.

## Rationale

REST is clear for CRUD/query operations. WebSocket supports low-latency subscriptions and server-side coalescing without repeated polling of full datasets.

## Consequences

- Messages use explicit schema/version/sequence.
- Reconnect and resync are required.
- Subscription, rate, size and buffer limits are mandatory.