Observability

Every call to an AI provider API MUST be logged with structured metadata for cost attribution, debugging, and performance monitoring.

All significant user actions MUST be instrumented via an `AnalyticsProvider` interface (`track(event, properties)`). ...

Adopt always-on, low-overhead production profiling correlated with traces only when measured perf/cost debugging justifies the pipeline.

Propagate W3C trace context across every service hop and async boundary, and correlate logs/metrics/traces via a shared trace_id.

Every component and flow must be instrumented with structured logging using the platform's best-in-class framework:

Instrument services with RED metrics and resources with USE so signals correlate and feed SLIs/SLOs.

Define user-centric SLIs, set SLOs, derive an error budget, and alert on multi-window burn rate rather than resource thresholds.