Back to Blog

AI

On Day One, My AI Chief of Staff Was Registered as Read-Only

By Khai Tran · · 1 min read

The day Red moved into a home of its own, every persona in our task app got a rule about what it could do without asking. Red's own rule was read-only.

Featured image for On Day One, My AI Chief of Staff Was Registered as Read-Only

Week ending April 17. Written up from the build log.

On April 16, Red moved out of a chat project and into a home of its own.

That day it got a memory it could read and write: a repository of files that holds what it knows about my businesses. One of the first files was a profile of how I write, drawn from 37,902 of my own sent messages.

In the task app we used at the time, ten personas were registered the same day, Red among them, and each got a rule about what it could do without asking. Five, including tax and legal, needed approval for anything sensitive or high-impact. Three could only draft. Two were set to read-only, and one of those two was Red.

So in that registry, the chief of staff started with the smallest permissions on the team.

Three routines were scheduled and rehearsed before the day was out: a weekday morning brief, a Saturday weekly review and a Saturday health check. All three passed. The weekly review tried to post its report as a document in Slack, the free plan blocked it, and the report came through as a thread of messages instead.

Before the day ended, I was messaging it from my phone.

The first real morning brief was set for 6:27 the next morning.