Future Defaults · No. 003
Negotiating settings
Settings pages are tiny bureaucracies: thirty-eight switches and no idea what any of them cost you. This entry replaces the wall of toggles with one good question and a negotiation about boundaries.
Preference agent
What are you trying to protect?
I want helpful memory, but I do not want the app to feel invasive.
Then I would not show you 38 toggles. I would propose a memory boundary.
What it breaks. The idea that users should manually configure every system behavior — and that a switch labeled “Improve personalization” communicates anything at all.
Why it might work. AI products create conditional, contextual preferences that are nearly impossible to expose as static toggles. A negotiation can surface the tradeoff a switch hides.
Where it fails. Automation around privacy, memory, and consent can easily overreach. A system that negotiates your boundaries can also talk you out of them.
Should settings negotiate boundaries — or is a wall of switches the more honest interface?