Live condition · historical base rate

Order book heavily bid-sided

The order book has averaged at least half of its depth on the bid side over the sampling window.

What is book imbalance?

Firing now (provisional, current bucket)

The live read is not yet enabled. This surface reports the historical base rates below; the firing-now list turns on when the live evaluator is connected.

What has happened when it held

Historically, when Order book heavily bid-sided held (462,444 occurrences in the scanned window, 424,762 with a computable 24h horizon), the market reached +5% within 24h in 121,563 of 424,762 (28.6) and drew down 10%+ in 25,717 of 424,762 (6.1). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

WHAT FOLLOWED · ALL 462,444 MATCHES

376,220 of 439,037 (85.7%) reached +0% or more within 1 hour · smallest move size with matches, picked for you

Pick a window and a move size: how often did a move at least that big follow?

WINDOWMOVE SIZE

🔒 Measured after every match, never by keeping winners. 439,037 of the matches have a complete 1 hour forward; the other 23,407 are too recent to know.

What are MFE and MAE?

Why 7 days can show fewer than 1 hour: a match too recent for a complete 7 days is left out of that count entirely, even if it already reached the level within 1 hour. The two counts cover different sets of matches.

When they happened - one bar per UTC day, all 462,444 matches
1578207891MATCHES PER UTC DAY · MAX 15782 ON 2026-09-161552515193153601504915056153861536015311153251537214816149401541415477155561563115585151391515915477157661577215733157041504215269157341575515782157391708-2408-3109-0709-142026-08-19 TO 2026-09-18 · 31 UTC DAYS · ZERO DAYS KEEP THEIR SLOT

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

Where the next 30 minutes landed - 413,789 measured, 48,655 too recent
≥ +0: 169110 OF 41378915182211576454091905842189627953207635605466223225464224438552136065087141183727112≤−100−50−30−20−15−10−5−2−1−0.5−0.2−0.1<00++0.1+0.2+0.5+1+2+5+10+15+20+30+50≥+400

Forward 30-minute returns across 413,789 matches: close to an even split, which is what a coin flip looks like.

How to read a distribution
Upside reached · 24hUpside reached (MFE, 24h)The most price moved up within 24h of each occurrence: a high-water mark, never a close. 424,762 with a complete 24h.
Drawdown · 24hDrawdown (MAE, 24h)The worst price moved against within 24h of each occurrence: the deepest point, never the close. 424,762 with a complete 24h.

Versus baseline

Historically, when any eligible minute in the window (baseline) held (22,983,802 occurrences in the scanned window, 20,112,238 with a computable 24h horizon), the market reached +5% within 24h in 5,822,070 of 20,112,238 (28.9) and drew down 10%+ in 1,220,618 of 20,112,238 (6.1). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

By market

Markets where this condition occurred often enough in the window to carry its own statistically meaningful receipt:

Check our work: the key that re-runs this exact count (q#0aa73797)
grammar
research_query.v2
normalization
archive_normalization.v1
feature library
feature_defs.v1
dataset revision
8904ef0442c6f623ec772df2b59d7baf1e49aaa808b5b11ac31546605549e3bb
query hash
0aa73797b9130a61c856e6e00ebef86f47e80348e406847e4b3d7dd9f28e1705
scanned window
2026-08-19T00:00:00.000Z to 2026-09-18T00: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 yourself, over the API or from an AI agent

This is the exact search definition behind the receipt. Send it to the key-authed research API (or the MCP research tool) and compare 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.book_imbalance",
        "gte",
        0.5
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-08-19T00:00:00.000Z",
          "2026-09-18T00: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.book_imbalance","gte",0.5],["times.anchor_time","between",["2026-08-19T00:00:00.000Z","2026-09-18T00: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.