Assets and the reusable library

One asset system

WorldPack is the reusable asset-library layer, not a second asset system parallel to QWAY. Assets retain the existing AssetManifest, archetype, normalization and persistence architecture. Resolution precedence is explicit user reference → project → user → standard. Project scope belongs to a saved project ID; it is not access control.

Search the Assets browser, filter by scope and inspect aliases. An alias is a lookup name, not stable object identity. Ambiguity is reported. Renaming an alias must not silently rebind an existing instance.

Import and analysis

Upload GLB bytes with a description. The API checks magic, bounds and file safety; deterministic TypeScript analysis records content hash, hierarchy, transforms, meshes, materials, textures, skins, morph targets, clips, bounds and measured feature candidates. Manifests are immutable revisions. Reanalysis creates a new pin; adoption is explicit.

Geometry evidence is separate from semantic suggestions. A likely worktop label may refer to a measured candidate; an AI response cannot invent collider vertices, surface coordinates or exact physical constants. Inspect confidence, accepted/suggested/disputed/unknown state and producer metadata.

Standard content and licensing

The implemented reviewed source is a bounded Kenney CC0 library, not arbitrary internet asset search. Get standard CC0 library starts an import job. Downloads are hash-checked, bounded and cached; repeated import is idempotent. Newly available standard assets are templates, not an instruction to add every item to the scene.

Inspect origin, author, license and attribution requirements before redistribution. A valid WorldPack proves byte integrity, not that you own redistribution rights. User-supplied licensed assets keep their metadata; no license is inferred from a filename.

Replace without losing intent

Replacement retains the scene instance identity and explicit semantic/user overrides. It changes pinned asset dependencies through a typed edit. Existing feature references need a justified mapping to replacement features; unresolved mappings fail rather than guessing. Undo restores historical dependency receipts. Reopening a project never silently adopts newer asset analysis or inference.