Assets
Characters, environments, props and reusable production assets.
Production system · Maya live link · R&D
ZapNotion is trying to make productions understandable as productions: workstreams, assets, shots, workflow areas, creator tools and publish state — instead of making the artist navigate a filesystem and remember how every application expects the work to be arranged.
Hybrid Controls ↔ proven Maya mechanics
The big idea
ZapNotion's architecture already treats a project as more than a directory. A production can contain workstreams; workstreams enable workflow pieces; creators work with logical Assets and Shots while Working, Published, Output and Data locations stay implementation detail rather than the primary interface.
The ambition reaches beyond animation. The current code already has workflow profiles for animation, games, music, writing, marketing and general/custom projects. That is the direction: one studio shell that can understand what kind of work is happening without forcing every project into the same rigid folder tree.
Animation workflow
These are real workflow areas already represented in the current application architecture, not a speculative marketing diagram.
Characters, environments, props and reusable production assets.
Concept, design and visual-development material.
Layout, animation and shot-production work.
Editorial, dialogue, music, sound and assembled timelines.
Look development, lighting, render setup and generated imagery.
Simulation, effects and compositing support.
Current proven floor
What 0.3.2 is actually proving
The current strategy deliberately stops trying to replace the proven Maya Asset Builder before a replacement earns parity. ZapNotion's Hybrid Controls discover and command the same legacy attachments, while adding stable semantic identity and a modern creator-facing layer around them.
The current production engine is the proven system, not an experimental replacement graph.
ZapNotion adds semantic identity as metadata rather than destabilising proven scene names.
Modern controls can drive the old mechanics, and Maya-originated changes can be read back without rebuilding the scene.
Unsaved Maya changes continue to block Publish until the creator deliberately saves the current asset.
The vision
Productions, workstreams, project-specific workflow pieces, Assets, Shots, stage tools, outputs and DCC connections working as one understandable production environment.
The reality now
The shell and broader workflow architecture exist, but the Asset Builder is currently the most heavily proven creator path. VS02 0.3.2 is about making that path reliable by adapting the modern UI to the legacy production mechanics rather than overstating the maturity of the whole system.