Hypotheses · shock · S5-hurdle-completed-large-negative
S5: hurdle completed large negative
holdout SUPPORTIVE: A/E 1.203 on 239 (GB 1.142, IRE 1.375), p 0.1787 against BH 0.003448 over 29 tests; LEARNINGS read it as holding
Starts the thread “S5: hurdle completed large negative” 1 hypothesis
- Proposed
- Designed
- Discovery
- Promising
- Falsification
- Frozen
- Vault
- Provisional
- Shadow
- Validated
- Live
- Source
- Imported from the RaceiQ holdout
- Made by
- import
- Created
- 15 Oct, 23:10
- Tests logged
- 2
Mechanism and rationale
Shock test S5-hurdle-completed-large-negative (shock.py, frozen before the holdout was fetched)
The rule
code = 'Hurdle' AND finished = 1 AND s <= -1.5
Reads: code, finished, s
Pre-registration
- Spec hash (sha256 of the canonical pre-spec)
- 78a36ffc1ad495bdf1934155635efb6673168026efbd152c42f7c0a0b5ce6321
- Frozen
- 14 Oct, 01:00
- Nothing in the definition can change after this.
- Direction
positive
- Frozen in
research/experiments/raceiq/shock_tests
- Frozen on
2026-10-14
- Id
S5-hurdle-completed-large-negative
- Rule
code = 'Hurdle' AND finished = 1 AND s <= -1.5
Result (from the archive)
info discovery year (reference) · 15 Oct, 23:10
- Bets
- 266
- A/E
- 1.26
- winners vs the prices
- SP return
- -15.7%
- level stakes
- Betfair SP return
- +4.6%
- 266 bets with a BSP
Strike rate 10.2%.
By period
Falsification
No attacks yet. Only promising ideas are attacked.
Sealed holdout (vault)
- Bets
- 239
- 14 Oct, 13:00
- A/E
- 1.20
- p = 0.18
- BH threshold then
- 0.0034
- over every vault test so far
- Outcome
- Failed
- from the archive
Forward record
- forward check refusederror
· 15 Oct, 23:21
Lineage
No parent and no descendants yet. When an agent mutates, generalises or splits this idea, the new hypotheses appear here.
Agent runs
No agent has worked on this yet.
Timeline
Job 2110 gave up: OperationalError: no such column: code Traceback (most recent call last): File "/app/lab/src/gallops/orchestrator/loop
· engine:compute-1
compute-1 took job 2110 (forward_check, attempt 5)
· compute-1
Job 2110 will retry: OperationalError: no such column: code Traceback (most recent call last): File "/app/lab/src/gallops/orchestrator/loop
· engine:compute-1
compute-1 took job 2110 (forward_check, attempt 4)
· compute-1
Job 2110 will retry: OperationalError: no such column: code Traceback (most recent call last): File "/app/lab/src/gallops/orchestrator/loop
· engine:compute-1
compute-1 took job 2110 (forward_check, attempt 3)
· compute-1
Job 2110 will retry: OperationalError: no such column: code Traceback (most recent call last): File "/app/lab/src/gallops/orchestrator/loop
· engine:compute-1
compute-1 took job 2110 (forward_check, attempt 2)
· compute-1
Job 2110 will retry: OperationalError: no such column: code Traceback (most recent call last): File "/app/lab/src/gallops/orchestrator/loop
· engine:compute-1