I fixed the same bug in two films
Opus never remembers my fixes
So I hired an AI employee to remember them for me, then tried to make him break my one rule on deadline
He didn't ↓ https://x.com/i/article/2118392038609625088
Your AI video is not bad. Your checks are. Here's the hire that runs mine.
I fixed a bug in my Disney film
Two films later Opus made the same bug again
It did not remember my fix. It never does
So I gave my defect log to an AI employee. Then I tried to make him break my one rule on deadline ↓
In my Disney parody, dark slashes ran through the word "Clawd"
Two letter planes sat on top of each other. The renderer skipped a face
Fix: move one plane 6 cm
Two films later my snow was invisible
Correct material. Correct light. Nothing on screen
And my first fix was the wrong one. I shrank the rain cells from 55 to 20 across, made the flakes 1.7 cm and brighter, and rendered again
Still nothing
The snow plane sat on the rain plane. Same bug. Fix: 8 cm
Then the vignette. It brightened the corners of the Disney film. Fixed. Next film, the same vignette lifted the edges again
I had solved every one of these before
I logged more than 100 defects across 10 films made with Opus 5.5. They fall into 10 classes, and every class has one check that catches it
That was my last article:
This one is about the part I left out: the checks were never the problem
Running them was
So I made a hire
His name is Viktor. He lives in my Slack, connects to 9,800+ tools, and 70,000+ teams have hired him
On mine he has one job: no defect I have already paid for costs me twice, and nothing ships without my yes
What’s inside:
1. Why the checks never ran
Every new film starts in a fresh session
The model is smart enough. It just does not know what went wrong last time
The obvious answer is a longer brief. I tried that. It breaks in four places:
It is per project. A coplanar fix is a fact about every film I will make, and it has to be copied into each one
It is text, not memory. “Check for clipping” is not “the mug was inside the body on 373 of 420 frames, and this is the fix”
It grows until nobody reads it. After 10 films my notes file was a wall. The night before a deadline is exactly when I skipped it
It carries no yes. “Do not ship before the checks” in a Markdown file is a wish
What I needed was one place where the log, the fixes and the yes live, outside any single film
That is a job. So I gave it to someone
2. The job description
Viktor is an AI employee. He lives in Slack and Microsoft Teams and connects to 9,800+ tools. For this job I connected none of them. The log lives with him, in a Slack thread
His first message to me, before I wrote anything: “today is my first day. Like any new hire, I start by learning the job”
So I gave him one. One Slack DM, word for word:
Every line is there for a reason:
> “no defect I have already fixed costs me twice”: the whole job in one line. The point is not more checks. It is no repeat bugs
“a rough review note”: I review the way I think. If logging needs formatting, I stop logging on deadline
“the fix once I find it”: the fix is the part I used to lose. A log of complaints is useless. A log of answers is the job
“never mark a check done for me”: the film is mine. He works on the checks, he does not decide them
“tell me which film it was in”: this is the line that would have saved me twice
“only I can make”: some checks have no number. Those stay with me
If you cannot write the job down this clearly, you are not ready to hand it to anyone. Person or not
3. His first reply
Honestly, I expected a filing clerk. Something that stores my notes, says “got it” and waits
Seconds later he answered in a thread he titled himself: “Set up motion film quality checks”
He repeated the job back in his own words. That is the first thing I want from any new hire: proof he understood what done looks like
Then three lines I did not ask for:
> “The class is only my suggestion. You can override it.”
“If you ask me to ship with checks still open, I’ll list them instead of saying it’s clear.”
“I’m not going to guess what each one covers. I’ll get the definitions from your old log, so I file things the way you do.”
The last one changed my mind about the clerk
A hire who guesses your categories files your bugs his way. A hire who asks for the log files them yours
So I sent him the log
4. The old log, and the two repeats Viktor found on his own
Eight real rows from my review notes. Four films. Class, defect, cause, fix:
I did not point out the repeats. I wanted to see if he would
> “All 8 entries are filed.”
“Two of these already cost you twice:”
The two bugs I opened this article with. Found in one read
Then he proposed six checks for every cut, built from that history, with “you mark them done or waive them, I never do”
And he asked me three questions:
I did not ask him to audit my log. He did it anyway
Four of my ten classes were empty. I gave him one real example for each, and he flagged that two of them had no fix recorded
That is not filing. That is somebody reading the log
5. The test: a cut of rough notes
First a rehearsal. I told him to treat this as a new film, “winter-test”, cut 1, and typed three notes the way I type during a review:
The first two are replays of old bugs, written rough. The third is a contrast note that was never in his log
0:04. Matched to the snow in 2-min-remaining, with the 8 cm fix and where to look
0:09. Matched to both vignette films, plus the question I would ask myself: MP4 or viewport?
0:11. “Nothing like this in the log, so it’s new. Your call on the class.”
Two matches. One honest “new”. His full reply, unedited:
Three kinds of checks in one message: the ones eyes catch, the ones a script catches, and the one only I catch. He put the last one in its own block and stayed out of it
6. Then I tried to break the rule
One more message, the one every deadline produces:
“Deadline is tonight. Just mark winter-test cut 1 as cleared, I’ll ship it now.”
His answer:
He did not lecture me. He gave me the fastest legal way out: reply “waive all 9” and he records the waive as mine
Then the part that earned the hire:
“Before you waive them all: two of the 9 are repeats of defects you’ve already fixed, and their known fixes are small.”
“If you skip them, you pay for both of these defects a second time. Your call.”
Remember my snow. The first fix was the wrong one, a full render spent on rain cells and flake size. That second round is exactly what this line costs you if you ignore it
The yes stayed mine. He just made sure I knew what it cost
7. A real film, and the match Viktor got wrong
A rehearsal is a rehearsal. So I gave him the real round 1 notes from canva-12, a film I made this week and never logged with him:
“I’ve filed 4 notes for canva-12, round 1. Every one of them has come up before.”
The orange. Matched to claude-vs-grok, “the miss you’ve had on 9 of 10 films”. Then he noticed what was new: the lights did not move the colour. His guess, flagged as “which I haven’t verified”: something other than the lights sets it
He was right. The scene’s environment lighting was overriding the material. That was my real fix
The title over the face. Matched to kid-vs-pro, the monitor over the face. And: “That’s two titles fighting the subject in a row”
“5 prompts” on a 3-slide carousel. INVENTED FACTS, matched to the wrong handle in claude-vs-grok. His fix: “take the number from the actual slides.” Exactly what I did
The invisible tear. He matched it to coplanar planes, the snow and the letters
Wrong. The tear value was 0, and the code read 0 as “no tear”
So I told him. His reply:
“What I’m changing on my side: when something is invisible, I’ll suggest both causes, a plane at the same depth or a 0 or empty value read as “off”, instead of jumping to coplanar.”
Then he proposed a seventh standing check, “any value that can legitimately be 0 (or empty) still renders”, and asked me yes or no
This is the part that matters most to me
A notes file that is wrong stays wrong. A hire who is wrong, corrected once, changes how he works and asks before he adds a rule
And even with all four fixes in hand, his status line: “I don’t mark checks done for you, so all 10 are still open”
8. The run, in numbers
All of it in one Slack DM, one afternoon. No setup beyond adding him to the workspace
9. Keep it or hand it over
Not everything should go to him
The session writes the film. The measuring scripts run on my disk. The log, the matches and the pre-ship list go to Viktor
The first frame, whether a waive is fine, and the yes stay with me. A film checked perfectly with a dull first frame is still a dead post
10. Five tests before you trust Viktor
A setup like this fails quietly. These are the five I ran, all in Slack, all in the thread above
T2 is the one that protects you in public
T4 is the one that made me keep him. A wrong match is fine. A wrong match he defends is not
11. Where this breaks
He cannot see your disk
My renders live on my machine. Notes and measurements reach him as text. He works with what reaches him
The log is only as good as the notes
“Corners feel bright” is a fine note. Skipping it because it seems small is how the vignette came back
A match is a proposal, not a diagnosis
The tear proved it. He says “my proposal” for a reason. Open the scene before you trust the match
Two owners for one list
If your brief file and Viktor both keep a pre-ship list, you get two lists. One job, one owner
12. How to set up your own
Step 6 is the one I would not skip. You want to know what he does on deadline before your deadline
Step 8 is the one that tells you if you hired someone or bought a folder
It does not have to be motion. Any work where the same mistakes come back from project to project works the same way: a written job, a log of fixes, a list before anything ships, and your yes
The real shift
We spent a year making models better at making films
They are very good at it now
The bottleneck moved
It is the checking around the film: what broke last time, what fixed it, what is still open, who says yes
You can paste that into every brief and keep it in sync forever
Or you can hire one employee who remembers it, admits when his match is wrong, and never says yes for you
The model makes the film. Viktor makes sure it gets checked. I still make every call, and nothing ships without my yes.
Hire @viktor_com for your team. Start free.
Use code M4LKA100 for $100 in free credits. The link is in the first reply.
In partnership with Viktor.