Week 1 Dailies: Rig Check

The week's first dailies — whether the rig runs at all, twice.

24 February 2027

• Monday lecture: The Rig
• Wednesday Dailies: Rig Check

Bring both clips, their graphs or request logs, and your timing notes — not a screenshot, since Dailies runs from files that can be rerun, not from what you remember happening. Each rig gets projected cold: if it doesn’t run in front of the room, that’s the result, not a technical difficulty to explain away afterward. Notes go on VRAM used or credits spent, render time for both clips, and whether the one changed parameter actually explains the difference between them. A rig that works but wasn’t saved as a reusable graph or log doesn’t pass, and neither does one running a checkpoint whose licence nobody in the room can name.

What gets screened#

The rig itself, not the picture it made. Two clips play, but what the room reads is the three things standing behind them: what the run cost, what licence the checkpoint carries, and whether the record is the kind another person can run.

The rungs, in the order they screen:

• the run — it executed in front of the room, twice, on the numbers you logged
• the licence — someone can name it out loud, off the model card
• the record — hand it over and watch a stranger rerun the clip from it alone

The failure here is not an ugly shot. It is a rig that runs beautifully and cannot be handed to anybody: no cost logged, a checkpoint nobody can name terms for, a record that only works with its author standing next to it.

You leave with one of the three named, and the smallest change that fixes it before it becomes a habit.