Garshuni is a lock

Status: Anticipated · untested

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)

Garshuni is a lock. This connects script choice with information control in a shared-language world. Garshuni, Arabic language in Syriac script, is usually explained as scribal habit or identity display. The conjecture: it also functioned as a soft access-control layer, keeping community texts in the common spoken language unreadable to the majority scribal culture, and the communities knew it. If the lock worked, circulation should be measurably sealed: ownership and reader notes in Garshuni books should be almost exclusively intra-communal across centuries, while Christian Arabic books in Arabic script, carrying the same kinds of content, leak across communal lines at detectable rates through sale, pawn, and curiosity.

Prediction clause (verbatim)

In catalogued Garshuni manuscripts, the share of legible ownership and reader notes carrying extra-communal markers (Muslim or Jewish name formulas) is at most 5%, while Arabic-script Christian manuscripts from the same regions and centuries show an extra-communal note share of at least 10%. Primary clause: the Garshuni extra-communal share at or below 5%; the verdict follows it. Secondary: the at-least-5-point gap between the two script groups.

Kill-dataset (verbatim)

Kill: the Mingana Collection catalogues (Birmingham) and vHMML's Garshuni records, both of which transcribe ownership and reader notes.

Nobody has run this test. The kill-data is named above. If you can run it — or you know the paper that already settles it — claim the kill or submit the prior scholarship. Kills and prior scholarship are credited here, by name, as they come in.

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: Fresh agent generation · model: claude-fable-5

Generated by a fresh Fable-tier instance (claude-fable-5) at maximum effort with generation-first blindness (no repo reads, no web searches, no DB queries); 218-title list supplied at launch, titles only, no verdicts/dossiers seen; prompt pre-committed in docs/generated/conjectures_1001_wave_ledger.md and docs/generated/conjecture_fresh_fable_w03_prompt_20260708.txt. Wave W03 of docs/GOAL_CONJECTURES_1001_CAMPAIGN_20260708.md. Novelty unverified by construction.

Novelty / leakage triage

anticipated in the literature — this exact test has never been run

Garshuni's function is debated, with identity-preservation and boundary-marking explanations published (Maronite case studies), which anticipates the exclusion mechanism qualitatively, but the circulation-sealing test on ownership and reader notes versus Arabic-script Christian controls is un-run.

'Arabic-Karshuni: An Attempt to Preserve the Maronite Identity: The Case of Aleppo', The Levantine Review 2/1

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.