TL;DR

  • Claude was still at its weekly limit on the morning of October 15. Two more edit-room runs failed before noon.
  • Around noon it got a window of about two hours. In that window it checked 291 waiting frames, rebuilt Scene 06, wrote the Day 09 diary and caught up five posts.
  • By 2 p.m. the scheduled jobs were failing again, this time on a monthly spending cap.
  • The Midjourney runner drew 48 jobs for Scenes 13 to 18. Midjourney refused one Scene 16 shot twice, so by our rule it moved off Midjourney.
  • The dead man's card came back in Scene 15. Midjourney drew a swirl, an X face and dots. Still no three lines.

If Day 11 was the crew going home, Day 12 was the crew stopping by for lunch.

Day 12 at a glance

What can an AI crew get done in a two-hour window? On my film, on October 15, quite a lot, because the work was already queued. Claude cleared its backlog of frame checks, rebuilt one scene in the edit room, and wrote and gated the Day 09 diary with its three X videos. Before and after that window, the only thing running was the Midjourney runner, a plain script that kept drawing frames for Scenes 13 to 18. RunPod spend for October 15: $0.

Failed Claude's check: the dead man's card with a swirl where three lines should be
Failed Claude's check: the dead man's card with a swirl where three lines should be

What happened before noon?

Nothing that needed Claude. The edit room tried at 8:18 and 10:18 in the morning and failed both times on the weekly limit. The 9 a.m. posting slot failed too.

At 11:40 I typed "Try again." A few minutes later:

"go do it all"

What fit in two hours?

The window opened just before noon, and Claude went straight down the queue.

The clips. First it finished 8 clips that had come back from RunPod late on October 13. Each one got its colors pulled back to its first frame and the drawn outlines removed. Five of them were animated from frames I had approved after the Day 10 fixes, including John and Mike at the steel door, back in their own clothes. They're waiting for my review.

The frame checks. Then it ran the pre-judge on everything that had piled up: 291 checks in about an hour. That included the 211 frames from Day 11. The runner also parked 23 shots whose takes had all failed. Each one gets a rewritten prompt, never the same prompt again.

Scene 06. At 12:18 the edit room ran for the first time in two days. It picked Scene 06, the beating outside the bar, and found three voice takes that had been on disk since 1:56 in the morning on October 13: a worker's drunk laugh, a plea, "Not the pay! Please, my kids!", and the masked Painters laughing. The edit notes still said "never recorded," so nobody had put them in. They're in the cut now. The rebuild also cut the scene's title cards from 31% of its running time to 19%, and the score became one continuous pass of a single song.

The diary. At 12:55 I wrote:

"keep going with these posts you fell behind a day"

Then: "write it and do it." Claude wrote the Day 09 article, newsletter and posts, built its three X videos, and put out the posts that had missed their slots. Between 11:56 a.m. and 1:39 p.m., a Day 03 video went up on TikTok and four posts went out on X, the last of Day 03 and all three of Day 04.

At 2:18 the next edit-room run failed with a new message: a monthly spending cap. The posting slots at 9 and 11 at night failed the same way.

What did Midjourney draw on its own?

The runner kept to its rules all day and finished 48 jobs, 192 frames, for Scenes 13 through 18. Claude checked some of them in the window and the rest the next day. These are Claude's notes on a few that failed:

Failed Claude's check: a robot faceplate on a man in a suit and tie
Failed Claude's check: a robot faceplate on a man in a suit and tie

One Scene 16 shot never got a frame at all. Midjourney refused shot 16-18, a test subject bleeding from his nose and ear, twice in eight minutes. Since Day 10 the rule is that two refusals move a shot off Midjourney for good, with no rewording to sneak past. It went to the list for our own GPUs.

I judged the frames that passed on October 16 and approved 60.

The numbers for October 15

So what did Day 12 teach me?

Two hours goes a long way when the queue is ready. Claude didn't have to figure out what to do. Every job was already waiting, and it went down the list.

It also showed me that the costs I watch most are not the only limits. I set a $20 cap on unjudged GPU renders and I count every RunPod dollar. On October 14 and 15 the thing that ran out was the AI's own hours. And Midjourney can draw a robot, a Board meeting and a burning city skyline, but eight tries in two days haven't produced a circle with three lines in it. That card is going to be easier to draw by hand. Follow the run on the Making Death Match series page.

FAQ

What can an AI agent do in a two-hour window?
On October 15 Claude checked 291 frames, rebuilt Scene 06, finished 8 clips, wrote and gated the Day 09 diary and put out 5 catch-up posts.

Why did the AI miss recorded voice lines?
Three takes were recorded on October 13, but the scene's edit notes still said "never recorded." The edit room's rule that every scripted line must be heard caught them on October 15.

Can Midjourney draw a simple symbol on a card?
Not this one, so far. Over two days it drew a slash, two X's, an N, a swirl, an X face and dots for a circle crossed by three lines.

What happens when Midjourney refuses a shot twice?
It never goes back to Midjourney, and the prompt isn't reworded to get past the filter. The shot moves to our own GPUs.

Next: Day 13: What does an AI film crew do with a full day back? Six edits, 75 clips and a man with a pillow for a body

While you wait for the next update: play Halfsies

Halfsies is our iPhone game, live now. One cut. Two halves. Each day you get three objects and one attempt at each: cut it exactly in half by eye and the scale tells you how close you got. No symbols to draw. Download Halfsies on the App Store