AI-generated conjecture · below the evidence/publication boundary
← All conjectures · Chance & decision
Managed randomness at Anyang
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).
Claim (verbatim)
Managed randomness at Anyang. The Shang kings at Anyang divined by heating cattle scapulae and turtle plastrons until they cracked, reading the cracks as answers — and the inscriptions often record the sequence in which the questions were put. Crack formation, driven by micro-structural accidents of bone and heat, should be a genuinely random process; but human handlers of random processes are prone to the gambler's fallacy, expecting streaks to self-correct. The conjecture couples the two: the crack outcomes themselves are statistically random, while the question sequencing shows the diviners applying gambler's-fallacy corrections — re-posing or reframing charges after runs of unfavourable answers, in ways sensitive to streak length. That would reveal a Bronze Age court managing its own random number generator: a genuinely stochastic oracle curated by officials exhibiting exactly the biases modern psychology predicts. Streak statistics in the Anyang corpus can catch them at it.
Prediction clause (verbatim)
From the Anyang oracle-bone corpus, code sequential divination outcomes (favourable/unfavourable) within inscription series, together with the diviners' follow-up behaviour (re-posing, reframing, topic change). Primary clause: the outcome sequences are consistent with randomness (runs tests not rejected at p > 0.05 corpus-wide), while the probability of re-posing or reframing a charge rises significantly with the length of the preceding unfavourable streak (positive trend at p < 0.05). The verdict follows the primary clause.
Kill-dataset (verbatim)
streak statistics in the Anyang corpus.
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 scholarship. Kills and prior scholarship are credited here, by name, as they come in.
On Inferpedia
This conjecture has been linked to the following subject pages on Inferpedia — an encyclopedia of the missing, now in limited preview.
Provenance
Run: Imported conversation (verbatim harvest) · model: claude-fable-5
Origin: operator conversation with Claude Fable 5 at max effort, conducted 2026-07-03, relayed verbatim by the operator into the shepherd session on 2026-07-04. No ModelRun exists for the original generation (it happened outside the pipeline); this transcript file is the canonical capture. Transcript path: docs/generated/conjecture_harvest_fablemax_20260703.md. Model (operator-attested, not pipeline-recorded): claude-fable-5. Novelty disclaimer (verbatim, load-bearing -- rule 4): "Same caveat as before, doubled: at 100 items across all of archaeology and history, some of these will have cousins in the literature I can't check. What I can guarantee is the format — each links two things not normally linked, and each names the dataset or measurement that would kill it."
Novelty / leakage triage
anticipated in the literature — this exact test has never been run
Statistical analysis of early Chinese divination records exists (numerical sequences on bones and artifacts, continuity studies), and royal interference with divination inscription is documented — so quantitative and manipulation-adjacent work is published. The specific two-part claim (crack outcomes statistically random; question SEQUENCING shows gambler's-fallacy corrections) was not located.
- 'Cracking bones and numbers: solving the enigma of numerical sequences on ancient Chinese artifacts' — Statistical treatment of divination sequences
Predictions
No prediction registered yet.
Weigh in
No community feedback yet.
New here? Create an account first
Create an account or sign in and your feedback is tied to you — you can track it, get replies, and claim this conjecture so others know you’re working on it. Prefer not to? Just leave your take below as a guest — only the name you type is shown.
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.