Visitor and collectible cycles
Updated: 2026-09-06. Current experience and unresolved mechanics.
Visitor flow
Browse the public flex → inspect a changing Dub → consider a mystery Stash or The Chase → own/display → follow new Looks and activity.
Buying a mystery collection bypasses discovery. Hunting seeks individual items through a game/scavenger experience. Both are central. The Chase has a playable three-lock pilot; production acquisition economics remain open. Creator/brand self-service and sponsorship are optional extensions.
Implemented cycle
Browse without a wallet → inspect a decoded Devnet Dub or public Stash → filter/sort → follow a confirmed test event → inspect/share its fixed snapshot. Hidden records and member details stay out of public responses. My Stash offers a real address/balance read. No hunt or purchase workflow is open.
Issuance fixes origin traits and cadence; the program records birth time and derives the due state from its Clock. Refresh reads that state without a transaction. Missed intervals jump directly to the current state with one previous Look. Minute/hour/day/calendar-month/calendar-year schedules are implemented; claims/transfers never restart them. Ordinary animation is separate. HOMEPAGE-V1.md defines reads, timing and errors.
Product cycles to define
| Cycle | Open rules | Available foundation |
|---|---|---|
| Share a moment / clip as a member | Future campaign rights, program entry, reward eligibility, attribution and pre-enrollment posts | Moments page and sample poster/caption exports; no member enrollment or payouts |
| Spectate and return | What is interesting to follow? Featured ranking, notifications and sharing | Sample public showcase and real lab record reads |
| Hunt and discover | Clues, proof, difficulty, availability, free/paid boundaries | Issuer-authorized claim; no hunt game |
| Buy and reveal a Stash | Contents/disclosure, price, odds if applicable, reveal timing, refund/ownership terms | Concept page; atomic five-member payment/transfer tested on Devnet, no consumer checkout |
| Claim and recognize | What discovery grants; founder/finder rights for hunted versus purchased items | Separate first-finder and current-owner fields |
| Own and display | Owner control, public identity, privacy and benefits | Transfer preserves finder and ciphertext |
| Change and evolve | Trigger, cadence, permanence, owner influence, recognizable identity | Issuance-bound program schedule plus authenticated type-specific rendering |
| Sell and swap | Offers, listings, currency, fees, atomic settlement and receipts | Signed transfers and atomic test payments; no consumer marketplace |
| Participate with a Crew | Membership, shared access versus ownership, rewards | Sample community page only |
Looks, Shifts and prices
Viewing and visual animation do not write transactions. V2 computes scheduled states from fixed birth rules; permanent milestone events or owner-triggered gameplay would require a separate explicit design. The same item should remain recognizable, but the meaningful visual rules and final renderer are open.
A Look is the current named appearance. A Shift changes that Look without necessarily being an improvement. Glow-up is optional language for a perceived positive visual change. Do not make evolution imply rising value. Fixed prices, asking prices, completed sales and estimates remain separate. Versioned test application events vary asks; confirmed sale receipts remain historical facts.
The implemented platform test price follows a fixed issuance profile and may rise, fall or stay flat. A future market value estimate still needs defined inputs and uncertainty. Rarity may depend on supply/traits; uniqueness alone does not establish scarcity or demand.
Mystery collection questions
What does the buyer know about quantity, categories, rarity and price before payment? Are contents assigned before buying or at reveal? When can they be inspected or transferred? Can a community participate without sharing ownership? Who receives original-finder credit? Is the collection bought in one transaction or many? Are fixed rarity prices or a bulk discount useful? High collection prices are an illustrative ambition, not an offer or validated demand.
Choose these rules through page review and focused discussion, then define source/read/write/confirmation behavior before wiring the corresponding API. Keep current choices in DECISIONS.md and the next working slice in CURRENT-WORK.md.
Issuance and selective reveal
ASSET-SYSTEM.md specifies the implemented test sequence: freeze issuance/rarity rules → encode an immutable identity → confirm its record → derive permitted appearance/state → surface only approved fields. Public selection favors mystery Stashes and selected rare/expensive items; remaining inventory stays hidden from public feeds. Ownership, reveal permission and featured selection are separate states. Discovery grants the assigned reward: free-claim eligibility or reveal only in the current pilot. Disabled paid offers cannot fall back to free claims. The program computes a rarity-based initial test price at creation; it is not evidence of a market floor.
The discovery specification defines the implemented signal → fragments → Shift loop, captured-Look clues and claim/reveal boundaries. Reservations, paid rewards and final finder rights remain open.