Partner telemetry: publishers see problems before users do

Canon: kb/167_unified_telemetry_observability.md · Principles: kb/13_foundational_principles.md (Magic by default)

Product shape

Partner magic is intentionally problem-first: a problem_summary, structured suggested_fix_steps, volume and first_seen, and a fingerprint per error class / asset — not raw stacks in the default fold.

Privacy

Aggregates describe what failed; no end-user PII in publisher-facing projections. Redaction rules apply before feed materialization.

Deterministic first

Playbooks come from stable HumanError codes and registry snippets; “expand with agent” can attach async enrichment so the hot path stays fast.

Surfaces

Developer Home and per-asset health consume the same canonical events as webhooks — webhooks are depth, not the only path.

Series

• Previous: Observability profiles
• Next: Escalations & remediation