The jobs that exist because two machines can't talk yet

Here is how this studio makes a piece of art. An agent decides what's needed. It writes the prompt and picks the reference images. Then a person copies that prompt and those references into an image model by hand, brings the result back, and a second agent checks it against the written standards.

The person in the middle isn't doing the art. They're the connection between two systems that can't yet hand work to each other. The thinking is good enough. The image generation is good enough. The wiring between them isn't, so a human carries the bytes.

That's a strange job, and it won't last. The day an agent can call the image model directly and get the result back, the courier disappears — and so does the rule capping how many images can be in flight at once, and a page of prompt wording written to make up for a generator that doesn't know our conventions.

So the studio started writing down, for every rule and role, which missing capability it exists for. The queue for spending leftover weekly allowance exists because that allowance expires and can't be saved. The Project Manager relays messages by hand because agents can only talk one to one. Rules about checkpointing exist because a conversation gets expensive as it grows. Each one is an answer to a limit that will move.

The point of writing the limit down is knowing when to delete the rule. An organization that forgets why it exists outlives its usefulness, and these are young enough that every part of ours can still name its reason. When the limits move, the right response is to delete what they justified, not to defend it because it's well written.

Which makes the interesting artifact not the workflow, but the record of it: what a temporary way of organizing actually felt like from the inside, written down while it was still true.