Package upload is the engine/v1 adapter for uploaded collections (docs/uploaded-collections.md §5.3, §7–§10, §0a). Core knows it as one more engine; each collection's params name one sealed asset store ("store:<id>", r/…/assets/v1) and Bind locks that store to the collection while it is a Draft. After the reveal every token shows the artwork of the slot a salt-keyed permutation gives it.
What holds, and why:
- art theft (T1): ValidateParams accepts a store only when its owner signs the Create tx; Bind needs caller == collection creator == store owner, from a wallet;
- no swap after sale (T2): stores are sealed before Bind and never change; params are fixed by core; Bind and Unbind run only while core says Draft, i.e. before any token was ever minted;
- one collection per store (T3); slots == maxSupply (T13);
- snipe resistance (T4/T5): before Final core shows its placeholder and never calls Render/Traits; every read here checks Final too; the assignment needs the final salt; Render answers core's real call only (CollectionID, params and seed must match core's), so RenderWith (CollectionID "0") always gets the generic card;
- SA-L5: this realm and assets/v1 may not be payees (Bind refuses);
- I-12: Render, Traits and ValidateParams only read; Bind, Unbind and Settle are crossing functions; there is no exported non-crossing mutator.
The adapter is stateful by design (bindings and cached keys), declares Living false, takes no fee (D3) and holds no coins.