First-pass mock for the Phase 2 RWA archetype (real-world assets — vaulted 1:1 graded slabs), per Design Documentation/Phase 2/rwa-archetype.md. What is decided: the Rwa enum variant is platform-gated (Toko only at first) via an allowlist check at creation — external creators never see the card; same enforcement spine as Phase 1 archetypes; every token is a 1/1 backed by a vaulted physical item. Capability numbers shown here are placeholders — the RWA defaults table is still to define. Custody flows connect to Vault admin and Vault management.
Start by choosing a collection type.
Every token in this collection is backed by a physical item held in vault custody. A token can only go Live once its item is vaulted and verified.
2 of 3 items verified. Custody state comes from the vault provider's workspace; it is never self-attested by the project.
From rwa-archetype.md: the ratified defaults table (ceilings are inherently small — every token is a 1/1 physical item), the seeded sale defaults (Tradeable, but redemption interacts with listing state), and exactly how the custody pipeline gates minting. This gallery pins the UI shape so those rulings have somewhere to land; frames 02–04 update when the numbers and redemption rules are ratified. RWA is not part of the Phase 3 burn/reward path — the gate is a platform allowlist, not a Reputation unlock.