Limited-Visibility Deployments — Telemetry Agents Many high-risk systems are deployed by third-party deployers who control the production environment. The provider may have limited or no direct access to inference logs, operator behaviour data, or real-world outcomes. Telemetry agents bridge this visibility gap. A lightweight monitoring component (OpenTelemetry Collector sidecar or Fluent Bit forwarder) runs in the deployer’s environment, collects inference metadata (input distributions, output distributions, latency, error rates), and transmits it to the provider’s PMM infrastructure. The Technical SME designs the telemetry to minimise transmitted data: distributional summaries and aggregate metrics rather than raw inference data, respecting the deployer’s data sovereignty. The telemetry schema, transmission frequency, and data handling terms are documented by the Legal and Regulatory Advisor in the deployer agreement. Telemetry agent deployment is a contractual obligation, not a request. The deployment contract includes escalation provisions for telemetry pipeline failures and, in extreme cases, the provider’s right to suspend service until monitoring is restored. Key outputs

• OpenTelemetry Collector or Fluent Bit telemetry agents
• Distributional summaries, not raw inference data
• Contractual obligation with escalation for pipeline failures
• Module 12 AISDP documentation