Sidebar IA changes that fall out of moving vendors to project level (they can hold tokens from multiple collections). Frame 01 marks what changes on the current sidebar; frame 02 is the proposed result. Frames 03–04 show the full collection submenu (Overview · Tokens · Attributes · Supply · Rarity · Guards · Claim defaults) for a Draft/Review collection and for a Live one — where the core policy pages and Claim defaults lock. Tracked in vendor-project-scope-migration.md.
What moves out of the collection:
· Vendors → up to Project level (a vendor can span collections).
· Sales / Claims History, Analytics, Revenue → removed; these live only at Project level now, filterable by collection.
· Defaults → renamed Claim defaults (Costs + Rules), the only collection-level defaults that remain.
Project level gains:
· Vendors — one surface for all vendors, each drawing inventory from any collection.
· Revenue templates — named split + buyback presets adopted per vendor.
· Sales & Revenue — analytics filterable by vendor and collection.
Collection keeps: Overview, Minted Tokens, and Claim defaults (Costs + Rules) — required-valid before the collection can go Live.
Collection submenu (Draft / Review):
Overview · Tokens · Attributes · Supply · Rarity · Guards · Claim defaults.
Claim defaults is the new item — cost (free / ICP / ICRC-1) per tier, plus optional requirements. It must be valid before the collection can be submitted to Review.
Everything in this submenu is editable while Draft or Review; each sub-page auto-saves.
At Live, core policy locks read-only:
Attributes, Supply, Rarity, Guards and Claim defaults are locked — issued tokens depend on them, so they can't change after Live.
Overview and Tokens stay open (Tokens for minting / managing issued copies). The pages still open read-only so you can see what was set.