Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
fix(oracle-docs): rewrite the banned em-dashes in the docs copy and its source catalog
nirholas7cdd829c4b23
diff --git a/pages/oracle-docs.html b/pages/oracle-docs.htmlindex e982f1cda..ede0173ca 100644--- a/pages/oracle-docs.html+++ b/pages/oracle-docs.html@@ -420,8 +420,8 @@<p data-i18n="oracle_docs.concretely_the_platform_splits_into_three_co">Concretely, the platform splits into three cooperating parts:</p><div class="cards c3">- <div class="card"><div class="ic">Read path</div><h3 class="ch" data-i18n="oracle_docs.the_conviction_library">The conviction library</h3><p data-i18n-html="oracle_docs.a_pure_side_effect_free_scoring_function">A pure, side-effect-free scoring function (<code class="t">convict()</code>) plus a defensive data-assembly layer. Given a mint, it returns a score, tier, pillar breakdown, and reasons. No I/O during scoring — fully testable.</p></div>- <div class="card"><div class="ic">Run path</div><h3 class="ch" data-i18n="oracle_docs.the_worker_2">The worker</h3><p data-i18n-html="oracle_docs.a_long_lived_node_process_running_three">A long-lived Node process running three independent loops — <b>score</b> (keep verdicts warm), <b>agent</b> (act on armed watches), and <b>settle</b> (grade outcomes) — each self-scheduling so a slow pass never blocks a fast one.</p></div>+ <div class="card"><div class="ic">Read path</div><h3 class="ch" data-i18n="oracle_docs.the_conviction_library">The conviction library</h3><p data-i18n-html="oracle_docs.a_pure_side_effect_free_scoring_function">A pure, side-effect-free scoring function (<code class="t">convict()</code>) plus a defensive data-assembly layer. Given a mint, it returns a score, tier, pillar breakdown, and reasons. No I/O during scoring, so it is fully testable.</p></div>+ <div class="card"><div class="ic">Run path</div><h3 class="ch" data-i18n="oracle_docs.the_worker_2">The worker</h3><p data-i18n-html="oracle_docs.a_long_lived_node_process_running_three">A long-lived Node process running three independent loops: <b>score</b> (keep verdicts warm), <b>agent</b> (act on armed watches), and <b>settle</b> (grade outcomes), each self-scheduling so a slow pass never blocks a fast one.</p></div><div class="card"><div class="ic">Edge path</div><h3 class="ch" data-i18n="oracle_docs.the_api_ui">The API + UI</h3><p data-i18n="oracle_docs.24_endpoints_json_sse_serving_the_feed">~24 endpoints (JSON + SSE) serving the feed, coin detail, wallet intel, backtest, streams, and the agent-config surface. Cached at the CDN; rate-limited per IP.</p></div></div><div class="note tip">@@ -588,7 +588,7 @@ score = min(score, 45 if rugger_creator)<h2 data-i18n="oracle_docs.the_worker_3">The worker</h2><p class="lead-in" data-i18n="oracle_docs.a_single_long_lived_node_process_runs">A single long-lived Node process runs three independent, self-scheduling loops. They share nothing but the database, so a slow scoring pass never delays an agent acting, and a stuck confirmation never freezes scoring.</p><div class="cards c3">- <div class="card"><div class="ic">every ~15s · batch 20</div><h3 class="ch" data-i18n="oracle_docs.score_loop">Score loop</h3><p data-i18n="oracle_docs.finds_recent_launches_that_are_new_or">Finds recent launches that are new or stale (last scored >3 min ago), scores each — assemble → classify → fuse → persist — and appends history on material change. Keeps the cache warm.</p></div>+ <div class="card"><div class="ic">every ~15s · batch 20</div><h3 class="ch" data-i18n="oracle_docs.score_loop">Score loop</h3><p data-i18n="oracle_docs.finds_recent_launches_that_are_new_or">Finds recent launches that are new or stale (last scored >3 min ago), scores each (assemble → classify → fuse → persist) and appends history on material change. Keeps the cache warm.</p></div><div class="card"><div class="ic">every ~3s</div><h3 class="ch" data-i18n="oracle_docs.agent_loop">Agent loop</h3><p data-i18n="oracle_docs.for_each_armed_watch_evaluates_freshly_score">For each armed watch, evaluates freshly-scored coins against the agent's bar and budget, executes a buy when the gates pass, and fires alerts. Dedups so an agent never acts twice on one coin.</p></div><div class="card"><div class="ic">every ~60s · batch 100</div><h3 class="ch" data-i18n="oracle_docs.settle_loop">Settle loop</h3><p data-i18n="oracle_docs.finds_open_actions_whose_coin_now_has">Finds open actions whose coin now has a resolved outcome, grades each win/loss/flat, marks PnL to market, and closes the learning loop.</p></div></div>@@ -809,11 +809,11 @@ CI = [centre − margin, centre + margin]</pre><h2 data-i18n="oracle_docs.limits_failure_modes_2">Limits & failure modes</h2><p class="lead-in" data-i18n="oracle_docs.a_model_you_can_only_trust_when">A model you can only trust when it flatters you is useless. Here is what Oracle cannot do, where it can be wrong, and how it's hardened.</p><div class="cards c2">- <div class="card"><h3 class="ch" data-i18n="oracle_docs.it_is_a_probability_not_a_prophecy">It is a probability, not a prophecy</h3><p data-i18n="oracle_docs.a_high_score_is_the_weight_of">A high score is the weight of on-chain evidence, not a guarantee. pump.fun is adversarial and heavy-tailed — most launches fail, and even a calibrated edge loses often. Read the tier as odds, size accordingly, and never bet what you can't lose.</p></div>- <div class="card"><h3 class="ch" data-i18n="oracle_docs.garbage_in_on_a_young_coin">Garbage-in on a young coin</h3><p data-i18n="oracle_docs.the_first_seconds_of_a_launch_are">The first seconds of a launch are data-poor. Pedigree and momentum need wallets to show up before they say much; a brand-new coin leans on structure and a category prior. Scores sharpen as the footprint fills in — which is exactly why history and movers exist.</p></div>- <div class="card"><h3 class="ch" data-i18n="oracle_docs.adversarial_structure">Adversarial structure</h3><p data-i18n="oracle_docs.the_how_pillar_is_a_guardrail_against">The HOW pillar is a guardrail against known manipulation — bundling, sniping, and coordinated holder concentration — but launderers iterate. New evasion patterns are caught by the outcome loop (they rug, reputation updates) before they're caught by a rule. The defense is the closed loop, not any single check.</p></div>+ <div class="card"><h3 class="ch" data-i18n="oracle_docs.it_is_a_probability_not_a_prophecy">It is a probability, not a prophecy</h3><p data-i18n="oracle_docs.a_high_score_is_the_weight_of">A high score is the weight of on-chain evidence, not a guarantee. pump.fun is adversarial and heavy-tailed: most launches fail, and even a calibrated edge loses often. Read the tier as odds, size accordingly, and never bet what you can't lose.</p></div>+ <div class="card"><h3 class="ch" data-i18n="oracle_docs.garbage_in_on_a_young_coin">Garbage-in on a young coin</h3><p data-i18n="oracle_docs.the_first_seconds_of_a_launch_are">The first seconds of a launch are data-poor. Pedigree and momentum need wallets to show up before they say much; a brand-new coin leans on structure and a category prior. Scores sharpen as the footprint fills in, which is exactly why history and movers exist.</p></div>+ <div class="card"><h3 class="ch" data-i18n="oracle_docs.adversarial_structure">Adversarial structure</h3><p data-i18n="oracle_docs.the_how_pillar_is_a_guardrail_against">The HOW pillar is a guardrail against known manipulation (bundling, sniping, and coordinated holder concentration), but launderers iterate. New evasion patterns are caught by the outcome loop (they rug, reputation updates) before they're caught by a rule. The defense is the closed loop, not any single check.</p></div><div class="card"><h3 class="ch" data-i18n="oracle_docs.narrative_lag_model_error">Narrative lag & model error</h3><p data-i18n="oracle_docs.the_what_pillar_depends_on_a_language">The WHAT pillar depends on a language model and a news feed; both can misread a story or miss a fast-breaking one. It's the lightest-weighted pillar for exactly this reason, and it degrades to a deterministic classifier rather than failing.</p></div>- <div class="card"><h3 class="ch" data-i18n="oracle_docs.outcome_latency">Outcome latency</h3><p data-i18n="oracle_docs.win_loss_isn_t_known_until_a">Win/loss isn't known until a coin resolves, so the backtest always trails the present. Recent windows are thin and their confidence bands are wide — and the page shows the width rather than hiding it.</p></div>+ <div class="card"><h3 class="ch" data-i18n="oracle_docs.outcome_latency">Outcome latency</h3><p data-i18n="oracle_docs.win_loss_isn_t_known_until_a">Win/loss isn't known until a coin resolves, so the backtest always trails the present. Recent windows are thin and their confidence bands are wide, and the page shows the width rather than hiding it.</p></div><div class="card"><h3 class="ch">Two features are missing, not zero</h3><p>The fitter reports every feature it drops for carrying no information, and on the current fit that is <code class="t">fresh_wallet_ratio</code> and <code class="t">bubblemap_connectivity</code>: both are null on effectively every training row, because nothing populates wallet metadata and the funder graph needs a Helius key that is not set. A third, <code class="t">coordination_score</code>, collapses to <code class="t">bundle_score × 0.6</code> once the null term drops out, which is why the live intel weights list the two as identical. The list is measured on each fit rather than hardcoded, so wiring the funder graph returns those features on the next refit with no code change. Until then, read the HOW pillar as bundle-and-organic evidence, not as a funder-cluster analysis.</p></div><div class="card"><h3 class="ch">Weights are fitted, and drift is real</h3><p>Since 2026-08-09 every bucket weight is fitted from labeled outcomes and validated on a temporal holdout. The flip side: a fitted model is only as current as its last refit, the launch meta drifts, and the training window always lags the newest evasion pattern by however long outcomes take to resolve. The refit script exists to be rerun.</p></div></div>@@ -830,11 +830,11 @@ CI = [centre − margin, centre + margin]</pre><p class="lead-in" data-i18n="oracle_docs.the_architecture_pure_scoring_over_a_coverag">The architecture — pure scoring over a coverage brain, behind a cached API, with a closed outcome loop — was chosen because it extends along several axes at once without a rewrite.</p><div class="cards c2"><div class="card"><div class="ic">Calibration</div><h3 class="ch" data-i18n="oracle_docs.interactions_over_the_fitted_buckets">Interactions over the fitted buckets</h3><p data-i18n-html="oracle_docs.learned_weights_and_a_calibrated_probability">Learned weights and a calibrated probability shipped in v2; the six-hourly refit behind a promotion gate shipped in v3. The next lever is the additive assumption itself: interaction terms or shallow trees over the same buckets, since the strongest observed patterns (holder concentration crossed with buyer count) are plausibly interactive and a sum of one-hot weights cannot express them.</p></div>- <div class="card"><div class="ic">Coverage</div><h3 class="ch" data-i18n="oracle_docs.more_wallets_more_density">More wallets, more density</h3><p data-i18n="oracle_docs.every_new_wallet_judged_and_every_new">Every new wallet judged and every new launch resolved sharpens the WHO pillar and tightens the bands. The data flywheel is the moat — coverage compounds into calibration.</p></div>- <div class="card"><div class="ic">Surface</div><h3 class="ch" data-i18n="oracle_docs.more_chains_more_venues">More chains, more venues</h3><p data-i18n="oracle_docs.the_pillars_are_venue_agnostic_who_how">The pillars are venue-agnostic — who/how/what/move generalize to any launch venue with on-chain footprints. The brain abstraction is the seam where a new chain plugs in.</p></div>+ <div class="card"><div class="ic">Coverage</div><h3 class="ch" data-i18n="oracle_docs.more_wallets_more_density">More wallets, more density</h3><p data-i18n="oracle_docs.every_new_wallet_judged_and_every_new">Every new wallet judged and every new launch resolved sharpens the WHO pillar and tightens the bands. The data flywheel is the moat: coverage compounds into calibration.</p></div>+ <div class="card"><div class="ic">Surface</div><h3 class="ch" data-i18n="oracle_docs.more_chains_more_venues">More chains, more venues</h3><p data-i18n="oracle_docs.the_pillars_are_venue_agnostic_who_how">The pillars are venue-agnostic: who/how/what/move generalize to any launch venue with on-chain footprints. The brain abstraction is the seam where a new chain plugs in.</p></div><div class="card"><div class="ic">Speed</div><h3 class="ch" data-i18n="oracle_docs.push_not_poll">Push, not poll</h3><p data-i18n="oracle_docs.streams_poll_the_database_today_for_serverle">Streams poll the database today for serverless simplicity. Event-driven push (LISTEN/NOTIFY or a log tail) cuts verdict-to-screen latency toward the block, which on pump.fun is the whole game.</p></div><div class="card"><div class="ic">Inputs</div><h3 class="ch" data-i18n="oracle_docs.richer_signals">Richer signals</h3><p data-i18n="oracle_docs.deeper_social_ingestion_holder_graph_evoluti">Deeper social ingestion, holder-graph evolution over time, cross-coin creator/funder linkage, and order-flow microstructure are all additive pillars or sub-signals under the same fusion contract.</p></div>- <div class="card"><div class="ic">Ecosystem</div><h3 class="ch" data-i18n="oracle_docs.an_agent_native_signal_layer">An agent-native signal layer</h3><p data-i18n-html="oracle_docs.the_machine_ready_endpoint_and_the_action">The machine-ready <code class="t">/signal</code> endpoint and the action loop make Oracle a primitive other agents build on — discoverable, payable, and composable across the three.ws agent economy and MCP.</p></div>+ <div class="card"><div class="ic">Ecosystem</div><h3 class="ch" data-i18n="oracle_docs.an_agent_native_signal_layer">An agent-native signal layer</h3><p data-i18n-html="oracle_docs.the_machine_ready_endpoint_and_the_action">The machine-ready <code class="t">/signal</code> endpoint and the action loop make Oracle a primitive other agents build on: discoverable, payable, and composable across the three.ws agent economy and MCP.</p></div></div></section>diff --git a/public/locales/en.json b/public/locales/en.jsonindex 76f967c24..28596dfde 100644--- a/public/locales/en.json+++ b/public/locales/en.json@@ -15430,11 +15430,11 @@"a_conviction_score_is_a_probabilistic_claim": "A conviction score is a probabilistic claim, and a probabilistic claim is worthless unless it's checked against reality. Oracle joins every verdict to its ground-truth outcome and publishes the result on the page — including when the edge is thin. This is the part that separates a model from a vibe.","a_dynamic_1200_630_opengraph_conviction_card": "A dynamic 1200×630 OpenGraph conviction card (SVG) for sharing a coin.","a_hard_ceiling_on_the_final_score": "A hard ceiling on the final score, set by a severe structural or pedigree red flag, applied before clamping.",- "a_high_score_is_the_weight_of": "A high score is the weight of on-chain evidence, not a guarantee. pump.fun is adversarial and heavy-tailed — most launches fail, and even a calibrated edge loses often. Read the tier as odds, size accordingly, and never bet what you can't lose.",- "a_long_lived_node_process_running_three": "A long-lived Node process running three independent loops — <b>score</b> (keep verdicts warm), <b>agent</b> (act on armed watches), and <b>settle</b> (grade outcomes) — each self-scheduling so a slow pass never blocks a fast one.",+ "a_high_score_is_the_weight_of": "A high score is the weight of on-chain evidence, not a guarantee. pump.fun is adversarial and heavy-tailed: most launches fail, and even a calibrated edge loses often. Read the tier as odds, size accordingly, and never bet what you can't lose.",+ "a_long_lived_node_process_running_three": "A long-lived Node process running three independent loops: <b>score</b> (keep verdicts warm), <b>agent</b> (act on armed watches), and <b>settle</b> (grade outcomes), each self-scheduling so a slow pass never blocks a fast one.","a_model_you_can_only_trust_when": "A model you can only trust when it flatters you is useless. Here is what Oracle cannot do, where it can be wrong, and how it's hardened.","a_pump_fun_coin_that_completed_its": "A pump.fun coin that completed its bonding curve — the canonical success event.",- "a_pure_side_effect_free_scoring_function": "A pure, side-effect-free scoring function (<code class=\"t\">convict()</code>) plus a defensive data-assembly layer. Given a mint, it returns a score, tier, pillar breakdown, and reasons. No I/O during scoring — fully testable.",+ "a_pure_side_effect_free_scoring_function": "A pure, side-effect-free scoring function (<code class=\"t\">convict()</code>) plus a defensive data-assembly layer. Given a mint, it returns a score, tier, pillar breakdown, and reasons. No I/O during scoring, so it is fully testable.","a_scored_coin_is_a_win_if": "A scored coin is a <b>win</b> if it graduated, or reached a ≥2× ATH multiple <i>without rugging</i>; a <b>loss</b> if it rugged or languished below 1.2×; <b>flat</b> in between. The \"without rugging\" clause matters: bundled launches routinely spike 2× from first sight before collapsing, and counting those wicks as wins would let pump-and-dumps inflate the very number that's supposed to expose them. Only resolved coins count toward a win rate — open positions are excluded, so the number can't be inflated by undecided bets.","a_single_long_lived_node_process_runs": "A single long-lived Node process runs three independent, self-scheduling loops. They share nothing but the database, so a slow scoring pass never delays an agent acting, and a stuck confirmation never freezes scoring.","a_single_wallet_s_profile_recent_coins": "A single wallet's profile + recent coins, or the wallet leaderboard.",@@ -15538,7 +15538,7 @@"endpoint_3": "Endpoint","every_action_an_agent_takes_simulated_or": "Every action an agent takes — simulated or live — is graded against ground truth and lands in its permanent win-rate ledger. This is what makes an agent's track record verifiable instead of asserted.","every_field_here_is_also_available_programma": "Every field here is also available programmatically from <code class=\"t\">GET /api/oracle/coin?mint=…</code> — see the <a class=\"inl\" href=\"#api\">API reference</a>.",- "every_new_wallet_judged_and_every_new": "Every new wallet judged and every new launch resolved sharpens the WHO pillar and tightens the bands. The data flywheel is the moat — coverage compounds into calibration.",+ "every_new_wallet_judged_and_every_new": "Every new wallet judged and every new launch resolved sharpens the WHO pillar and tightens the bands. The data flywheel is the moat: coverage compounds into calibration.","every_one_of_those_facts_is_on": "Every one of those facts is on-chain or one inference away from it. The bottleneck has never been availability — it is <b>assembly and speed</b>. No human watches every wallet across every launch and fuses it into a decision in seconds. A machine can.","every_scored_coin_as_a_glowing_sphere": "Every scored coin as a glowing sphere in a force-directed, category-clustered 3D field; size and color encode conviction and tier.","every_section_opens_in_plain_english_what": "Every section opens in plain English: what it is, why it exists, and how to use it. If you only read the prose, you will understand the whole system and never see a formula you didn't ask for.",@@ -15548,7 +15548,7 @@"explicit_bundle_risk_flag": "Explicit bundle risk flag","feeds": "Feeds","finds_open_actions_whose_coin_now_has": "Finds open actions whose coin now has a resolved outcome, grades each win/loss/flat, marks PnL to market, and closes the learning loop.",- "finds_recent_launches_that_are_new_or": "Finds recent launches that are new or stale (last scored >3 min ago), scores each — assemble → classify → fuse → persist — and appends history on material change. Keeps the cache warm.",+ "finds_recent_launches_that_are_new_or": "Finds recent launches that are new or stale (last scored >3 min ago), scores each (assemble → classify → fuse → persist) and appends history on material change. Keeps the cache warm.","five_brain_tables_feed_every_score_oracle": "Five brain tables feed every score. Oracle queries each one <b>defensively</b> — a missing or younger table degrades the affected pillar gracefully rather than failing the whole verdict.","flagged_wallet_present_rugger_dumper": "Flagged wallet present (rugger/dumper)","flat_everything_in_between": "<b>Flat</b> — everything in between.",@@ -15735,7 +15735,7 @@"the_edge": "<b>The edge</b>","the_fair_launch_guardrail_also_imposes_hard": "— the fair-launch guardrail; also imposes hard ceilings.","the_final_integer_maps_to_one_of": "The final integer maps to one of five tiers. Tiers are how humans skim the feed and how agents set a bar.",- "the_first_seconds_of_a_launch_are": "The first seconds of a launch are data-poor. Pedigree and momentum need wallets to show up before they say much; a brand-new coin leans on structure and a category prior. Scores sharpen as the footprint fills in — which is exactly why history and movers exist.",+ "the_first_seconds_of_a_launch_are": "The first seconds of a launch are data-poor. Pedigree and momentum need wallets to show up before they say much; a brand-new coin leans on structure and a category prior. Scores sharpen as the footprint fills in, which is exactly why history and movers exist.","the_formal_view_for_readers_who_want": "The formal view, for readers who want the model stated as a model.","the_four_pillar_bars_who_how_what": "<b>The four pillar bars</b> — WHO / HOW / WHAT / MOVE — are the sub-scores from the section above. The big number is their capped, weighted fusion.","the_four_pillar_scores_collapse_into_one": "The four pillar scores collapse into one number by a weighted average — then the structural and pedigree caps clamp it down, it rounds, and it lands in a tier.",@@ -15750,11 +15750,11 @@"the_live_oracle_is_eight_views_over": "The live Oracle is eight views over one engine. Every state — loading, empty, error, populated — is designed; the empty states below are the real product telling you what's coming, not bugs.","the_live_surface_every_launch_in_the": "<b>The live surface.</b> Every launch in the last 12 hours, scored and ranked, with a live conviction-breadth bar and per-narrative averages. <a class=\"inl\" href=\"/oracle\">three.ws/oracle</a>","the_lowest_cap_triggered_wins_this_is": "The lowest cap triggered wins. This is the formal statement of \"structure is a veto\": a launch with a serious structural defect is ceiling-limited <i>before</i> the weighted average is taken, so no amount of pedigree or narrative lifts it into a high tier.",- "the_machine_ready_endpoint_and_the_action": "The machine-ready <code class=\"t\">/signal</code> endpoint and the action loop make Oracle a primitive other agents build on — discoverable, payable, and composable across the three.ws agent economy and MCP.",+ "the_machine_ready_endpoint_and_the_action": "The machine-ready <code class=\"t\">/signal</code> endpoint and the action loop make Oracle a primitive other agents build on: discoverable, payable, and composable across the three.ws agent economy and MCP.","the_one_sentence_version": "The one-sentence version","the_pedigree_graph_made_browsable_every_wall": "<b>The pedigree graph, made browsable.</b> Every wallet Oracle has judged, ranked by track record — early-buy win rate against dump/rug behavior. This is the raw material the WHO pillar reads. <a class=\"inl\" href=\"/oracle\">Top wallets tab</a>","the_pedigree_leaderboard_every_judged_wallet": "The pedigree leaderboard — every judged wallet ranked by track record.",- "the_pillars_are_venue_agnostic_who_how": "The pillars are venue-agnostic — who/how/what/move generalize to any launch venue with on-chain footprints. The brain abstraction is the seam where a new chain plugs in.",+ "the_pillars_are_venue_agnostic_who_how": "The pillars are venue-agnostic: who/how/what/move generalize to any launch venue with on-chain footprints. The brain abstraction is the seam where a new chain plugs in.","the_problem_asymmetric_information_at_the_sp": "The problem: asymmetric information at the speed of a block","the_product_is_keyboard_driven_focuses_searc": "The product is keyboard-driven (<kbd>/</kbd> focuses search, number keys jump tabs, arrows move between them), fully responsive, and built on a monochrome cool-gray palette where lightness encodes strength — brighter is stronger conviction.","the_proven_wins_gallery_ordered_by_ath": "The proven-wins gallery, ordered by ATH multiple, with a summary.",@@ -15819,7 +15819,7 @@"wilson_interval": "<b>Wilson interval</b>","wilson_interval_the_95_score_interval_on": "<b>Wilson interval:</b> the 95% score interval on each tier/bin win rate (derivation in the evidence deep-dive), correct for small <code class=\"t\">n</code> and bounded to [0,1].","win_loss_flat": "<b>Win / loss / flat</b>",- "win_loss_isn_t_known_until_a": "Win/loss isn't known until a coin resolves, so the backtest always trails the present. Recent windows are thin and their confidence bands are wide — and the page shows the width rather than hiding it.",+ "win_loss_isn_t_known_until_a": "Win/loss isn't known until a coin resolves, so the backtest always trails the present. Recent windows are thin and their confidence bands are wide, and the page shows the width rather than hiding it.","win_rate_by_tier_with_honest_error": "Win rate by tier, with honest error bars","win_rate_by_tier_with_wilson_cis": "Win rate by tier with Wilson CIs, calibration ladder, Brier, and the edge summary. Filters: <code>period, tier, network</code>.","win_the_coin_graduated_or_its_peak": "<b>Win</b> — the coin graduated, or its peak multiple reached ≥2× on a coin that didn't rug and isn't marked below half entry.",