Assets, model files, and images
Category: Content Creation. Status: Normative.
Content records and binary assets have separate lifecycles. A model, texture, preview, rendered image, or derived AR file is usable only when its record, object path, version, checksum/metadata, and ownership agree.
Model assets
Upload model files through the card asset workflow. Keep source formats and normalized/runtime derivatives distinguishable. After upload:
- confirm completion rather than assuming a signed upload succeeded;
- inspect model scale, orientation, hierarchy, and mesh names;
- select the active asset version;
- bind workflow Mesh nodes to verified mesh IDs;
- preview visibility, materials, and transforms;
- retain prior versions for recovery and published references.
Do not rename mesh identities casually after workflow or signature bindings exist.
Image workflow
Image cards maintain version history. Upload a new image or supported video, add a bounded version note, then activate the desired version. The active version remains the visual root even while older versions are inspected.
Image annotations, drawing layers, boxes, and comments belong to the relevant version/card context. Review an older version without accidentally making it active.
Generated images
There are separate workflows: queued renders, Render Studio authoring, and the standalone browser `<vertcie-image>` element. The image element does not run Render Studio. It can render a missing image locally and, with store=true plus boardId, finalize it as a versioned image card. Browser-only mode makes no persistent writes. See the runtime-image guide for deployment status, board permissions, properties and completion events.
Rendered product images are derived from a published file, selection, camera, environment, size, format, and optional board context. A request may enqueue work. “Accepted” is not the same as “render complete.”
For consistent output, record:
- permanent
publishedFileId, resolved publication revision, latest/pinned policy, and selection revision when applicable; - rotation, dolly, boom, field of view, and target height;
- environment rotation/intensity and backdrop;
- width, height, format, transparency, samples, and renderer version.
Textures and previews
Texture sets should identify semantic roles such as base color, roughness, metalness, normal, bump, alpha, emissive, or displacement before authoring the material. Preview thumbnails are conveniences; validate the full-resolution asset in the model.
Recovery and Trash
Never hard-delete an apparently unused asset during normal content work. Mark important assets as kept, move unwanted assets to Trash, and use Restore when needed. Items remain recoverable until the configured retention and deletion process completes.