# LarGrr — Product as a System (text diagram)

> Concept review for Stefan + Felix · 2026-06-02
> Brand: **LarGrr** (largrr.com) — *reclaim big* · SF big-guy nightlife.
> Companion visual: `largrr-system-map.html`

```
LarGrr  ·  reclaim big  ·  SF big-guy nightlife
"what's worth leaving the house for tonight" — one fresh, glanceable place,
built by someone the scene already trusts.   Wedge = FRESHNESS + BELONGING (not features)
│
├─ CORE LOOP   (the spine — must feel effortless)
│     Open → Tonight (relevant to me) → Tap event → who/where/when + real photos
│     → Decide → GO / Save / Share
│
├─ THREE LENSES   (one dataset, three views)
│     • Tonight    — default, glanceable  (the load-collapse)
│     • This Week  — calendar / list
│     • Map        — SoMa + Castro clusters
│
├─ ★ FRESHNESS ENGINE   (the actual product — won or lost here, NOT the feed UI)
│     INGEST  ─────────────→  RECONCILE  ─────────→  canonical fresh "tonight"
│     • scrape venue IG/sites/Eventbrite          • dedup
│     • Felix-seeded events                        • conflict-resolve
│     • venue self-post (post-once-fan-out)        • verify / curate
│     • gig-worker self-post                         (Felix + you = trusted curator)
│     • user submit
│
├─ USER TYPES
│     • Viewers      browse · "going" · follow venues/DJs/dancers · save · share · submit · photos
│     • Venues       claim page · post-once-fan-out · see who's coming
│     • Gig workers  profile · post themselves to events        (FELIX = the prototype)
│
├─ COMMUNITY + PHOTO   (mission-critical)
│     • Consent-first by construction: attest rights · tag-approval · 1-tap untag/takedown
│       · no bystander exposure by default
│     • Felix archive = quality bar + seed
│     • Reviews of VENUES & EVENTS — never people
│
├─ ◌ MONEY   (designed in, switched OFF in v1 → runs under FELIX'S ENTITY when on)
│     • Featured placement   • Venue subscription   • Photo sales (Felix model)   • Gig booking
│
├─ ✕ REFUSED — FOREVER   (L3 mission guardrails, baked in now while it's cheap)
│     • no hot-or-not        • no body ranking / desirability scoring
│     • no filters that sort people out        • no paywalled safety tools
│
└─ BUILT TO EXPAND
      • city-scoped from day one
      • franchise unit = "local trusted photographer + their scene"  (the Felix model, repeatable)
      • maps onto the Aurochs platform's per-tenant isolation


TWO SURFACES  /  PHASING
  Phase 0   Resource site (static, aurochs-ssg) ......... ~2 weeks    brand + SEO/GEO seed + Felix archive
  Phase 1   MVP vertical (dynamic, in-platform) ......... early July  Tonight feed + freshness engine + accounts + consent photos · MONEY OFF
  Phase 2   Activate revenue ......................................... featured + subscription, then Felix-model photo sales
  Phase 3   Expand ................................................... 2nd scene/city via the franchise unit
```

## Why it's shaped this way (the load-bearing calls)
- **Freshness is the moat, and the engine is the real build.** Every incumbent (venue sites, Instagram, Facebook Events) loses to staleness; if the aggregator also rots, it has negative value. The ingest→reconcile machine, not the feed UI, is where this is won.
- **Belonging lives in the imagery.** The first 50ms decides whether a big/older/diverse guy thinks "this is for me." Felix's 15-year documentary archive is that answer, pre-built.
- **Guardrails baked in now.** Money is deferred but "shaped in for later" — and later, under revenue pressure, is exactly when a body-confidence product drifts toward objectification. The "refused forever" list is locked now, while it's free.
- **Warm start, not cold start.** Felix is supply (venues, events, a photo archive) on day one, which is why marketplace-adjacent features are even feasible this early.