Player standbyPlay any artist upload to keep listening while you browse.
0:000:00
Sign In|Sign Up
Integrity Model

Transparent feed logic, adapted for HYPE.

This page brings the strongest Rift-style best practices into the music product: visible heuristics, public aggregate reporting, versioned feed logic, and clear trust commitments without pretending hidden ranking is a feature.

Open JSON snapshotLaunch readiness
1.1.0Feed heuristics version
2Live shows now
3Listeners live now
5Show hype events
7Profile hype events
Best Practices Applied

What transferred well from the civic-platform playbook.

Explainability by default

Feed logic is now described in plain language on show surfaces rather than staying hidden in sort order or operator intuition.

Versioned heuristics

The current feed model is labeled with a public heuristics version so ranking changes can be documented instead of quietly drifting.

Public aggregate reporting

The app now exposes an auditable aggregate snapshot route so growth and trust metrics are inspectable in a machine-readable form.

Heuristics Ledger

Public rules that currently affect show visibility.

LIVE-001

Live Priority

Shows that are live now receive the strongest visibility boost in the main feed.

Live broadcasts should surface ahead of scheduled or archived shows when other factors are similar.

TIME-001

Freshness Window

Scheduled shows closer to their start time receive a stronger freshness lift than distant events.

Shows happening soon rise above far-future listings, and recent archives stay visible briefly before fading.

HYPE-001

Bounded Momentum

Hype count increases feed momentum, but cannot override live status or basic freshness rules on its own.

A heavily hyped show can climb, but it does not permanently dominate the feed.

SAFE-001

Archive De-emphasis

Ended and canceled shows are de-emphasized unless they are still fresh enough to matter as recent context.

The feed stays oriented toward what can be watched or acted on now.

TRUST-001

Visible Explanations

Feed ranking rules and aggregate platform metrics are surfaced publicly rather than kept as hidden operator logic.

Users can see why a show is surfaced and inspect the current heuristics version.

GOV-001

Versioned Changes

Heuristic changes should be versioned and disclosed instead of silently drifting in production.

Teams can compare behavior across versions and explain when ranking rules change.

Why This Is Surfaced

Example explanation for the current top-ranked show.

CHI Riverline Live

Heuristics version 1.1.0

StatusLive now
FreshnessBroadcast is active, so it receives the strongest freshness lift.
Momentum61 hype signals give this show a strong momentum boost.

Plain-language breakdown

  • Status rule: Live now.
  • Broadcast is active, so it receives the strongest freshness lift.
  • 61 hype signals give this show a strong momentum boost.
  • Context includes Chicago / Lakefront Frequency / South Loop Signal.
Transparency Snapshot

Current aggregate platform view.

This demo exposes a current snapshot. A production-grade version should publish delayed, thresholded reports with retention and anonymity rules layered in.

5Total shows
2Upcoming shows
1Archived shows
3Events held
10Total profiles
2Artists
2Promoters
2Venues
4Listeners
3Listeners live now
961Tickets sold
52Songs uploaded
4Venue requests
2Pending requests
2Booked requests
3/13/2026, 8:19:21 PMSnapshot generated
Operating Commitments
  • Explainability is treated as a product feature, not a buried policy note.
  • Heuristic changes should be versioned and disclosed rather than silently shipped.
  • Aggregate transparency matters more than hidden growth loops.
  • Behavioral-profile targeting is out of scope for this product direction.