AI-generated conjecture · below the evidence/publication boundary
← All conjectures · Networks & trade
Tin percolation collapse
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)
Tin percolation collapse. Bronze needs tin, and Late Bronze Age tin moved through a long-distance exchange network linking a handful of distant sources to every workshop in the eastern Mediterranean. In network terms, some cities were mere consumers while others were high-betweenness brokers — nodes through which a disproportionate share of the metal flow had to pass. The conjecture is that the famous cascade of destructions around 1200 BCE propagated through this network rather than across the map: the order in which sites were destroyed should follow their betweenness centrality in the metals network, with the critical brokers failing early, and should not follow geographic dominoes in which each site falls to its nearest burning neighbor. Destruction-layer dates set against modeled centrality would decide between the two propagation regimes.
Prediction clause (verbatim)
Build the Late Bronze Age metals-trade network from attested tin and copper routes, compute betweenness centrality for each major site, and take destruction dates from the destruction-layer dates vs modeled network centrality dataset; regress destruction order on centrality and, separately, on geographic distance from the earliest destruction. Primary clause: betweenness predicts destruction order with Spearman ρ ≥ 0.5 (p < 0.05) and outperforms the geographic-contagion model in out-of-sample rank prediction. The verdict follows the primary clause.
Kill-dataset (verbatim)
destruction-layer dates vs modeled network centrality.
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
already answered in the literature
The core join is published: recent work models the Late Bronze Age Mediterranean as a multi-layer network and analyzes the collapse as cascading failure with betweenness-centrality/'gatekeeper' node concepts (plus a systemic-risk literature doing the same). The harvest's sharp refinement — regressing site-by-site destruction-layer DATES against computed centrality rankings of a metals-specific network — was not located as executed, but the connection itself is established.
- 'Are civilizations destined to collapse? Lessons from the Mediterranean Bronze Age', Global Environmental Change (2023) — Two-layer LBA network model, cascading failure, gatekeeper centrality
- Galaitsi et al., 'Navigating the precipice: Lessons on collapse from the Late Bronze Age', Risk Analysis — Systemic-risk network framing of 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.