Launch wave collections (informative)
This note is non-normative. It records early ÐogeRelics-style collections being built against the Dogenals standards tree in spec/, so implementers have a concrete reference while wallets and indexers catch up.
Wave 1 (Ðrok + dogenals.com stack)
| Collection | Repository / path | Role |
|---|---|---|
| Dogenal Chads | dogeco/drok → collections/dogenal_chads/ | Waist-up Shiba “Chad” portraits; primary Ðrok image pipeline today. |
| Game Doge | dogeco/drok → collections/gamedoge/ + separate handheld UI repo | Parody handheld Nintondo Game Doge; parent HTML shell + composable LCD (inscription child and/or Grok Imagine); collaborative mint via command.dog/api (planned). |
Both collections aim to conform to Dogenals norms (continuous doginal numbering, multi-marker expectations, and specs such as DogeRelics, ÐMS, ÐMP where applicable) as those specs stabilize after Dogenals Genesis and related launch drafts.
See also
collections/registry.jsonin the Ðrok repo — machine-readablecollections[]includingdogenalsmetadata.- DogeRelics core —
parent/ delegate patterns relevant to Game Doge recursion.