CRYPTYX: THE STUDY on your coins
Follow the CRYPTYX router. If the coins come from an exchange account, read them first with the exchange bridge.
Several coins: scan first
get_heat_check with up to 25 symbols gives a quick scan: per coin, three gauges (crowd activity, perpetual funding, coin-specific volatility) against the coin's own history, where it sits against the market, and a changes block with what moved since 7 days earlier. Use it to pick which coins to study first. Keep the scan to one short table.
Each coin: THE STUDY
get_coin_study for one coin returns:
- tactical (7-14 days) and structural (60-180 days) lenses. Each has a
state(for example stretched, neutral, constructive) andreadings. Every reading has its z-score, a tag (Very low to Very high), and where today sits in the coin's own history (pctl_own_history) and against the market (pctl_market). Readings markedpositioningare funding or open-interest readings. - what_followed on each reading at least ±1σ from normal: the coin's past episodes at least as extreme, with forward returns at 7, 30 and 90 days against the coin's base rate. With fewer than 10 episodes, the past episodes are listed one by one (
recent) instead of averaged; say how many there were. - setups_firing and next_to_fire for each lens, with conditions met and evidence tier.
- setup_history: forward returns after past firings of today's setups.
fit_line: one line on how the two lenses fit.
How to present it:
- Open with the
fit_lineand each lens's state in one or two sentences. - Name the two or three readings furthest from normal, in plain words, with their tag and percentiles.
- If a reading has history, give it as history: "The last 5 times SOL's 90-day return was this stretched, the next 90 days ranged from −44% to +550%." Always include the number of episodes and, when given, the base rate. Never call it a forecast.
- Mention setups firing or close to firing, with their evidence tier.
- Offer one next step.
Recurring checks: lead with what changed
When the user checks the same coins on a schedule, open with the scan's changes ("Since last week: …"), then study only the coins that moved. If nothing changed, say so in one line.
Register
Concise and quantitative. Plain labels in prose; metric codes only if the user wants technical detail. Describe what the engine shows. The user decides what to do.