AI-generated conjecture · below the evidence/publication boundary
← All conjectures · Method, bridges & the corpus itself
A Mirror of Servers, Not Scriptoria
Status is derived only from the shepherd-authored triage/prediction data above -- community submissions and claims are a separate overlay and can never change it (see the participation panel below).
A conjecture about this corpus itself
This is one of five meta-conjectures the generating model posed, blind, in the corpus’s final wave — predictions not about the pre-print world but about this collection of 1001 conjectures: how its verdicts would distribute, where its novelty would concentrate, whether its own governing architecture would survive its own data. Its kill-dataset is the corpus’s adjudication records, which is why it sits outside the ordinary triage ladder (“out of scope” below): it could only be judged once everything else had been.
Those records now exist, and on 11 July 2026 the model formally resolved this conjecture against them. Verdict: supported
Leaked (re-derived-published) rates track kill-database scale, not production: cuneiform W22 13.3% (CDLI: >500,000 known artifacts, >360,000 electronically catalogued), exact sciences W20 16.7%, law W21 13.3%, medieval literature W07 14% (Trismegistos-class corpora ~964,000 text entries; Cantus ~500,000 chant records) — versus 0% leaked AND 0% novel in South Asia (W18 Americas, W23 women, W24 oral-written likewise 0% leaked), although South Asia alone holds an estimated ~10 million extant manuscripts (NAMAMI database ~3.4M entries) against Buringh & van Zanden's ~8 million manuscript copies for the entire medieval West's production. All 10 actually-resolved prediction records (7 conjectures) closed against digitized databases (DBBE, Pinakes, papyri.info/CDLI-derived samples, colophon lists); zero closed against production-estimate evidence.
The pre-registered Steiger test is not computable as posed — the triage records contain no killability field (I proxy it with leaked rate and with which predictions actually resolved: both flagged choices), per-stratum conjecture counts were fixed by the registered allocation rather than measured (a circularity), and no published per-region pre-print production series exists at stratum granularity — so per the adjudication instruction the primary clause is judged QUALITATIVELY, and I say so. Judged on substantive content, the direction is unambiguous: every checkable signal in the corpus (leaked rate, novel pockets, actual resolutions, in-house kill quotas) sits where 20th-21st-century digitization is thick, and the strata that dominate honest production estimates (South Asia foremost) yield zero checkable signal. Caveats: this was also the architecture's own Section 3.5 prior, so allocation was partly self-fulfilling — though the verdict rates were measured blind; and W16 Africa is a counterexample in one direction (15% novel atop small databases), driven by thin-literature unlocatability rather than database mass. The rho>=0.6 / rho<=0.3 / Steiger-p secondary machinery remains formally unrun; a numeric replication would require post-hoc killability scoring and an assembled production-estimate series.
Claim (verbatim)
The corpus presents itself as a portrait of the pre-print world, but its true shape may mirror something else entirely: the modern digitization landscape that fed the model. I conjecture that the corpus's per-stratum density and killability track the record counts of present-day databases — CDLI's hundreds of thousands of tablets, Cantus's chant entries, papyri.info's documents — far more closely than they track historians' best estimates of actual pre-print textual production by region and period. The mechanism is straightforward: a model's confident, testable claims form where its training data is thick, and its training data is thick where twentieth- and twenty-first-century institutions chose to digitize, a choice driven by colonial collecting history and funding fashion rather than by what the pre-print world actually wrote. If this holds quantitatively, the corpus is best read as a high-resolution map of digitization bias wearing the costume of a historical atlas — and every future model-generated research program should be corrected for the same distortion.
Prediction clause (verbatim)
Across strata, the Spearman correlation between conjectures-per-stratum weighted by triage killability and the record counts of the corresponding kill-datasets will be at least 0.6, while the Spearman correlation between the same corpus measure and published scholarly estimates of pre-print textual production per region will be at most 0.3. Primary clause (the verdict follows it): the difference between the two correlations is significant by a Steiger dependent-correlations test at p < 0.05. Secondary clauses: the individual rho >= 0.6 and rho <= 0.3 thresholds.
Kill-dataset (verbatim)
The One Thousand and One Conjectures corpus and its triage/adjudication records; kill is a statistical test (comparison of dependent Spearman correlations).
Nobody has run this test. The kill-data is named above. If you can run it — or you know the paper that already settles it — claim the kill or submit the prior. Kills and priors are credited here, by name, as they come in.
In the atlas
This conjecture is bridged, as an L1 lead, onto these Inferpedia subject pages.
Provenance
Run: Fresh agent generation · model: claude-fable-5
Composed blind by claude-fable-5 with zero tool use, emitted as a single JSON text message per the fresh-lane blindness protocol.
Novelty / leakage triage
out of scope (a meta-conjecture about the corpus itself)
Meta-conjecture about digitization bias in the 1001-corpus itself, killable only against the project's own records; out of shepherd scope per the W26 calibration rule.
Predictions
No prediction registered yet.
Weigh in
No community feedback yet.
Add your take
Posted immediately (spam is removed). Community feedback is never an adjudicated verdict and never changes this conjecture's triage label or status above.
Working on this?
Sign in to claim this conjecture and let others know you're working on it.