Package
In plain words: 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.
- 1The manifest records revisions, lineage, tools, findings, approvals and known use limits.
- 2The package carries no credentials or permission for other uses; consumers may refuse it.
- 3A bad reference or revoked consent marks dependent revisions stale without erasing history.
Words on this page, decoded click one for its card
A consumer needs to know exactly which images it received and which uses their acceptance covered. atelier.export_visual_package@1 seals that answer in VisualAssetBundle@1; atelier.review_visual_package@1 returns findings without changing approved material.
What crosses the boundary
The package manifest lets another craft inspect the accepted work before using it. It binds the revision/digest, target profile, assets, visual constraints, source and derivative lineage, tools/provider receipts, validators, findings, approvals, and known use or likeness boundaries.
Foundry uses that account to decide whether exact revisions can enter an engine and support playability. Broadcast judges their use in claims, storyboards, timeline, render, accessibility, and publication. Either consumer may refuse. The visual director's approval answers the original commission; exported files cannot extend that judgment to an entirely different one.
The handoff therefore carries no SigilID Badge, secret, provider session, approval for another use, or downstream effect authority.
Effects, failure, and return
Paid generation and external handoff each need their own effect record, binding an idempotency key and exact payload digest. If an acknowledgement is missing, keep the result unknown. Reconcile that same effect with its provider or consumer before deciding whether another attempt is permitted.
A bad reference, revoked consent, or later finding makes every dependent revision stale. Preserve the accepted history so it remains possible to explain what was used and why. A correction must address those dependencies rather than overwrite the accepted package.
Restart first recovers the pinned PatternWorkflow, schema, sources, providers, tools, receipts, and artifacts. If parked work is incompatible with them, it must drain, migrate explicitly, or end non-complete. Deletion follows the same chain of custody: inventory derivatives and handoffs, request authorized downstream removal, and record any material still held externally.
Proving package
Begin with a local, style-led 2D commission using licensed references. Freeze the brief, version the direction, make concept plus sprite/texture assets, probe and normalize them, and complete a bounded repair before accepting VisualAssetBundle@1. This first proof includes no sound, engine import, channel render, PortalCloud Model, paid generation, or public release.
Then try separate landscape and portrait hero profiles. Keep the accepted stills and animate one or two exact boundary frames through an admitted Video implementation. Probe loop and export behavior before sealing the successor package. The declared still or motion boundary can each be an honest finish.
Model-returned sound may cross into the package only with pre-execution role authority, its independent SemanticFacetAdmissionReceipt@1, and the shared compound parent. Retain all three with the admitted material. Motion follows each role's admission. Broadcast alone accepts the final editorial audiovisual relation.