AI-generated conjecture · below the evidence/publication boundary
← All conjectures · Time, sky & calendars
Intercalation as policy
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)
Intercalation as policy. This joins calendrics to political economy. Before the 19-year cycle fossilized Babylonian practice, Mesopotamian leap months were declared ad hoc, by royal or priestly decision, ostensibly to keep the lunar calendar aligned with the seasons. But an extra month is also an economic instrument: it postpones the tax and debt deadlines that fell at fixed calendar points, granting the countryside a thirteenth month of breathing room. The conjecture holds that intercalation was used exactly this way — that ad-hoc leap months cluster after poor harvests, beyond what astronomical drift alone would require, making the calendar a tool of economic stimulus. Dated intercalations survive in abundance, and harvest quality can be proxied from flood records and commodity prices; the two series should show intercalary years disproportionately shadowing the bad ones.
Prediction clause (verbatim)
For each attested leap month in dated intercalations vs flood and price proxies, restricted to the pre-standardization era, record its year and pair it with harvest-quality indicators — river-level records and barley or silver price movements — for the preceding season; compare intercalation frequency after poor harvests against frequency after normal or good ones, controlling for the astronomically expected intercalation rate. Primary clause: intercalation probability following poor-harvest years must exceed that following good-harvest years by at least 50 percent in relative terms, and the excess must survive the astronomical-drift control; no harvest dependence falsifies the claim. The verdict follows the primary clause.
Kill-dataset (verbatim)
dated intercalations vs flood and price proxies.
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
That early Mesopotamian intercalation was ad hoc and guided partly by seasonal/agricultural signs (weather, crop ripening) is the standard account — a weak qualitative form of calendar-responds-to-harvest; the quantitative test of dated intercalations against flood/price proxies was not located (one possibly-relevant paper was unfetchable, noted in the dossier).
- Babylonian calendar (Livius overview) — Ad hoc intercalation guided by seasonal signs
- 'Early Mesopotamian Intercalation Schemes', MAA Journal — Title-relevant; 403 on fetch, content unconfirmed
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.