Ars Inquirendi

AI-generated conjecture · below the evidence/publication boundary

← All conjectures · Money & economy

Hoards as a fear index

Status: Already answered

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).

This is a proposed connection between two domains, generated by a language model. It is not an article and not evidence: it sits below the evidence/publication boundary. A quantitative prediction and a named kill-dataset are attached (when registered) so the claim stays falsifiable rather than merely evocative.

Claim (verbatim)

Hoards as a fear index. Coin hoards and the VIX volatility index are the two well-known things joined here: hoard deposition is antiquity's fear gauge. People bury treasure when they are frightened, and — crucially — they bury on rumor, before armies actually arrive, just as modern volatility indices spike before crises fully materialize. So dated hoard deposition rates should lead the invasions recorded in narrative sources by months, rather than trail the events they respond to. The index has a second dial: a hoard survives to be excavated only when its owner never came back for it, so non-recovery rates should scale with conflict mortality — the deadlier the episode, the larger the share of buried hoards never retrieved. Deposition timing measures the fear; non-recovery measures how justified the fear turned out to be.

Prediction clause (verbatim)

For each invasion or conflict episode dated in chronicle chronology, align the regional deposition-rate curve from dated hoard databases and measure the offset between the deposition spike and the chronicled event, plus non-recovered hoard density against the episode's severity. Primary clause: deposition spikes precede their chronicled invasions in at least two-thirds of episodes, with a median lead measured in months rather than years, and hoard non-recovery counts scale positively with conflict mortality across episodes; systematically lagging spikes, or no severity scaling, kill the conjecture. The verdict follows the primary clause.

Kill-dataset (verbatim)

dated hoard databases vs chronicle chronology.

In the atlas

This conjecture is bridged, as an L1 lead, onto these Inferpedia subject pages.

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

already answered in the literature

The core join — hoard deposition/non-recovery as a quantitative instability-and-mortality gauge — is published: Turchin & Scheidel use unrecovered coin-hoard frequency as a proxy for internal warfare in Roman Italy, with non-recovery explicitly tied to owners killed or displaced. The harvest's months-scale refinement (deposition LEADING invasions in narrative sources, burial-on-rumor) was not located, and the dossier notes linking hoards to specific military events is regarded as notoriously difficult; but the connection itself is established. Chosen class matches the pilot's leaked calibration items.

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.