← All conjectures · Islamicate book cultures

The laureate's fraction

Medieval Dated c. 990 CE – 1040 CE Islamic world

Status: Falsified

The verdict’s fine print — quoted from the resolution record: “KILLED ON THE FIRST LIMB OF ITS OWN CONJUNCTION - the number died while the mechanism it was meant to capture was resoundingly confirmed; the caveats carry both facts at full weight.” Read the full caveats ↓

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 conjecture imagined by a language model — drawn from its trained weights and held to falsifiability, novelty, and plausibility, not to any one method: it may join two or more fields, or none. 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)

Unsuri (Abu'l-Qasim Hasan Unsuri Balkhi, d. c. 431/1039) was amir al-shu'ara, poet laureate, at the court of Mahmud of Ghazna, the most powerful literary patron of the age, and presided over a workshop of court poets. The tazkira tradition assigns his divan a great extent - Dawlatshah and later sources report figures in the tens of thousands of couplets - and credits him besides with three verse romances. Whatever the exact total, it describes a laureate's life-output at a fabulously rich court. What survives is a slim divan of a few thousand couplets and three romances reduced to fragments or bare titles. The mechanism is the panegyric trap. The praise-qasida is the most patron-bound, occasion-specific genre in the tradition: its market value collapses the moment the praised dynasty falls, and no devotional or scholastic institution ever adopts it, so the very poems most lavishly rewarded in 1030 had the least reason to be recopied in 1250. The romances fared worse still - Vamiq u Adhra survives only because stray leaves turned up in a book-binding, the other two are names. Ganjoor's Unsuri corpus is the surviving slice. Prediction restated: the head of Mahmud's poets survives at a small fraction of even a conservative reading of his attested output, and his narrative poetry has no complete text at all - the paradigm case of a celebrated poet whose fame did not protect his lines.

Prediction clause (verbatim)

Prediction: the total bayt count of the Unsuri (عنصری) divan on Ganjoor will be under one third of the divan size the tazkira tradition reports for him (a reported figure on the order of 30,000 bayt, flagged here as a soft topos), and each of his three attested verse romances - Vamiq u Adhra, Khing-but u Surkh-but, Shadbahr - will have zero complete text on Ganjoor (primary clause, resting on the hard surviving counts: the Ganjoor Unsuri divan under 3,000 bayt AND no complete romance text; the reported-total ratio is the corroborating figure). Romance survival is scored on complete text; surviving fragments do not count as presence.

Kill-dataset (verbatim)

Kill: the Ganjoor (ganjoor.net) Unsuri corpus for the surviving bayt count and for the presence or absence of each romance, against his reported divan size and romance titles in Safa's Tarikh-i adabiyat dar Iran and de Blois' Persian Literature: A Bio-Bibliographical Survey.

In the kill-dataset registry:

Ganjoor (Open Persian Poetry Corpus)

Provenance

Run: Fresh agent generation · model: claude-fable-5

Fresh blind generation by claude-fable-5, 2026-07-17, Persianate wave instrument-anchored on the open Ganjoor corpus (ganjoor.net) with the Cambridge Shahnama Project as the second instrument where manuscript transmission is the question. Every Kill names one corpus and one countable/positional/citation-geometric operation, thresholds sit far from 1, disambiguation and name-matching rules are pinned inside each prediction, and coverage guards separate what Ganjoor holds (print-era critical editions) from what existed. DISJOINTNESS: the Nizami/Khamsa transmission ground and de Blois vol. V's Nizami dated-manuscript census are owned by minds-w02 (item 'The Khamsa is bound, not born') and are NOT re-posed here; the Rumi Masnavi return-formula operation on Ganjoor is owned by minds-w02 and avoided; the Ferdowsi age-statement / reign-boundary operation on the Ganjoor Shahnameh is owned by minds-w01 ('The Shahnameh keeps the poet's birthdays') and the Shahnama interpolation-topography / illustrated-extent / folio-grid / dispersal / defacement operations are owned by fable-w01 (#14), fable-w03 (#24) and fable-w05 (#3,#4,#11) on the Cambridge Shahnama Project - so the Daqiqi item here reuses the Ganjoor Shahnameh and Cambridge Shahnama instruments ONLY under a distinct survival-by-embedding operation, flagged in its Kill; prose Kalila wa Dimna transmission is owned by fable-w01 (#22) and fable-w07 (#11,#22), so the verse-Kalila point is folded into the Rudaki item and no standalone Kalila/Sindbad-nama item is posed. Safa's Tarikh-i adabiyat and de Blois' Bio-Bibliographical Survey are reused as census controls under attested-poet/attested-title operations distinct from the minds-w02 Nizami dated-ms count. NOTE cleared: the 'Mu'jam' in islamicate-openiti (#4) is Yaqut's geographical Mu'jam al-buldan, a different work from Shams-i Qays's prosody al-Mu'jam used here - no collision. DROPPED CANDIDATES: (a) Nizami's own lists / khamsa-imitation chains of lost romances - dropped as Nizami is owned by minds-w02; recast as the non-Nizami verse-romance census (item 12). (b) A standalone Sindbad-nama / verse-Kalila item - dropped, prose Kalila owned by fable-w01/w07; the verse-Kalila loss folded into item 1. (c) A raw-bayt genre-size comparison (three Ghaznavid panegyrists vs one lyricist) - dropped as FALSE on the numbers (Farrukhi's surviving divan alone is large), replaced by the within-Ganjoor pre-Mongol survival-concentration op (item 6). (d) A smooth recency-gradient census - replaced by the mechanistic Mongol-caesura step (item 4). CONFIDENCE FLAGS carried inside the items: Rudaki's 100,000-couplet attestation and 'Unsuri's ~30,000-bayt divan are classical topoi (kept out of the load-bearing clauses, which rest on the hard surviving counts); the exact women-poet roster and the Khayyam cross-attribution magnitude are MODERATE and primary clauses are phrased to survive the uncertainty.

Novelty / leakage triage

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

Half the conjunction is settled in print: no complete text of any of the three romances exists anywhere - Vamiq u 'Adhra survives as fragments recovered from a binding (M. Shafi's Lahore find, re-edited in Hagg-Utas), Khing-but u Surkh-but and Shadbahr as titles and stray lines - so the zero-complete-romance clause is guaranteed a fortiori for Ganjoor. The divan half is not: the tazkira topos of tens of thousands against a slim survivor is stated qualitatively everywhere, but the surviving divan's printed extent sits near the 3,000-bayt threshold and no source tabulates the Ganjoor count, so the compound primary clause as a whole is un-run rather than leaked.

Sources cited by the triage

F. de Blois, Persian Literature: A Bio-Bibliographical Survey, vol. V (2nd rev. ed., London, 2004), s.v. 'Unsuri, on the divan and the three romance titles
T. Hagg and B. Utas, The Virgin and her Lover: Fragments of an Ancient Greek Novel and a Persian Epic Poem (Leiden, 2003), the Vamiq u 'Adhra binding fragments after M. Shafi's Lahore 1967 edition
Divan-i 'Unsuri, ed. M. Dabir-Siyaqi (Tehran, 1342sh/1963)

Predictions

Killed registered 2026-07-19 variant: v1 calibration prediction (parent triage: leaked/adjacent)

Resolution: Killed

Caveats: KILLED ON THE FIRST LIMB OF ITS OWN CONJUNCTION - the number died while the mechanism it was meant to capture was resoundingly confirmed; the caveats carry both facts at full weight. (a) THE KILL: the registered SUPPORTED clause was a conjunction - divan under 3,000 bayt AND no complete romance text - and the divan came in at 3,781 bayt on a complete, triple-cross-validated enumeration (distinct coupletIndex, floor(verses/2), and sections coupletsCount agreeing 480/480; zero estimation anywhere in the number). 3,781 >= 3,000, so clause (2) fails and the registered REFUTED clause fires mechanically. Per house discipline (MT/Tur v2, cdli) the pin is honoured as pinned: re-litigating a self-chosen absolute threshold the moment it lands unfavourably would gut pre-registration. (b) NO ARITHMETIC ESCAPE - stated so no one can accuse the house of wishing: the pinned op counted the poet-62 FULL tree, which includes categories a stricter 'divan proper' reading might contest - the 111-bayt اشعار منسوب (attributed) category, the 265-bayt scattered-qasida-fragment category, and the 182 scattered masnavi bayt (mutaqarib 111 + khafif 70 + 1 on the parent node). Strip every one of them and the remainder is qasidas 3,069 + ruba'iyat 154 = 3,223 bayt - still over the pin. No defensible reading of 'divan' brings Ganjoor's Unsuri under 3,000; the kill does not hang on the contestable categories. (c) MECHANISM CONFIRMED: the conjecture's substantive claim - institutionally-anchored court panegyric survives while verse romance dies - is plainly present in the data. 81.2% of surviving Unsuri is qasida (3,069 of 3,781); all three attested romances (Vamiq u Adhra, Khing-but u Surkh-but, Shadbahr) show ZERO complete text not just under poet 62 but anywhere on the 233-poet roster; and the sweep's sole title-level hit is 11 bayt inside Jami's Salaman u Absal - a different poem by a different poet more than four centuries later, in which Vamiq figures as a stock exemplar of the seeker, containing not one line of Unsuri's own text. The registered 1,000-couplet completeness floor proved generous in both directions exactly as designed: largest known witness anywhere (the Lahore Vamiq u Adhra binding fragments) ~372 couplets; largest found on this roster, 11. The poet-62 tree even carries the predicted fragment stratum itself - 182 scattered masnavi bayt in mutaqarib and khafif, the wreckage of the lost masnavis, present, counted, and sub-floor as foreseen. (d) CALIBRATION - THE PROSE WAS RIGHT AND THE PIN WAS WRONG, the sharpest instance yet: the prediction's own prose clause ('under one third of the ~30,000-bayt tazkira topos', i.e. under ~10,000) was met with 2.6x headroom - 3,781/30,000 = 12.6% - while the registered hard pin at 3,000 missed by 26%. This extends the standing calibration finding beyond multiplicative-ratio overshoots (MT/Tur v2: wagered 10x, the world delivered 9.4x) to aggressive absolute pins: the registrant converted a comfortably-true prose claim into a needlessly tight absolute number and died on the tightening, not on the claim. File in the calibration series as the absolute-pin extension. (e) SWEEP SOFTNESS CANNOT RESCUE THE VERDICT: the roster-wide romance sweep was the recipe's disclosed search-endpoint fallback, not an exhaustive 233-poet tree crawl, so its negative is best-effort. Weighed honestly, a hiding >= 1,000-couplet romance is remote: a complete text under the romance's own title would almost certainly surface, since its hero's name saturates its body text, all 3,253 body-text rows for the 7 pinned terms had title AND breadcrumb checked (ZWNJ/space-normalized), and a titled parent category rides into the breadcrumb of every surfaced member poem; while a complete text under a title containing NO pinned string falls outside the registered definition of romance presence ('under the romance's title anywhere on the roster') in the first place. The residual gap is search-index lacunae only. Note the guard direction: this softness sits entirely on the limb that PASSED - a missed romance would flip the second limb to failure and make the kill doubly decisive - so the sweep's best-effort character can only strengthen, never soften, the verdict; the limb that killed rests on the COMPLETE enumeration. (f) NO V2 CHASE: re-registering at a looser pin (say <4,000) now, with 3,781 in hand, would be threshold-shopping - precisely what register-before-compute exists to prevent. The shepherd recommends leaving this killed and routing the two reported-non-verdict findings - the 12.6% survival ratio against the topos, and the romance-extinction confirmation (max continuous title-level fragment on the roster: 11 bayt, and it is not even Unsuri's) - into the calibration essay and the laureates-fraction finding respectively.

Registered against the Ganjoor public API, api.ganjoor.net (instrument verified at registration 2026-07-19: robots.txt on both ganjoor.net and api.ganjoor.net reads 'User-agent: * / Disallow:' (blank) = fully permitted, no crawl-delay; GET /api/ganjoor/poets returned 200 with 233 poets; poet عنصری بلخی confirmed present, id=62, fullUrl /onsori - roster metadata only, no verse data fetched). PREDICTION VERBATIM: "Prediction: the total bayt count of the Unsuri (عنصری) divan on Ganjoor will be under one third of the divan size the tazkira tradition reports for him (a reported figure on the order of 30,000 bayt, flagged here as a soft topos), and each of his three attested verse romances - Vamiq u Adhra, Khing-but u Surkh-but, Shadbahr - will have zero complete text on Ganjoor (primary clause, resting on the hard surviving counts: the Ganjoor Unsuri divan under 3,000 bayt AND no complete romance text; the reported-total ratio is the corroborating figure). Romance survival is scored on complete text; surviving fragments do not count as presence." FULL OPERATIONALIZATION PINNED AT REGISTRATION: DIVAN COUNT: enumerate poet id 62's complete category tree and every poem under it via the API (endpoints documented in the compute output); bayt count per poem = number of couplets = count of distinct couplet indices if the API supplies them, else floor(verse-line count / 2), the choice documented once and applied uniformly; the DIVAN total excludes any category or poem whose title names one of the three romances (title matching any of: وامق, عذرا, خنگ‌بت, خنگ بت, سرخ‌بت, سرخ بت, شادبهر) - such material is evaluated under the romance clause instead. ROMANCE CLAUSE: a romance counts as having 'complete text on Ganjoor' only if a continuous text of at least 1,000 couplets appears under that romance's title (under poet 62 or anywhere in the poet roster, swept by category-title match on the same strings). The 1,000-couplet completeness floor is the registrant's ex-ante pin of the prediction's own 'fragments do not count' rule, justified before compute: the romances are attested as multi-thousand-couplet works, and the largest known surviving witness (the Vamiq u Adhra binding fragments, M. Shafi's Lahore find) runs about 372 couplets, so the floor separates any genuine complete text from every known fragment by a wide margin in both directions.

Resolution criteria — the registered fine print

Resolution criteria: COMPUTE RECIPE (blind agent): (1) GET the poet-62 category tree and all poems via api.ganjoor.net (sequential, >=1s self-imposed spacing; document endpoints and counts); (2) compute the divan bayt total under the pinned exclusion; (3) sweep for romance-titled categories/poems (pinned title strings) under poet 62 and across the roster's category titles; measure any hit's continuous couplet extent. CLAUSE PRECEDENCE: (1) INCONCLUSIVE_BY_ACCESS if poet 62's corpus cannot be enumerated via the API; (2) SUPPORTED if divan bayt total < 3,000 AND no romance shows a continuous text of >= 1,000 couplets; (3) REFUTED otherwise (either divan >= 3,000 bayt, or a complete romance text found). REPORTED, NON-VERDICT (the prediction's own framing: 'the reported-total ratio is the corroborating figure'): the ratio of the measured divan total to the ~30,000-bayt tazkira topos, and the extent of any romance fragments found below the floor. Compute firewalled from thresholds and direction.

Known-priors disclosure — what the registrant already knew

Known priors disclosure: Triage 2026-07-17 graded ADJACENT with the split stated plainly: the zero-complete-romance half is settled in print a fortiori (de Blois s.v. 'Unsuri; Hagg-Utas 2003: Vamiq u Adhra survives only as binding fragments, Khing-but u Surkh-but and Shadbahr as titles and stray lines) - that half is close to leaked and is registered only because the prediction's primary is the CONJUNCTION with the live divan half; the divan half is genuinely un-run: 'the surviving divan's printed extent sits near the 3,000-bayt threshold and no source tabulates the Ganjoor count' (triage's words). Wave confidence flag (breadth_w2_confidence_flags): the ~30,000-bayt figure is a soft tazkira topos - the prediction itself flags this and rests the verdict on the hard counts. REGISTRANT'S PRIOR (disclosed): modern editions of the divan (Qarib; Dabir-Siyaqi 1342sh) are commonly reported in the high-2,000s-to-low-3,000s of abyat, and Ganjoor's transcription can sit on either side of 3,000 - the primary is at genuine risk in both directions; the registrant did not look up any count at registration. CALIBRATION NOTE: absolute-count and existence pins, not the overpinned multiplicative class. PROBE DISCLOSURE: only the poet roster endpoint was fetched; it carries no bayt counts.

Method and dataset — how it was measured

Register-before-compute honoured and verified read-only: prediction persianate-ganjoor-005-the-laureates-fraction v1 sits in the DB with registered_at = 2026-07-19T11:23:15.496843+00:00; the firewalled blind compute produced its artifact at 2026-07-19T12:00:32.608361+00:00 - computed_at postdates registered_at by 37 minutes (rule 6 satisfied). Registered clause precedence applied mechanically: (1) INCONCLUSIVE_BY_ACCESS not triggered - the compute judges poet-62 enumeration COMPLETE (full tree walk, de-duplicated poem-id set of 480, no missing or erroring nodes); (2) SUPPORTED requires the conjunction [divan bayt total < 3,000] AND [no romance shows continuous text >= 1,000 couplets] - the romance limb HOLDS (roster-wide maximum continuous title-level text = 11 bayt) but the divan limb FAILS at 3,781 >= 3,000; (3) REFUTED fires. House verdict enum maps REFUTED to killed; the pin is honoured as pinned per the MT/Tur v2 and cdli precedents.

Dataset: Live api.ganjoor.net enumeration, 2026-07-19 (503 polite sequential requests, all HTTP 200): poet 62 (عنصری بلخی, /onsori) category tree walked exhaustively - 8 nodes (root plus قصاید, رباعیات, قطعات و ابیات پراکندهٔ قصاید, ابیات پراکندهٔ مثنویها with its بحر متقارب and بحر خفیف children, and اشعار منسوب), 480 unique poems, zero duplicates, every leaf confirmed childless. Bayt = distinct API-supplied coupletIndex per poem, cross-validated per poem against floor(verses/2) and sections[].coupletsCount: all three methods agreed 480/480. Divan total 3,781 bayt (qasidas 3,069; ruba'iyat 154; qata'at/scattered qasida lines 265; scattered masnavi lines 182 = 1+111+70; attributed 111). The 7 pinned romance-title strings matched zero poet-62 categories or poems at three separate checkpoints, so the registered exclusion filter removed nothing. Roster-wide romance sweep (233 published poets) via the full-text search endpoint per the recipe's documented fallback - 7 terms, PageSize=-1 verified uncapped, 3,253 raw body-text rows, every hit's title AND full breadcrumb checked with ZWNJ/space normalization: exactly ONE title-level hit, Jami (poet 24), هفت اورنگ » سلامان و ابسال section 59 ('حکایت گفتن وامق...'), 11 continuous bayt.

computed 2026-07-19

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.