Atelier

In plain words: App: Atelier (visual art)

Designed 2 min read 5 glossary terms 22 connected pages
The short version written for the Snayu team

Atelier takes a visual commission, such as a still image, animation or visual effects package, from brief to an accepted, traceable result, keeping direction, sources, candidates and approved revisions on record.

Why read it: Read when working on image or video generation features, or deciding what visual work Atelier owns versus music, editing or game import.
  1. 1The commission declares its finish: an accepted still, accepted motion, or a sealed VisualAssetBundle.
  2. 2You, the Operator, remain visual director; generators and editors are replaceable tools.
  3. 3Stops before sound, engine import, final editing and publication, which other apps own.

Designed Accepted design; no registered workflow or delivered implementation.

Words on this page, decoded click one for its card

In this section 5 pages

Brief Atelier: the visual brief How Atelier fixes a commission before generation starts: purpose, audience, target format, budget, roles, acceptance criteria and a frozen set of reference images with their rights and consent. open → Direction Atelier: visual style rules How Atelier turns your taste into a reviewable style guide covering palette, composition, light, camera and exclusions, and uses it to judge and correct candidates. open → Assets Atelier: making visual assets How Atelier produces and reviews images, sprites, textures and 3D models as candidates, with full lineage of sources, tools, transforms and review findings. open → Motion Atelier: animation and video How Atelier handles moving visuals: animation, transitions, camera moves and generated video, typically from an accepted first frame through video generation to a reviewed sequence. open → Package Atelier: sealed visual package How Atelier seals accepted visuals into a VisualAssetBundle that other apps can inspect, plus how it handles effects, failures, restarts and deletion. open →
The original text Underlined words open their plain-English card.

The MagusYou, the Operator 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 MagusYou, the Operator 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 PatternWorkflow 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 RunJob Record; later motion begins a forward InvocationJob Request 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 PrismVision & Media 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 PatternsWorkflows to @2. No Portfolio registry or RunJob Record used revisions 3 or 4; no executable migration exists, and historical references keep their meanings.

Workflow · Vision · Composition Portfolio