GEM Hunter
GEM HUNTER
Relative engine

Leader or laggard versus BTC — then resume.

Relative prints on a name that is leading or lagging BTC (and then resumes with volume). Not Lead, which is venue discovery. Own geometry. RR ≥ 2. Own Telegram, own paper book, own bot toggle.

1
Lane
vs BTC
2
RR floor
after fees
Wired
Bot
user toggle
None
Advice
paper tools only
Process

Versus BTC → displace → resume → geometry.

A weak alt in a weak tape is not a laggard trade. Relative needs the spread, then volume.

Spread vs BTC

Lead or lag versus BTC, not versus a sector story on Twitter.

Displacement

The spread actually moved. A flat relative line is not a card.

Resume with volume

Continuation of the relative move, confirmed. A dead bounce stays silent.

Own geometry

Stop beyond the relative swing. RR ≥ 2 after fees, or skip.

What this is

  • A relative-strength engine versus BTC.
  • A different question from Lead’s cross-venue median.
  • A paper book and Telegram lane of its own.
  • Wired to the CEX bot when you enable the toggle.

What this is not

  • Not Lead. Lead follows venues, not alts versus BTC.
  • Not a blended index you can buy as one ticket.
  • Not Radar’s relative score. Radar never prints a side.
  • Not financial advice. If the spread snaps back, the idea is gone.
FAQ

Relative engine, in plain language

Is Relative the same as Lead?

No. Lead asks which venue is discovering price. Relative asks whether this name is leading or lagging BTC.

Do you print a sector basket?

No. One name, one card. Never a blended index.

Does it read Radar’s relative board?

No. Radar may hint Relative to humans. evaluate() does not consume that board.

Are Relative cards financial advice?

No. Paper tickets, invalidation, and R multiples are tools. Leverage can liquidate you. Past paper results do not guarantee future results.

Run Relative on the live venue

Open cards, history, paper R, and the Relative bot toggle are membership surfaces.