Package & Version

Preparation guidance — the schema and validator below are proposed, not a live submission API.

Package And Version Your Work

Wearable manifest fields: schemaVersion, title, kind, slot, bodyFits, rigVersion, files, finishes, coveredSlots, rightsDeclaration and screenshots. Creator identity is assigned by the authenticated server. Each body fit links a GLB and any permitted masks/offsets. Server-calculated hashes bind the review to exact files.

Proposed upload bounds: 50 MB compressed, 150 MB expanded, bounded file count and compression ratio. Reject path traversal, symlinks, nested archives, executable files and remote resources. Scan and parse in isolated workers with memory/time limits and no outbound network.

Never replace a published file in place. New revisions return to review. Retain prior files and entitlement references. Delisting stops new sales without deleting receipts. Compatibility quarantine, ownership revocation and refunds are separate explicit operations.

Suggested working folder

This is a local organization example, not an upload schema. Keep licensed third-party source out of any distributable package.

my-original-item-v001/
  README.txt
  source/
    my-original-item.blend
  exports/
    item-test.glb
  textures/
    base-color.png
    normal.png
  previews/
    front.png
    side.png
  review/
    rights.txt
    test-results.txt

What to put in the README

• Your asset title, version and a short description of its intended use.
• Authoring application and version; export settings and export date.
• Measured dimensions, pivot, triangle/material counts and texture dimensions.
• For wearables: each tested body, rig revision, slot and layer combination.
• For emotions or animation: named controls, timing, compatibility and cancellation behavior.
• Known limitations and reproduction steps for any unresolved issue.

Do not claim a kit revision that has not been published or tested. Record unknown compatibility as unknown.