AI-generated conjecture · below the evidence/publication boundary
← All conjectures · Money & economy
Sticky wages in Sumer
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)
Sticky wages in Sumer. Nominal wage rigidity — the Keynesian observation that wages resist adjustment even when prices move — is here pushed back four thousand years to the ration lists of Ur III Mesopotamia. Ur III institutions paid workers standardized rations of beer and barley, recorded in tens of thousands of administrative tablets. The conjecture is that these ration quantities behaved like modern sticky wages: they should hold unchanged through price shocks that ought, on flexible-market logic, to have moved them. The adjustment, as in modern firms that cannot cut the headline wage, should hide in quality — thinner beer, poorer grades of barley — while the nominal quantity stays fixed. If so, the world's oldest wage records already exhibit the rigidity that macroeconomics treats as a modern institutional artifact.
Prediction clause (verbatim)
For each archive with overlapping coverage, assemble ration quantities per worker category over time alongside barley price proxies, and test whether nominal ration quantities respond to price shocks. Primary clause: across documented price shocks, standard ration quantities remain unchanged in at least three-quarters of worker-category series (elasticity of quantity to price indistinguishable from zero), while quality indicators such as beer strength or barley grade shift in the adjusting direction where recorded; ration quantities that adjust freely with prices kill the conjecture. The verdict follows the primary clause.
Kill-dataset (verbatim)
ration quantities vs barley price proxies across archives.
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
The enabling literatures partially embody the claim: Ur III barley:silver price series are reconstructed (including the Ibbi-Suen near-hyperinflation), and the ration system's standardized disbursement schedules are core Assyriology. What was not located is the economics framing and its sharp test — ration quantities as nominally rigid wages held fixed through price shocks with adjustment hidden in quality.
- 'The Structure of Prices in the Neo-Sumerian Economy (I): Barley:Silver Price Ratios', CDLJ 2017:2 — Stable equivalence ~35 years, then sharp late devaluation
- 'Cults and Prices at the Collapse of the Ur III State', JCS — Price structure during the collapse
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.