Ars Inquirendi

AI-generated conjecture · below the evidence/publication boundary

← All conjectures · Time, sky & calendars

Portolan crowd wisdom

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)

Portolan crowd wisdom. This joins the mysterious accuracy of medieval portolan charts to the statistics of error averaging. Portolans appear in the late 13th century already startlingly accurate, with no known surveying campaign behind them; the conjecture's explanation is that they are averaged compass logs — compilations of bearings and distances reported by many voyages, in which each sailor's random errors partly cancel. Statistics dictates the signature of such averaging: the error of a mean of n independent estimates shrinks as 1/sqrt(n). If portolans were built this way, chart accuracy per route should scale as 1/sqrt(voyage traffic): heavily sailed routes, contributing many logs, should be drawn proportionally more accurately than lonely ones, following that specific square-root law. Cartometric analysis can measure each route's error on surviving charts, traffic can be proxied from commercial records, and the two should fall on the predicted curve.

Prediction clause (verbatim)

For each route segment in a dataset of cartometric route error vs traffic proxies, measure the chart's positional or bearing error against modern coordinates, and estimate relative voyage traffic from commercial and notarial records; fit log(error) against log(traffic) across routes on the same chart. Primary clause: the fitted slope must be negative, significant, and lie within 0.25 of the theoretical value of -0.5, with the inverse-square-root law fitting better than a null of traffic-independent error; route errors uncorrelated with traffic, or a slope far from -0.5, falsify the claim. The verdict follows the primary clause.

Kill-dataset (verbatim)

cartometric route error vs traffic proxies.

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 a named, actively disputed hypothesis in the cartometric literature — the 'averaging hypothesis' that portolan accuracy derives from compiled compass-and-distance observations of many voyages — and notable evidence runs AGAINST it (accuracy did not detectably improve from the earliest dated charts onward; Nicolai argues accuracy exceeds what averaging could produce). The harvest's 1/sqrt(traffic) scaling law per route was not located as tested, but the connection is established and contested rather than new.

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.