git_admin/obsidian-vault
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[2026-09-17] eagle: work/projects/cpm-m3-telemetry-privacy-triage.md

Browse Source
This commit is contained in:
Alexey Martemyanov
2026-09-17 16:23:54 +06:00
parent 60a25605e3
commit 82025e8d4a
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
work/projects/cpm-m3-telemetry-privacy-triage.md
+5 -5
View File
@@ -1,8 +1,8 @@
# TD: Pixel Definition: CPM M3 Telemetry (macOS/iOS)
# TD: Pixel Definition: CPM Failure Diagnostics (macOS/iOS)
**Author:** Alex M
**Reviewer:** TBD
**Stakeholders:** Michal, Konrad, Russell (from the first CPM Tech Design; confirm for M3)
**Stakeholders:** Michal, Konrad, Russell (from the first CPM Tech Design; reviewers for this proposal to be confirmed)
**Project:** [CPM: root-cause the stuck embedded extension messaging (macOS/iOS)](https://app.asana.com/1/137249556945/task/1216761517055116)
**Previous Tech Design:** [CPM breakage pixels](https://app.asana.com/1/137249556945/task/1218005985662983)
@@ -10,13 +10,13 @@
The first CPM pixels detect initialization failure, a stuck messaging episode and recovery. They do not explain whether a failure coincides with background-process termination, a context-load error or incorrect tab wiring.
Forced background-process termination can reproduce a persistent CPM outage. M3 adds native-side diagnostics to investigate whether the same failure occurs in production on iOS and macOS, without relying on the extension's messaging channel.
Terminating the extension's background process can leave CPM unable to respond, even after page reloads or opening new tabs. To investigate these failures in production, the iOS and macOS apps will attach process, extension and tab state to the existing failure pixels. This reporting does not depend on the extension responding.
## Problem Statement
Distinguish background-process/context failures from tab-local problems and identify failed extension reload operations. Collect the diagnostic state alongside existing failures, without page content, URLs or persistent identifiers.
M3 provides evidence for the production-validation milestone; it does not implement graveyard mitigation or an A/B experiment.
This proposal covers diagnostic collection only; it does not change recovery behavior or introduce an experiment.
## Recommended Approach
@@ -96,7 +96,7 @@ No intended page-behavior changes. However, the investigation recorded a changed
**Experimentation**
None in M3. Graveyard mitigation and A/B testing remain separate milestones.
None. Recovery changes and experiments are outside this proposal.
**Operational**