The production OS motion design never had.
Status: in development · private beta
Pr0j runs motion graphics like a real production: productions made of shots, shots carrying versions and approvals, rendering routed to whatever ships each shot best, and the whole layer operable by human producers and AI agents alike.
The pattern
Open a motion project file from a year ago and try to answer basic questions. Which brand was this for? Which version did the client approve, and why did it replace the one before it? Is the render on the server the same as the one that shipped? The file can't tell you. Everything that made the work meaningful (its brand, its approvals, its history, its running order) lived in someone's head, an email thread, and a naming convention that broke the third time someone saved over it.
Every discipline that scaled built a system for exactly this. Software got version control and issue tracking. Design got multiplayer files with history. Film has run on production management for a century: shot lists, call sheets, dailies. Motion graphics still runs on file names, spreadsheets, and the memory of whoever has been there longest, which means a studio's real capacity is whatever one overloaded lead can hold in their head.
It's also why the role motion needs most keeps failing to exist. Hire a producer into a studio with no system to run and they drown in the same inbox as everyone else. The missing piece was never just the hire. It's the system that makes the hire possible.
What it does
Pr0j models what motion work actually is. Productions are made of shots; shots carry versions; versions carry status: brief, in progress, review, approved, delivered. Real production roles sit across the top, so the work is schedulable, staffable, and accountable instead of tribal.
The deeper move is where the truth lives. Every shot, brand, and version gets a permanent, human-readable address that survives renames, folder reshuffles, and round-trips between tools. The source of truth moves out of the project file and into the data; the file stops being precious and becomes what it always should have been: one disposable rendering of something durable. Open the work a year later and it can tell you what it is, who approved it, and why.
SVDS is the method; Pr0j is where the method runs.
After Effects becomes a plugin
There's a race on to give AI assistants hands inside creative tools, and everyone in motion wants one for After Effects. It won't work the way they're imagining, because After Effects was never built to answer the phone: every attempt so far is a fragile panel wedged inside the app. One machine, one open project, supervised by a person, amnesiac the moment the file closes.
The better move isn't controlling After Effects. It's holding the story of the work (the brands, the shots, the versions, the running order) in a layer any surface can talk to. Then rendering becomes routing. The common ninety percent of shots (lower-thirds, type, cutdowns, templated sequences) ship through M0SH, Pr0j's real-time web renderer, which previews at full resolution instantly and outputs every aspect ratio from one source. Hero shots queue to After Effects running as a worker: no longer open on anyone's desk, no longer babysat to the end of a progress bar. Shots that are really a prompt go to generative video. After Effects goes from the center of the universe to a plugin: still the most powerful instrument in the building, now called only when a shot has earned it.
Built for what's coming
This is where Pr0j stops being a management tool and starts being infrastructure: the production layer speaks MCP, the open standard that lets AI assistants operate software rather than just discuss it. An agent can't read a project file; it can read Pr0j. Which means the work agents are about to do in every studio (drafting shot lists from a brief, versioning a campaign across brands, queuing renders overnight, reporting what shipped and what's blocked) has a structured layer to do it through, with a human producer holding approvals. The "After Effects MCP" everyone keeps asking for turns out to live outside After Effects, and this is it: agentic workflows don't get bolted onto the pipeline later, because the pipeline was built assuming they'd arrive.
The bet
The wager underneath: the project file was never the source of truth, and the teams that realize it first will compound while everyone else rebuilds. When the work is addressable data, nothing is ever lost, versioning is free, any renderer can serve any shot, and each production makes the next one cheaper: the thousandth deliverable stops costing what the first one did. There's a second wager stacked on the first. The next wave of production labor will be part human, part agent, and it will route through whichever layer is legible to both. Files are legible to neither. Pr0j is being built as that layer: the production OS motion never had, designed so the tools, and now the agents, plug into it.