I Run a Lottery Model That Publishes Its Own Failures — 51 Draws of Mark Six Data
Most lottery prediction sites show you their wins. Mine shows you the misses — every single one, on a public status page. Here's why I built it that way, and what 51 draws of Hong Kong Mark Six data actually look like under an honest model. The setup I maintain three independent number generators for Mark Six (6 numbers out of 49, plus an extra number): Science — frequency, recency, and…
This reporter from the wire details a unique lottery model that openly publishes its failures. The model generates three sets of numbers: one based on statistical frequency, recency, and omission-gap weighting, another using physics-based priors like ball-machine simulation and positional bias, and finally, a control group with a deliberately non-statistical baseline based on numerology rules.
If the control group ever matches the statistical models' hit rate, it indicates the statistical models lack any signal. So far, the control group has not matched the statistical models, which is keeping the other two honest.
The last draw, number 26104, had winning numbers [4, 28, 31, 44, 47, 48] plus an extra number 19. The statistical model achieved 0/6 hits, the physics model got 1/6 hit, and the control group had 0/6 hits, resulting in a total of 1 hit versus the expected 2.2 for random picks of 18 numbers out of 49. This performance is below random, and the reporter still publishes this information.
The model's self-calibration process is also discussed, where every signal the model emits is scored against actual results, and the weights automatically update. Over the last 24 parameter updates, the 'late steam' weight oscillated between 0.947 and 0.992, showing the model's ability to correct itself without human intervention.
The next draw, number 26105, with picks published in advance, is scheduled to be released tomorrow. The consensus across models predicted number 48 and 7 to appear in the winning numbers. The reporter emphasizes that honesty is the actual product, highlighting the importance of providing full prediction history, post-mortems, public health checks of the pipeline, and calibration stats that include losing streaks.
This approach distinguishes the project from a market for lemons, where everyone claims high accuracy rates without any auditing. The model is built on Cloudflare Workers + Pages + KV/D1, with a cron snapshot every 2 minutes on race days, and an EMA drift loop in Python. The reporter is available to answer questions about the model's architecture.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
