Pattern: observability-control-plane

Query-in-place monitoring across client accounts: telemetry stays client-side; Propel runs only a thin pane. Designed, not yet deployed.

The design: Amazon Managed Grafana, one workspace per customer (hard isolation, billable seats) + Uptime Kuma for status pages + cross-account read roles (ExternalId, no static keys) + OTel-first instrumentation. Full rationale, costs, and log-privacy tiers on the Observability & Logging page.

Decision: ADR-0003 · Observability Control Plane — query-in-place by default, per-customer opt-in log ingestion.

Graduates to golden-path when: first client deployment proves the workspace-per-customer model end to end.