Toko · Phase 2 · Consistency reference

Asset spec — states gallery.

First-pass mock for asset specs — named templates of required media slots, per Design Documentation/Phase 2/asset-spec-design.md. A spec is applied to token types and gates go-Live: a token can't go Live until every required slot has a file. It verifies existence only, never content — human review stays the content check. First consumer: the graded-slabs programme (front + back photos required per slab). Snapshot-on-apply, versioned — editing the template never mutates tokens that already carry a copy.

01Project · Asset specs listA project-level template list — same card grammar as revenue presets. Each spec shows its slots, version, and where it's applied.
Studio/Toko Studios (internal)/Asset specs

Asset specs

2 specs
Graded slab v2
2 required slots: Front photo · Back photo — applied to 1 token type (Slab, Vaulted Slabs — Series 1).
Signed print v1
1 required slot: Signature close-up — not applied yet.
02Spec editorA spec is a list of slots: key (slug, unique in the spec) + display label + kind (V1 ships image-only) — all listed slots are required in V1 (optional slots are a V2 nicety). Saving a change bumps the version; already-applied token types keep the version they snapshotted until re-applied pre-Live.

Asset spec · Graded slab

frontFront photoImageRequired
backBack photoImageRequired

Currently version 2. Saving changes creates version 3 — token types that already carry version 2 are not changed until you re-apply.

03Batch apply · pick token typesThe established batch-select pattern (token-state policy attach, bulk listing): pick a spec → select token types → apply. A collection with one token type is effectively a whole-collection application. Live tokens are skipped (locked).

Apply · Graded slab v2

✓Slab · Vaulted Slabs — Series 1 (42 tokens · 40 Draft, 2 Live — Live skipped)
✓Slab · Vaulted Slabs — Series 2 (18 tokens · all Draft)
Poster · Print Vault (no physical media requirement)

Each selected type snapshots version 2 of this spec. Editing the spec later never changes them — re-apply pre-Live to update.

04The gate · token slots + status checklistExistence check only, on effective state, via one shared function (the R34/R61 pattern; mirrors the default-variant R50 gate). The token editor shows the slots; the collection status checklist names exactly which tokens are missing which slots. Slot files come from the project media library (or direct upload into the slot, which lands in the library) — for slabs, the vault partner's intake photos.
Toko Studios/Vaulted Slabs — Series 1/Manage

#042 · Required media

Graded slab v2
Front photo
✓ on file
Back photo
missing — required

Collection status

✓
Required media — Series 1 (40 of 42)
40 tokens have every required slot filled.
✕
2 tokens missing required media
#042 — missing: back · #051 — missing: front, back. These can't go Live until their slots are filled.
Note (not UI) — open questions

From asset-spec-design.md: per-variant slots (deferred — digital tokens only; variants never apply to RWA items, ruled 2026-07-07); optional slots and non-image kinds (V1 or V2); whether a token type can carry multiple specs (recommend one — merge templates instead); and the creator-facing name ("Asset spec" vs "Media requirements" — glossary entry once ruled). Generator-produced art is not a spec slot in V1 — specs cover additional required media. After Live, slot files follow the standard media mutability rules; the spec itself locks with the token.