< Swept the lows and reclaimed (1h)ORDIUSDT · historical base rate

Swept the lows and reclaimed (1h) on ORDIUSDT

The last completed one-hour candle swept prior lows and closed back above them: the "bullish" sweep and reclaim formation on the hourly.

What has happened on ORDIUSDT when it held

Historically, when Swept the lows and reclaimed (1h) on ORDIUSDT held (37 occurrences in the scanned window, 35 with a computable 24h horizon), the market reached +5% within 24h in 7 of 35 (20.0) and drew down 10%+ in 0 of 35 (0.0). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

WHAT FOLLOWED - ALL 37 MATCHES, FROM THE PER-SCAN SUMMARY

0 OF 37 (0.0%) REACHED ≥ +5% WITHIN 1H

METRIC MFE_1H · CHIPS RE-READ THE SUMMARY, NEVER RE-QUERY

🔒 COMPUTED FORWARD, NEVER A FILTER · DENOMINATOR 37 = MATCHES WITH A COMPLETE 1H HORIZON

OCCURRENCES PER DAY · UTC · SUM 37 - ALL 37, NOT THE PAGE

About 1.2 a day, on 20 of 31 days: spread through the record rather than one event.

FWD_RET_30M DISTRIBUTION · 37 PRESENT · 0 ABSENT

Forward 30-minute returns across 37 matches: 57% of them finished up.

Versus baseline

Historically, when any eligible ORDIUSDT minute in the window (baseline) held (39,181 occurrences in the scanned window, 37,857 with a computable 24h horizon), the market reached +5% within 24h in 7,047 of 37,857 (18.6) and drew down 10%+ in 177 of 37,857 (0.5). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

The full record

The same setup counted over every recorded day on ORDIUSDT (2026-05-15 to 2026-07-31), growing daily.

Historically, when Swept the lows and reclaimed (1h) on ORDIUSDT over the full record held (73 occurrences in the scanned window, 71 with a computable 24h horizon), the market reached +5% within 24h in 23 of 71 (32.4) and drew down 10%+ in 1 of 71 (1.4). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

WHAT FOLLOWED - ALL 73 MATCHES, FROM THE PER-SCAN SUMMARY

1 OF 73 (1.4%) REACHED ≥ +5% WITHIN 1H

METRIC MFE_1H · CHIPS RE-READ THE SUMMARY, NEVER RE-QUERY

🔒 COMPUTED FORWARD, NEVER A FILTER · DENOMINATOR 73 = MATCHES WITH A COMPLETE 1H HORIZON

OCCURRENCES PER DAY · UTC · SUM 73 - ALL 73, NOT THE PAGE

About 0.9 a day, on 40 of 78 days: spread through the record rather than one event.

FWD_RET_30M DISTRIBUTION · 73 PRESENT · 0 ABSENT

Forward 30-minute returns across 73 matches: 56% of them finished up.

Reproducibility key (q#cbf0a2e8)

grammar: research_query.v2
normalization: archive_normalization.v1
feature library: feature_defs.v1
dataset revision: 52a43a418a97fbe3a324f7c372fa4d53967163acaa0ed33c56b78ddd897331a4
query hash: cbf0a2e866fdf4979503573acfda295d30543f49730e1e27550cfef4c28faeb1
scanned window: 2026-07-01T00:00:00.000Z to 2026-07-31T00:00:00.000Z (UTC)

Same key, same bytes. This receipt reruns; it does not retell. When the record grows, the dataset revision changes and says so.

Re-run this over the API or MCP

This is the exact research_query.v2 definition behind the receipt. Send it to the key-authed research API (or the MCP research tool) and diff the bytes: a cached rerun is free.

{
  "schema_version": "research_query.v2",
  "normalization_version": "archive_normalization.v1",
  "feature_version": "feature_defs.v1",
  "target": "record_occurrences",
  "where": {
    "all": [
      [
        "feature.candle_sweep_reclaim_1h",
        "eq",
        "bullish"
      ],
      [
        "identity.symbol",
        "eq",
        "ordiusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-07-01T00:00:00.000Z",
          "2026-07-31T00:00:00.000Z"
        ]
      ]
    ]
  },
  "sort": [
    "times.anchor_time",
    "desc"
  ],
  "page": {
    "limit": 50,
    "cursor": null
  }
}

curl -s https://app.edgedepth.com/api/v1/research/query \
  -H 'authorization: Bearer $EDGEDEPTH_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"schema_version":"research_query.v2","normalization_version":"archive_normalization.v1","feature_version":"feature_defs.v1","target":"record_occurrences","where":{"all":[["feature.candle_sweep_reclaim_1h","eq","bullish"],["identity.symbol","eq","ordiusdt"],["times.anchor_time","between",["2026-07-01T00:00:00.000Z","2026-07-31T00:00:00.000Z"]]]},"sort":["times.anchor_time","desc"],"page":{"limit":50,"cursor":null}}'

How to read this

Counts ship with denominators: occurrences across the eligible symbol-buckets scanned. A rate is over the occurrences with a computable horizon (present), never the total.
Absent is absent. When a feature was not warm at a minute, that bucket leaves the denominator and is reported; it is never coerced to zero.
This selects a setup, never its outcome. The grammar forbids filtering on what followed (OUTCOME_IN_PREDICATE), so the distribution below is over every occurrence, not a survivorship-picked subset.

Occurrences are observed examples in a selected archive, not a guarantee. Outcomes are computed forward from each anchor and are descriptive, never a filter and never a prediction. Nothing here is trading advice.

Everything measured on ORDIUSDT right now: the ORDIUSDT research page