What this interface is not

Three boundaries are worth stating plainly so an integration is scoped
correctly.

It is not the subscriber telemetry interface. Per-subscriber counters,
session records, address pools, plans, and the DHCP protocol counters live on the
controller's own API and are documented in the companion BNG Telemetry API
Theory of Operations. Reach them through the /v1/* passthrough. Deliberately,
no per-subscriber series exist in the Prometheus store — that data is served
on demand from the controller and retained briefly in the ring buffer, which is
what bounds cardinality, storage, and exposure.

It is not a push interface for telemetry. Consumers poll, or they scrape
Prometheus. QuantumTouch does not open webhooks or streams toward a monitoring
system. Audit shipping is the one outbound mechanism and it ships audit records
to explicitly configured destinations — not telemetry, and not to arbitrary
callers.

It is not the log stream. Structured service logs are written to standard
output and consumed through the operator's log pipeline. The journal endpoints in
this document provide bounded, filtered access for incident investigation; they
are not a substitute for a log shipper on a busy box.

An integration therefore has four channels available — structured operational
REST, the raw telemetry passthrough, the Prometheus scrape, and the log stream —
and should use each for what it is suited to.