← All conjectures · Texts, scribes & transmission
The Fleet Is the Bridge
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)
For the far Indian Ocean rim, Ming contact was state-carried, not merchant-carried: it existed exactly as long as the treasure fleets (1405-1433) and their diplomatic afterwash, and it stopped with the 1435 retrenchment. Polities west of the Malacca Strait - Bengal, Ceylon, Calicut, Hormuz, Aden, Mogadishu - should therefore appear in the Ming Shi-lu almost exclusively inside the window 1403-1440, while mainland and archipelagic neighbors (Champa, Siam, Java, Melaka) spread their entries across the whole span 1368-1500, because proximity sustains contact without fleets. The temporal shape of the record distinguishes bridge types: infrastructure-dependent connection is pulse-like, neighborhood connection is baseline.
Prediction clause (verbatim)
Prediction: for every far-rim polity with at least 10 dated entries, at least 75% of its Ming Shi-lu entries from 1368-1500 fall within 1403-1440, while for every enumerated near polity with at least 10 entries the same share is below 50%, sign-consistent across all qualifying polities; coverage guard: at least 5 far-rim and 4 near polities meeting the 10-entry floor in the database, else inconclusive.
Kill-dataset (verbatim)
Kill: the open-access Southeast Asia in the Ming Shi-lu database (Wade) - count dated entries per named polity per decade, 1368-1500, and compute each polity's 1403-1440 share.
On Inferpedia
This conjecture is linked to the following pages on Inferpedia, an encyclopedia of the missing — working atlas pages, some still early scaffolding.
Provenance
Run: Fresh agent generation · model: claude-fable-5
Fresh blind generation by claude-fable-5, 2026-07-20, for the connected-Old-World (movement-signatures) wave. The sixteen items lean on digit-string error phylogeny, first-translation-lag profiles (backlog cliffs and two-pulse corridors), bridge-language fingerprints (Sogdian, Aramaic-chancery, Judeo-Arabic), attribution drift, and pulse/directional asymmetries, with five anti-connection wagers (ordinals 2, 9, 13, 14, 15) where independence or non-transmission is the predicted outcome.
Novelty / leakage triage
already answered in the literature
That embassies from Bengal, Ceylon, Calicut, Hormuz, Aden, and the Swahili coast reached the Ming court essentially only within the treasure-fleet window and its immediate afterwash, while Champa, Siam, Java, and Melaka sustained missions across the whole dynasty, is documented fact in the Zheng He and tribute-system literature. More pointedly, Wade — the author of the very database pinned for the kill — has published quantitative analyses of Ming Shi-lu mission frequencies across the fifteenth century that exhibit precisely this pulse-versus-baseline contrast between far-rim and neighboring polities. The 75/50-percent per-polity thresholds and the sign-consistency clause are a formalization of a published result, not a new question. Leaked: the primary claim is stated and effectively tested in the corpus author's own print.
Sources cited by the triage
- Geoff Wade (trans.), Southeast Asia in the Ming Shi-lu: An Open Access Resource, Asia Research Institute and Singapore E-Press, National University of Singapore, 2005.
- Geoff Wade, “Engaging the South: Ming China and Southeast Asia in the Fifteenth Century,” Journal of the Economic and Social History of the Orient 51 (2008). — Quantitative mission-frequency analysis by the database's own author.
- Edward L. Dreyer, Zheng He: China and the Oceans in the Early Ming Dynasty, 1405-1433, Pearson Longman, 2007. — Documents the far-rim embassies' confinement to the fleet era.
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.