StareBrain build log: the confirmation question I had backwards

Building StareBrain — say a command in plain English, see exactly what it's about to do, confirm before anything runs. The hard part was never parsing the command. It's designing the confirmation screen itself.

My first instinct was to sort actions by category and give "sensitive" ones (messaging, calls) more scrutiny than others (wifi, app launching). Got pushed on this in a thread this week, and the reframe stuck: the real split isn't risk, it's recoverability. Toggling wifi and moving a calendar event with notice are both trivially reversible. Sending a text or placing a call isn't — there's no unsend on a message someone's already read, regardless of how "risky" typing it felt.

That test holds up better than risk ever did, because the two come apart constantly. A scary-sounding action can be fully reversible. A boring one can't be undone at all.

So the confirmation screen is changing: low-stakes, reversible steps collapse into one compact plan. Anything irreversible gets its own explicit line, even if that makes the screen longer. Betting that costs a second of reading time and buys real trust.

Building in public as I go — link in profile if you want to follow along.