AI Fluency.

The framework

1. 01

   Write down what it can already touch.

   Open every assistant, integration and automation you switched on in the last year and list, tool by tool, what each is permitted to do with no human present. Mark every line read or write, and every write reversible or not. The list always runs longer than your memory of it, because permissions accumulate one convenient click at a time. Day 33 asked where your judgement stays in the loop, and you can't answer that without this list. You're not auditing cleverness here. You're auditing reach.

2. 02

   The narrower version almost always exists.

   There's nearly always a smaller version of what you granted: draft rather than send, propose rather than commit, staging rather than production, read rather than write, a capped spend rather than an open card. Take each line on your register, write the narrower version beside it, and move to it this week. Reversibility is the property that matters most, because an action you can undo turns an incident into an inconvenience. Convenience will argue against every one of these changes, and convenience is precisely what talked you into the wide permission in the first place.

3. 03

   A canary, a watcher, and a stopping rule written first.

   Google's engineers don't ship to everyone and watch. They ship to a canary — a small, closely observed population — with the stopping signal defined before the release goes out. Do the same with anything that acts: one team, one account, one fortnight, a named person watching a named indicator, and the authority to halt without convening anybody. The second half of that is what makes it a test rather than a soft launch. A pilot with no written stopping result will always find a reason to continue, because by the time it's running, somebody's plan depends on it.

4. 04

   Who granted this, and when does it expire?

   Every permission gets a line: what was granted, to which system, by whom, on what date, and when it runs out. Expiry is the field people leave blank and the field that does the work, because a register nobody revisits is just a list of things you once agreed to. When something goes wrong, and eventually it will, the distance between a bad hour and a bad quarter is whether you can state exactly what the system was allowed to do and who decided it could. Write the log while granting is boring. You won't write it afterwards.