Back to Blog

AI

Our AI Assistant Can't Change Her Own Schedule

By Khai Tran · · 2 min read

Our AI admin assistant had stayed inside the approval rules for 46 runs. We moved her into her own space anyway, with a much smaller view of the business.

Featured image for Our AI Assistant Can't Change Her Own Schedule

Week ending August 21. Written up from the build log.

This week I had to decide how much of my business our AI admin assistant should be able to see.

I didn't want to make that call alone. My note at the time: "Before making these 3 decisions, I think I should have council and round table's take." So three of my AI specialists worked through it. Tony, who handles systems. Grant, who runs real estate operations. Harvey, who reads everything like a lawyer. Each formed a view before seeing the others'. Two rounds, three to zero, on all three questions.

Then the audit found something the roundtable hadn't been looking at. The assistant wasn't running where we thought, and she could reach far more than her job needed. In 46 logged runs, she had stayed inside the approval rules. The concern was reach: how much she could touch if a run ever went wrong.

So she moved out. She has her own login now, without admin rights. Her workspace was started from zero with none of Red's history in it, because a copy that keeps the history isn't really separate. She can't change her own schedule, which lives somewhere she can't edit. She can't mark her own work as approved. That still takes a tap from me.

One question was left open on purpose: should she know when someone in one of my businesses is also a client in another? Grant wants her to know. The council warned that's exactly how the old exposure could leak back in. That decision was left to me.