Old "Trove" host-experience vision — archive + gap map
A review of the archived consumer Trove page (app.triunalabs.com/trove/#hosts, "Turn your sale
into a can't-miss event") against the current seller-ops-first plan. This doc preserves that
vision so it isn't lost, and maps each feature to where it lives now: ✅ covered · 🟡 partial /
consciously deferred · ❌ under-captured (now parked Backlog, see decision D42).
Source: a 49 MB saved snapshot of the deployed
#hostsroute (C:\TriunaLabs\Research\Trove _ Real World Treasure.mhtml). It's the host side of a two-sided "real-world treasure" marketplace (Hosts + Hunters), heavy on event-marketing and gamification.
What the old page pitched
A sale is a live event. Hosts get a public ● Live sale page + a dashboard, schedule item
reveals to build hype, grow a following, and earn gamified reputation — and every buyer interaction
boosts the sale's reach.
- Live sale event page + host dashboard — Overview / Items / Teasers & Drops / Reservations / Followers / Analytics / Messages; a "Sale Snapshot" (Views / Followers / Reservations / Items Sold with deltas).
- Teasers & timed Drops — scheduled item reveals (Teaser vs Drop, with times + Saves).
- Engagement → visibility loop — Follows / Saves / Comments / Check-Ins / Shares / Reservations each add reach ("More engagement = higher visibility").
- Built for every kind of host — Garage / Estate / Flea Market / Tag-Sale / Pop-up.
- Host Cards + CRED — Community Magnet · Trusted Curator · Legendary Host · Repeat Seller; CRED points, trust ratings, attendance/sales boosts.
- Two-sided — nav for Hunters · Hunt Packs · Cards · Community alongside Hosts.
Gap map
Old #hosts feature |
Status | Where it lives now |
|---|---|---|
| Public sale pages + buyer-safe QR | ✅ covered | P5/P6 sale pages; QR opaque-ID requirement |
| AI descriptions & value estimates | ✅ covered | the scan→appraise pipeline (P1–P4) |
| Buyer discovery (home/marketplace/map/search) | ✅ covered | Trove Go (buyer) requirement |
| Followers / saves / watches / wanted / alerts | ✅ covered | marketplace/buyer data layer (P6) |
| Token economy (earned via submissions/confirmations/check-ins) | ✅ covered | token_ledger requirement |
| Check-ins | ✅ covered | mobile owns check-ins; tokens via check-ins |
| Timed discount phases (markdown pricing) | ✅ covered | discount_phases / calculateSaleDiscountState |
| Buyer "treasure cards" / full gamified Trove Go | 🟡 deferred | explicitly later-phase, not current scope |
| Host event dashboard (Sale Snapshot, Reservations, Messages) | ❌ under-captured | WI-087 |
| Teasers & timed item Drops (reveals — not discount phases) | ❌ under-captured | WI-088 |
| Engagement → visibility growth loop | ❌ under-captured | WI-089 |
| First-class casual host segments (garage/flea/tag/pop-up) | ❌ under-captured | WI-090 |
| Host↔buyer messaging + reservations | ❌ under-captured | WI-091 |
| Host-side gamified Host Cards + CRED + boosts | ❌ under-captured | WI-092 |
Reading
- Much of the page is an intentional pivot, not an oversight. The plan deliberately leads with seller operations and scopes the consumer gamification (treasure cards, the "full gamified Trove Go") as later-phase. The genuinely untracked slice was the host event-marketing / virality layer above (now WI-087–092), captured additive-only — no reshuffle of committed waves (D42).
- Product boundary (reinforced by the lead-gen research, below): TroveSnap = seller OS (sale pages, partner proof, exports) → host event pages (WI-087) belong here. Trove Go = buyer discovery + gamification → the engagement loop (WI-089) and Host Cards/CRED (WI-092) attach to the later-phase Trove Go. One canonical platform underneath (identity, QR/deep-links, public-safe projections, tokens, consent).
- Two senses of "Host Card" — don't conflate them. The old page's Host Card is a gamified reputation card (CRED, leaderboard-style: Legendary Host, etc.) → WI-092. The lead-gen research's "Host Card" is a shareable company/sale card (marketing/referral artifact) → part of the GCMD card taxonomy below. Both are valid; they're different objects.
Related
- Estate-seller lead-generation research — the B2B/trust angle on community & cards: a GCMD card taxonomy (Treasure / Memory / Provenance / Host / Partner-Proof / Handoff / Legacy), realtor referral flavor, and the TroveSnap↔Trove Go product-boundary recommendation that this doc's "Reading" section follows.
- Estate-seller pain points · Web enhancements (the deliberate gaps: contracts, staffing/SOPs, lead-gen, post-sale).
- Decision D42 (this capture) in the decision log.