MMRF v1.0
A prime dataset defined by what it will not answer.
Every number below comes from a frozen, hash-covered dataset, and every figure on this site is regenerated from that dataset rather than typed in. The interesting part is the other half: the questions this infrastructure is built to decline.
crosses the boundary
- a density
- a quantile
- a histogram
- a count
- a manifest hash
- an audit event
never crosses
- a target integer
- an RSA modulus
- a factor
- a factor candidate
- a narrowed range
- a prime list
The guard runs before the data layer. A refused request costs nothing, reads nothing, and is still recorded.
What is published
One dataset generation, frozen. 148,933 prime records covering [0, 2,000,000), stored as 20 immutable columnar shards under a single manifest hash. Appending a range never rewrites a prior shard.
- Release
- MMRF-1.0.0
- Prime records
- 148,933
- Shards
- 20 × immutable NPZ
- Range
- [0, 2,000,000)
- Columns
- 10
- Stable manifest
a5caea22a57efaac915c00dd92c655b1126e0b6d9b2b93790e48bc167733e0d1
The query surface is aggregate-only
There are seven permitted operations. Each returns a statistic over a shard range — a density, a quantile, a histogram, a count. None returns a prime, a list of primes, or anything conditioned on a number you supply.
- dataset_metadata
- interval_density
- gap_quantiles
- gap_histogram
- residue_distribution
- family_counts
- workflow_replay
Seventeen request fields are refused by name before the request is parsed further. The guard runs ahead of the data layer, so a refused query never reaches a shard — it costs cost_units: 0 and produces a hashed audit event anyway.
- n
- integer
- target
- modulus
- rsa_modulus
- public_key
- private_key
- factor
- factors
- candidate
- candidates
- range_narrowing
- nearest_prime
- prime_list
- exact_primes
- source_integer
- source_factor_relation
Measured, not asserted
The four aggregates below were computed from the shipped shards on this machine, not copied from the release notes. The full output, its hash, and the script that produced it are on the research page.
That last figure is the one worth pausing on. Across the eight residue classes coprime to 30, the counts differ by only 114 out of roughly 18,616 each — primes are distributed almost perfectly evenly among the classes they are allowed to occupy.
Start here
Citation
EveMissLab Technology Co., Ltd.. MMRF Public Prime Lake Schema 0.9. MMRF dataset MMRF-DATASET-73015C5329AE7190; manifest 73015c5329ae71900ef3f4aca7f35152f3d96a435e65e3bddbd1ae513d597420.