Default-Setting Harm Documentation - Platform Policy Org

Objective

Observe and document platform-favouring defaults and buried settings at billion-device scale to build the regulatory file.

Summary

Monolith shapes behaviour across more than a billion devices through defaults that profit the platform and protective settings buried beyond reach — lawful by design, and the most consequential harm in the registry for it. Held at Observe: most of the harm is legal, so the lever is the regulatory and documentation file, not a counter-op. GOVERNOR's default-divergence maps already show choices set consistently against the user; the file escalates only if an unlawful, non-default harm is isolated. The Hand stays invisible.

Operational Timeline

• T-5 dGOVERNOR default-divergence map flags settings set consistently to the platform's benefit.
• T-1 dWatch cell confirms protective controls buried five-plus screens deep.
• T-0Forced-account paths for actions needing none recorded against the documentation file.
• Day 3Regulatory file advanced; no escalation criterion met under lawful default design.

Findings

• Default settings consistently configured to the platform's benefit at billion-device scale.
• Protective privacy controls buried five-plus screens deep, beyond practical reach.
• Guest and anonymous paths blocked behind mandatory account creation to capture data.

Outcome

Linked Target

Techniques Deployed