Pr0j is the software implementation of Scalable Video Design Systems: a production platform that turns projects, shots, versions, approvals, render targets, and client delivery into durable creative data.
Modern motion designers and creative teams are now expected to operate across too many roles at once:
That is normal now. But the operating model never caught up.
Pr0j exists because creative work needs better infrastructure than scattered files, generic task boards, spreadsheets, chat threads, and sealed proprietary project files.
Scalable Video Design Systems is the methodology. Pr0j is the implementation layer: the place where productions, shots, versions, render targets, reviews, client delivery, and production memory stay connected.
Pr0j is built for businesses, studios, agencies, and creative operators who need a shared source of truth for modern video production.
It can support one top-level ORG_, with multiple BIZ_ records beneath it. In a business context, those may represent internal business units. In a studio or agency context, they may represent clients.
Every production moves through the same six phases. Each phase has a clear purpose and produces durable state that the next phase reads from.
Context, intake, brand, stakeholders, requirements.
References, direction, structure, shot plan, deliverables.
Active creation. Writing, design, recording, build.
Shot-level assets, metadata, variants, versions.
Review, assembly, feedback, approvals.
Delivery, portal, archive, reuse, future availability.
The final state of a modern production is not just shipment. It is persistent access, client delivery, archive, reuse, and future availability. That is why the last phase is 05.LIVE.
Pr0j treats shots as structured, addressable production objects. Each shot can carry source data, canvas data, versions, aspect variants, approvals, notes, and render targets.
The final file is one output. The shot is the durable unit that survives.
If teams need to find, discuss, revise, render, approve, or automate something, it needs a stable address. JANK is Pr0j's address system: dot-notation for creative production.
JANK stands for Just Add Names to Knowledge. It is the naming convention that lets every entity in the system, from a brand down to a single aspect-ratio version, hold a permanent, human-readable identity that agents and automations can also address.
Artists, producers, and clients should all work from the same source of truth, but they should not have to see the same interface.
Everyone sees the truth at the altitude they need.
AE0N is Pr0j's motion and rendering layer: a real-time environment for designing, previewing, rendering, and adapting the common ninety percent of motion shots teams need to produce today.
It keeps design, animation, preview, output, and production state connected instead of trapping the work inside isolated project files.
Most production shots do not need a heavy desktop compositing round trip. They need structured source data, brand tokens, editable text, reusable presets, multi-format outputs, fast preview, and reliable version state.
AE0N is designed for that layer of work: the repeatable, high-volume, production-critical shots that should stay fast, editable, system-aware, and connected to the rest of Pr0j.
When a shot needs deeper compositing, custom effects, or specialized finishing, it can still graduate to After Effects. The point is not to remove the instrument. The point is to stop making every shot depend on the heaviest possible workflow.
Hero shots can still graduate to After Effects when they earn it. The common ninety percent should stay fast, structured, and inside the system.
AE0N is the motion layer Pr0j needs for video production to behave like software.
M0SH is Pr0j's live-performance mode: a way to use the AE0N real-time rendering engine and project data for events, installations, launches, VJ sets, and live visual systems.
The same shots, variants, tokens, presets, text, imagery, and motion systems used in production can become source material for live output.
M0SH turns the production system into a performance instrument.
After Effects can stay the instrument. It should not have to be the archive, database, review system, delivery system, and institutional memory.
Pr0j keeps the system outside the sealed project file, so the file becomes what it always should have been: one rendering of something durable.
Pr0j's nuts-and-bolts implementation of SVDS. Every module operates on the same production data.
Pr0j is built to support SVDS at the business, studio, and agency level. It can model:
SVDS is also being validated through reference implementations such as Hyper-Brand, EasyVideo, Jordan Lloyd & Co., and MR-KT.
Pr0j is being built for teams that have outgrown generic project management, folder chaos, and sealed production files.