IVC Translation Research
An attempt to decipher the Indus script that has accepted exactly one claim, and zero readings.
The Indus Valley script has resisted decipherment for a century. Nobody knows what language it writes, whether signs are sounds or words, or even whether it’s fully a writing system. That makes it a perfect trap: the space of plausible stories is enormous, and most “I decoded an ancient script” projects quietly work backward from the answer they wanted.
This workspace is built to make that structurally hard. Nothing counts until it’s in the claim ledger, and nothing gets into the ledger until it survives forger tests (can random or shuffled data produce the same pattern?), skeptic attacks, and provenance checks on every source it leans on. Claims are split by class, so a structural regularity can never be smuggled in as a reading.
The ledger, as of today, is in the panel above. One accepted structural finding. Zero accepted translations, sound values, sign meanings, or language identifications. Thirteen candidates have been proposed and put through the gates; eleven were retracted. Tainted branches of the work aren’t deleted, they’re quarantined, kept for autopsy but never citable as support unless they’re re-earned from scratch.
The one survivor is deliberately modest: the sign string 861 | 533 | 717 recurs after sign 002 on two separate seals, tested against 4,135 strict rows of the corpus. It’s a pattern, not a meaning. The most recent campaign ran four independent routes at the problem and ended, correctly, with “no reading accepted.”
It is not an app and it is not finished. It is the unglamorous version of decipherment: mostly a discipline for not fooling yourself, which is the only version that has ever actually worked.