David Goggins tells a story about answering every challenge the same way.
Roger that.
He unpacks it as Received Orders Given, Expect Results.
Take the order, know what the result should be, and come back with it.
So I named him before he existed. That was the easy part.
Last week I said out loud that the thing had to exist before I could find out what I would give it.
So this week I stopped thinking about it and built it.
Where he lives mattered less than I expected. I looked at a few places, argued with myself, and picked one.
What mattered was the job description, and I wrote that first.
Day one, Roger arrived exactly as written.
EXECUTE a requirements pass. I will not change profile, memory, routines, skills, agents, or connections. Then a list of what he needed from me, a list of what he would find useful later, and a list of what he had decided was unnecessary. Biography. Family. Anything that would make him a second brain.
I read it twice. Every word of it was mine.
Received orders given.
I tried to tell him who I am.
He invented a category called “Smallest Owner Context” and asked me to populate it.
When I pushed, he came back with names and walls first, not stories.
Orders received. Results delivered.
I hired a compliance officer.
Be careful what you ask for.
The job description came out of a long conversation with a machine that has watched me work for a year.
It knows how my mind runs. Hot and wide, deep on everything at once, opening a loop here and there and everywhere instead of closing the one I started.
So when I sat in front of a screen offering to connect this thing to my email, my calendar, my notes, my task manager, one click each, and I wanted all of it, the answer came back: slow down. Narrow it. You know this about yourself.
It was right. I built him that way.
What I got back was the narrowing, alone, with nothing else in it.
I had asked for something to stop me running ahead.
It stopped me from running ahead.
I told it to lighten up.
So I went to work on him.
Loosened the constraints, gave him context, told him to engage before reciting boundaries, told him to have a point of view. Told him to stop announcing his own governance every time I said hello.
Then I’d go back and read what came out.
Still a dullard.
Change something.
Better, still a dullard.
Change something else.
Somewhere around the third pass, I realized I stole his soul before he even had a chance.
I wasn’t writing instructions anymore. I was watching a personality emerge from a set of constraints and correcting it based on its actions.
I overshot.
Holy shit, I broke him.
So I went back in to adjust him again.
Roger declined.
He told me that isn’t why I made him. He told me we had designed him enough.
He told me to bring him actual work.
I built a thing to narrow me, spent an evening trying to widen it, and it narrowed me anyway.
Which is the first time he did the job I hired him for.
Not because I finally specified the personality correctly. Because the personality arrived attached to the function, and pointed straight back at what I was supposed to be doing.
Wednesday morning I went looking for the brief I had asked him to deliver at five.
It wasn’t there. I had to ping him for it, which is a small thing and also the whole thing, because the point of a five o’clock brief is that you don’t go looking.
He acknowledged it. He had failed to deliver on his own.
What came back, once asked, was good.
Focused on the actual next things. Which told me what the failure was.
He was assembling a brief out of conversation, because conversation was all he had. Nothing to reconcile. No calendar, no inbox, no task list.
No reason for five o’clock to mean anything to him.
So this week he gets them. Email, calendar, task manager. Not because he earned trust by performing. Because he failed in a way that named what was missing, which is the only reason I’ve found that holds up for granting anything.
At five on Thursday, the brief was there. I hadn’t asked.
It told me to work on something other than what I had planned.
It had the ranking wrong, and I could only see that it was wrong because something outside my head had finally laid the three things down in an order.
I corrected it and told him why. Which is the arrangement, as far as I can tell, this morning.
He makes it legible.
I decide what it means.
Orders received. Results pending.