Yesterday’s question was what the AI in my build is allowed to do on its own. Here’s the answer I settled on, in one line:
AI assists. Verified rules enforce. Authorized people decide.
What that means in practice:
- AI assists. It can interpret, organize, suggest, and flag. That’s its whole job.
- Rules enforce. The system’s own permission checks decide what’s allowed, no matter what the AI suggests and no matter what the screen shows. Hiding a button isn’t security. A button that’s just out of sight can still be reached another way, so the system itself has to check who’s allowed, every time.
- People decide. Anything consequential, like granting access, deleting something, or sharing it outside the company, needs an authorized person to confirm it.
Two more things I added:
- When the AI is unsure or can’t be reached, it says so and hands the decision to a person. It doesn’t guess, and it doesn’t quietly do the risky thing anyway.
- A written rule isn’t proof. I only count a safeguard as real once I’ve tested it. Right now I’m still testing, so this is the rule I’m building to, not a claim that everything is finished. I’ve also had a second AI review the first one’s work on one of my safety checks. It found problems, and I’m fixing them. That’s a check, not a substitute for expertise.
If you’re building something with AI in it, you can borrow this in about ten minutes: write your own one-line version, list what your AI can suggest versus do, and pick the one action in your app you’d least want a wrong guess to trigger. Start there.
Next week: the app that wouldn’t guess, and why I don’t want mine quietly making things up.
This is general information, not legal advice.

Leave a Reply