Atelier
The Magus asks for a still image that can stand on its own. Once accepted, that image may later become the first frame of a moving sequence. Atelier carries either commission to its declared finish, keeping visual direction, source influence, candidates, and accepted revisions attributable.
The craft can combine generators, editors, renderers, procedural work, capture, and authored material. The Magus remains visual director. Here VFX means visual effects.
The work
Start with Brief: what should exist when the commission is done, and how will you judge it? Direction turns those intentions into a visual language.
Assets makes and reviews images, models, textures, and other visual roles. Enter Motion when the requested work changes through time. Once a result is approved, Package seals the exact revisions another craft can admit.
The requested finish
Choose the requested finish when admitting the commission: an accepted still, accepted motion, or an approved immutable VisualAssetBundle@1. The principal Pattern atelier.build_visual_package@3, published by atelier.studio revision 5, works from that commission, frozen references, target profile, and acceptance criteria. If it cannot reach the requested boundary, it must return exact partial or non-completion under the pinned score.
Reaching a requested still boundary completes the Run; later motion begins a forward Invocation over the retained artifact. Motion follows both motion within the pinned score and separately admitted continuation.
Atelier owns the commission, visual judgment, candidates, accepted revisions, provenance, and package. It stops before sound production, engine import, final audiovisual assembly, publication, or rights certification. Riffmaw owns music; Language Edition owns timed-language editions; Foundry owns engine integration; Broadcast owns picture sound, the final editorial relation, and publication.
These craft boundaries can meet in one proposed Atelier studio, with shared controls and a timeline. The studio example distinguishes that broader operator experience from this visual contract and follows joint generation, music revisions, and game-directed work.
Revision continuity
Earlier designs and their exact successors
Revision 5 supersedes revision 4, advancing atelier.build_visual_package and atelier.forge_visual_sequence to @3 with exact ImageJob@2/VideoJob@2 Prism placements and pre-execution compound-facet authority. Revision 4 replaced SyncCueMap@1 with MusicCueMap@1, routed returned sound by role, and advanced the former @1 Patterns to @2. No Portfolio registry or Run used revisions 3 or 4; no executable migration exists, and historical references keep their meanings.