ZNZAPNOTIONStudio · VS02 0.3.2 SVILX ↗

Production system · Maya live link · R&D

A studio layer
between the project and the tools.

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.

ZAPNOTIONStudioVS02 0.3.2
Production / Film & Animation / Asset
AssetsDesignShotsEditRenderFX
ASSET BUILDER Creator workspace

Hybrid Controls ↔ proven Maya mechanics

Surface USurface VHeadingScale U/V
Asset Builder · connected production context ● MAYA LIVE

The big idea

Create production items.
Not folders.

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

The production surface

These are real workflow areas already represented in the current application architecture, not a speculative marketing diagram.

01ZapNotion / Maya

Assets

Characters, environments, props and reusable production assets.

02ZapNotion / External

Design

Concept, design and visual-development material.

03ZapNotion / Maya

Shots

Layout, animation and shot-production work.

04Edit DCC

Edit

Editorial, dialogue, music, sound and assembled timelines.

05ZapNotion / Maya

Render

Look development, lighting, render setup and generated imagery.

06Replaceable backend

FX

Simulation, effects and compositing support.

Current proven floor

Hybrid Asset Builder

ENGINElegacy_proven_v1production default

What 0.3.2 is actually proving

Modern controls around mechanics that already work.

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.

Surface U / VHeadingScale U / VConnector moduleCore import / replaceCreate from Maya selection
01Legacy Maya graph stays authoritative

The current production engine is the proven system, not an experimental replacement graph.

02Stable IDs without renaming Maya nodes

ZapNotion adds semantic identity as metadata rather than destabilising proven scene names.

03Two-way creator control

Modern controls can drive the old mechanics, and Maya-originated changes can be read back without rebuilding the scene.

04Publish respects real scene state

Unsaved Maya changes continue to block Publish until the creator deliberately saves the current asset.

The vision

One studio surface.

Productions, workstreams, project-specific workflow pieces, Assets, Shots, stage tools, outputs and DCC connections working as one understandable production environment.

AnimationGameMusicWritingMarketingCustom

The reality now

One slice is much further along.

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.

VS02 0.3.2RUNTIME 46SCHEMA 9ACTIVE R&D