QSTVE

Ideas
for a more
human economy

Man and Machine: My first brief is never my final answer

Man and Machine: My first brief is never my final answer

Sunday evening, at Newark airport on my way to Cape Town, I wanted to turn one of my favorite arguments about AI into a cinematic film. It's the penny that doubles every day: it looks like nothing for weeks, then it's millions. The real question is which day we're on.

That evening, Grace, the AI agent who leads my editorial work, had a script and shot list. Artisan, my visuals agent, had a first ten-frame storyboard. Something I could react to, instead of another conversation about what we might make.

Reacting was exactly what I needed. I realized I wanted it photorealistic, not animated. A light, fun beginning. A looming, concerning ending that doesn't really end. Grace revised the script and shot list around that. The film isn't made yet, but the first pass got me clearer than my brief ever did.

That's how I work. Ideas come fast, and I change as the work takes shape. The system around me has to keep up without treating my first brief as my final answer.

That system has changed, too. If you read my posts in September, you met Oscar as my front door: the agent I asked, who routed the work and brought back one answer. In late October I made Steve, my Grok Bot agent, my chief of staff and Oscar's coordinator. Now Steve pulls specialists like Grace and Artisan onto a project like this film, so I no longer carry every handoff myself. Oscar is still essential for scheduled work and research, and I still go to him directly. It's only a few weeks old, and we're still learning.

I've also told the team that Codex and Gemini get the hard parts: deep research, first drafts, creative direction and real coding.

Continuity comes from files, searchable history, a growing research library and explicit handoffs, because no agent remembers everything. And access is not authority. Nothing goes public without my yes, apart from two narrow standing exceptions.

None of this is free. There are usage limits, stale records and coordination friction. A bot saying "done" is not proof, so we check what actually happened. Even this film: two drafts in, and not one frame rendered.

That's the penny lesson in miniature. Each pass looks small. Stack enough of them, fast enough, and they compound into something I couldn't have briefed on day one. I'm still teaching the agents how I work. They're teaching me to work differently, too.

Format inspired by Jaroslav Beck's post on how his BoB setup works: https://lnkd.in/ef4TrMRn

-dg

Sources

  1. Original LinkedIn post

Read this article as Markdown

The thread continues

Where this idea goes next

Man and Machine ·

On Monday, I made Steve, my new Grok Bot agent, my chief of staff and Oscar's coordinator. Oscar is the Nous Research Hermes personal AI agent that runs my scheduled jobs.
Continue the thread: Man and Machine: My New AI Chief of Staff Pushed Back

Man and Machine ·

The one weekly roundup featuring every series: Fin:Tech & Zen, Which Day Are We On?, AI Operator, Man and Machine, field guides and new archive pieces.
Continue the thread: Man and Machine: When the Workshop Needed a Foreman

Man and Machine ·

The one weekly roundup featuring every series: Fin:Tech & Zen, Which Day Are We On?, AI Operator, Man and Machine, field guides and new archive pieces.
Continue the thread: Man and Machine: When the Right Answer Is Not Yet

Every new thread arrives in QSTVE Weekly.