AI-generated conjecture · below the evidence/publication boundary
← All conjectures · Chance & decision
Khipu redundancy
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)
Khipu redundancy. Spanish chroniclers report that Inca accounting was run by paired officials who kept independent records of the same stocks so that each could check the other — and the surviving corpus does contain matching khipus, cord records whose numerical content substantially overlaps. The information-theoretic question is what kind of copies they are. Mechanical duplication — one khipu transcribed from another — propagates errors identically and shares every idiosyncrasy of layout; independent encoding by two accountants, later reconciled, instead produces records that agree on the audited totals while differing in construction details, groupings and residual discrepancies. The conjecture is that paired accounting khipus from checker-pairs of officials show exactly the second pattern: differences consistent with independent encoding plus reconciliation, not duplication. Khipu redundancy would then be an error-correction scheme — dual-entry auditing in knotted cord — testable on the matching pairs in the Khipu Database.
Prediction clause (verbatim)
For matching khipu pairs in the Khipu Database, compare agreement on aggregate numerical values against concordance on construction variables (cord grouping, knot placement, colour patterning). Primary clause: in at least two-thirds of matching pairs, the recorded totals agree while at least one construction dimension diverges substantially beyond what direct transcription would produce — the signature of independent encoding reconciled on the numbers. The verdict follows the primary clause.
Kill-dataset (verbatim)
Khipu Database pair analysis.
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: the 'Khipu Archives' study examines duplicate/matched khipu sets in the Harvard database against chronicle accounts of multiple parallel khipu-keepers as a checks-and-balances system, distinguishing 'linked' (near-identical) from 'matched' (double-entry-like) pairs — substantially the conjecture's paired-accounting-with-reconciliation claim. Access caveat: full text 403-blocked in the dossier session, so whether its statistical characterization matches the independent-encoding-plus-reconciliation signature specifically is unconfirmed; the join itself is established per the paper's own description.
- 'Khipu Archives: Duplicate Accounts and Identity Labels in the Inka Knotted String Records' (Harvard DASH) — Matched/linked khipu pairs + checks-and-balances framing (snippet-cited; 403)
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.