Discovery entrance study — 3 October 2026 Question New visitors ask what Eiko or Gyro is. Showing a selected vault and a normalized 1,000-unit comparison explains neither the catalogue nor the reason to explore it. This study tests a front door: understand the product, recognize an asset, choose a route. It does not redesign execution, calculate a yield estimate or ship a new first-visit router. Scope and input evidence - Current dev baseline: bfa5ef8d. Only review galleries and their local assets change. - Eiko app: TIBBIR, Base, 0.26 strike, disconnected. Gyro app: WBTC, Ethereum, 65000 strike, disconnected, intro=1. Desktop 1440x1000, phone 390x844. Captures use https://thetanuts.finance/dev/ URLs, never localhost. - Both app snapshots were read successfully. Public RPC retry/throttle warnings and the existing WalletConnect setup warning occurred. No wallet was connected. - Eiko index.html still foregrounds VIRTUAL; Gyro index.html foregrounds BTC. This observation informed the exploration, not an authorized landing rewrite. - Current site configurations contain Eiko VIRTUAL/TIBBIR/ROBO/OPG and Gyro's broader three-chain inventory. Configuration is NOT proof of tradable listings. - eiko/eiko.jpg supplied color/type/mascot references only. Its AI signals/chat claims were deliberately excluded. Existing Eiko mascot used as identity input. - Built-in imagegen generated three independent Eiko hypotheses and a Gyro catalogue adaptation. No claim about the underlying image model version. - All exact prompts are in all-prompts.txt. Generated words and diagrams are proposals. A — Asset catalogue Adopt for a possible first implementation: four assets visible together, a clear product sentence and one Explore action per card. The recognizable asset imagery gives the selection presence that tiny ticker tabs lack. Adapt: remove repeated 'Explore vaults and options for...' prose inside every card; keep the product explanation once. Keep the hero short and trim decorative art before it displaces assets on a real phone. Use approved asset icons where available. The generated 'Browse without a wallet' search-looking pill is ambiguous: make it either a genuine labelled search input or ordinary reassuring text, not a fake field. Do not interpret an Explore options link as a statement that a listing is live. B — Goal-led entrance Adopt as an alternate direction: the two routes are legible, both present on phone, and 'No vault deposit needed' survives beside buying. The quiet existing-share listing link is subordinate rather than a third equal choice. Tradeoff: the catalogue comes later. It explains what the product does better, but foregrounds less of the asset breadth. Adapt: the decorative price ladder belongs to a selected asset or should have no numeric labels. As drawn it places TIBBIR's prices beside a mixed-token stack. Do not ship that as a universal strike scale. C — Asset atlas Adopt for consideration after an asset is chosen: one expansion reveals strikes, a dated result and two relevant destinations. The phone wraps six strikes into two rows and preserves both actions. Tradeoff: it brings unfamiliar strike terminology forward. It is denser and requires more reading than A as a first impression. The +15.78% is one observed completed TIBBIR 0.26 epoch (25 Sep–2 Oct), not an all-asset result or forecast. Always bind the date, strike and outcome unit to it. Do not preselect whichever strike had the largest gain. The diagram must not skip the deposit step or imply fees are paid merely by choosing a strike. A final step sequence would be asset -> strike -> deposit, with fee mechanics explained separately. Gyro adaptation Uses the catalogue pattern with Gyro's own navy/teal identity, small chain badges and broader asset categories. Examples: WBTC, wstETH, XAUt, SPYon, EURC, XSGD, NUTS and HYPE. No live status, current listing count or forecast was supplied. A production catalogue must derive availability from the correct site config and current contract/listing state; it must not import another subDAO at runtime. The first Gyro image invented a Solana symbol and clipped phone chain filters. A targeted edit removes the unsupported symbol and uses compact phone filter menus; the original incorrect board is not the review recommendation. Recommendation (not an approval) Start with A for discovery. Shorten its copy and keep B's clear distinction between providing liquidity and buying in the route labels. C is a candidate asset-detail view, not extra content to stack onto the first page. Do not average all three screens together. The owner chooses the direction before implementation. Acceptance questions for people, not models 1. After five seconds: what can you do on this site, and which asset would you open? 2. Can an options buyer find the correct route without first making a vault deposit? 3. Can a returning holder get directly to positions without repeating an intro? 4. Do people read the historical figure as a forecast? If so, the design fails. Future engineering boundaries Browse anonymously; connect only when necessary. Preserve direct asset/strike links. Returning-wallet positions may lead only after actual positions are known. Fees, wallet returns and whole-strike records remain distinct. Missing reads are not zero; loss records are not hidden. No annualized promotional leaderboard. Keep wallet actions in the existing app; no copied financial calculations in the discovery layer. Forks own their copied implementation, design and configuration. No changes to app.html/app.js, index.html, beta, worker APIs, fees or launch gates. Review delivery Both sites keep local copies of the gallery assets; no cross-subDAO image dependency. Generated desktop/phone layouts are not responsive implementation proof. Gallery validation covers complete file links, alt text, local ownership and current screen dimensions. Browser checks cover actual gallery layout and image loading.