Hypotheses · overlay · SYS-wide-trip-beaten-under-five
System: Wide trip last time, beaten 5 lengths or less
published system (live from 2026-10-13); from IQ140a-wide-trip-with-figures [broad]
Part of the thread “IQ140a: wide trip with figures” 21 hypotheses
- Proposed
- Designed
- Discovery
- Promising
- Falsification
- Frozen
- Vault
- Provisional
- Shadow
- Validated
- Live
- Source
- Imported from the published systems
- Made by
- import
- Created
- 15 Oct, 23:10
- Tests logged
- 0
Mechanism and rationale
A horse forced wide covers extra ground; if it still finished close up, the bare result undersells it. Unlike the obvious hard-luck stories, the market does not seem to price this in. Remarks only go back twelve months, so the record is short.
The rule
last_raced_wide = 1 AND last_position > 1 AND last_beaten_lengths <= 5 AND last_slow_start = 0 AND NOT coalesce(last_run_style IN ('midfield', 'held_up') AND last_race_tilt >= 0.2 AND (last_position - 1.0) / max(last_field_size - 1, 1) <= 0.4, 0)Reads: last_raced_wide, last_position, last_beaten_lengths, last_slow_start, last_run_style, last_race_tilt, last_field_size
Pre-registration
- Spec hash (sha256 of the canonical pre-spec)
- not designed yet
- Frozen
- not frozen
- The definition can still change.
- Backing
bookmaker
- Kind
system
- Live from
2026-10-13
- Matched
{ "hypothesis_id": "IQ140a-wide-trip-with-figures", "similarity": 0.83, "variant": "broad" }- Published
true
- Rules
- On its last run the horse raced wide (from the in-running remark).
- It was beaten that day, by 5 lengths or less.
- It did not start slowly, and was not a held-up horse flattered by a race that fell apart for the leaders.
- Source
In-running remarks analysis, October 2026
- System id
wide-trip-beaten-under-five
- Tier
none
- Where
last_raced_wide = 1 AND last_position > 1 AND last_beaten_lengths <= 5 AND last_slow_start = 0 AND NOT coalesce(last_run_style IN ('midfield', 'held_up') AND last_race_tilt >= 0.2 AND (last_position - 1.0) / max(last_field_size - 1, 1) <= 0.4, 0)
Discovery result
Not measured yet.
Falsification
No attacks yet. Only promising ideas are attacked.
Sealed holdout (vault)
Not queried. Only a frozen idea can spend its one query against the 2020-25 holdout.
Forward record
No forward record. Shadow tracking starts after the vault and counts only races run after the freeze.
Lineage
Agent runs
designer v1ok · 54s · 16 Oct, 11:15
Output (schema-checked)
{ "rule": "last_raced_wide = 1 AND last_position > 1 AND last_beaten_lengths <= 5 AND last_slow_start = 0 AND last_race_type IN ('Hurdle', 'Chase') AND last_going_group IN ('soft', 'heavy')", "refinements": [ { "label": "14/1 or shorter", "rule": "last_raced_wide = 1 AND last_position > 1 AND last_beaten_lengths <= 5 AND last_slow_start = 0 AND last_race_type IN ('Hurdle', 'Chase') AND last_going_group IN ('soft', 'heavy') AND sp_decimal <= 15" }, { "label": "heavy ground last time (where routing wide for fresher ground is most deliberate)", "rule": "last_raced_wide = 1 AND last_position > 1 AND last_beaten_lengths <= 5 AND last_slow_start = 0 AND last_race_type IN ('Hurdle', 'Chase') AND last_going_group = 'heavy'" }, { "label": "chase last time (fence lines make the outer route a common chosen line)", "rule": "last_raced_wide = 1 AND last_position > 1 AND last_beaten_lengths <= 5 AND last_slow_start = 0 AND last_race_type = 'Chase' AND last_going_group IN ('soft', 'heavy')" } ], "control": { "description": "Same-race other runners should be close to 1.00. The control that matters for the rival explanation is the same wide-trip trigger over jumps on ground that was NOT soft or heavy. Code is held the same and only the ground changes, so if the ground-routing explanation is right, that group should keep the system's edge (around 1.2 or higher) while the soft/heavy subset sits near 1.00. If both groups come out about the same, the ground-routing rival fails and the lost-ground reading stands.", "rule": "last_raced_wide = 1 AND last_position > 1 AND last_beaten_lengths <= 5 AND last_slow_start = 0 AND last_race_type IN ('Hurdle', 'Chase') AND last_going_group NOT IN ('soft', 'heavy')" }, "pass_criteria": { "min_bets": 150, "min_ae": 1.05, "max_p": 0.05 }, "forward_bar": { "min_bets": 100, "min_ae": 1, "max_p": 0.2 }, "confounders": [ "Winter jumps seasonality: soft and heavy ground falls mostly in November to March, so the subset is heavier in midwinter cards and bigger staying fields", "Thin window: last_raced_wide exists only from November 2025, so there is about one year in two halves, and soft-ground jumps is a fraction of that", "Soft-ground stayers trade at bigger prices, and the 16/1+ longshot lift common to beaten horses can inflate A/E (hence the 14/1 refinement)", "Today's race may be on different ground or a different code from the wide run, which mixes ground-change effects into the result", "Track mix: soft-ground jumps wide trips cluster at certain galloping tracks (e.g. Haydock, where wide routes are customary), so a track effect could pass for a ground effect", "Remark tagging: 'raced wide' in a jumps comment on soft ground may be written differently ('came wide for better ground'), so the tag may be uneven across going" ], "mechanism": "Over jumps on soft or heavy ground, jockeys often take a wide line on purpose to find fresher, less churned ground. Any extra distance is roughly paid back by the better footing. The horse then gave up little or nothing net, so its finishing position and beaten distance are a fair measure of its ability, and there is no hidden merit for the next race to reveal. If so, the wide-trip edge (A/E 1.27 overall) should shrink to about market level in this subset.", "market_miss": "Under this rival explanation there is no market miss in this subset. The form figures already read fairly, the price is fair, and these runners should sit near 1.00, which dilutes the published wide-trip system. If instead the edge holds at 1.20 or more here, the market is underrating the ground lost even on a chosen wide route, and the ground-lost reading of the system is confirmed.", "prediction": { "direction": "negative", "size": "A/E 0.95 to 1.05 on 150+ bets, clearly below the 1.27 of the overall wide-trip rule and below the jumps good-ground control", "falsified_if": "A/E 1.20 or higher on this subset, or no clear gap below the good-or-faster jumps control (within 0.05 of it). Either would mean deliberate wide routes on soft ground still undersell the horse." }, "notes": "I checked the going values: last_going_group uses lower-case 'soft' and 'heavy', as other live rules do. I kept the draft rule unchanged because it matches the four conditions of the live system SYS-wide-trip-beaten-under-five, plus the jumps and soft-ground restriction the question needs. This is a rival-explanation (dilution) test. 'Negative' here means near or below the market and well under the system's 1.27, not necessarily a strong over-bet, so a 'pass' in the negative direction is unlikely by design. The decisive reading is the gap to the good-ground jumps control, not the absolute A/E. If the subset falls well short of 150 bets in the November 2025 window, treat the result as thin and descriptive. If it comes out at 1.20 or higher, that supports the ground-lost reading. Do not read it as a new trigger." }
Timeline
hypothesis note SYS-wide-trip-beaten-under-five
· importer
New idea SYS-wide-trip-beaten-under-five: System: Wide trip last time, beaten 5 lengths or less (import)
· importer
Every change is an event with an actor: an agent and its version, an engine, a human, or the importer. Current stage: Live.