Resolution: Killed
Caveats: Killed mechanically on the registered clause precedence, and the honest weights all point the same way. (1) THE KILL IS TOTAL, NOT A NEAR-MISS: SUPPORTED required singleton_share_R >= 2 x singleton_share_A = 0.7726; observed R = 0.3903 vs A = 0.3863 - ratio 1.0103 against a 2.00 pin, a 1.98x shortfall. Every previous multiplicative kill in the calibration series was a direction-right magnitude-miss; this one is not even that in substance: the realized separation sits at parity (R above A by 0.40 percentage points), the nearest-to-null observation the series has produced. The wagered structural effect - the great responsory as a dramatically thinner-transmitted repertory than the antiphon - is absent from this instrument, not attenuated. (2) NO DIRECTIONAL REMNANT SURVIVES: the primary clause's sign is nominally satisfied (R 0.4pp above A) at a magnitude with no evidential weight, and the companion clause - R median breadth 'lower than A by a wide margin', registered ex ante as report-only because unquantified - finds identical medians of 2.0 sources. The full distributions agree end to end: 2-source share A 15.13% vs R 14.56%; deep-tail 20+-source share A 20.19% vs R 20.44% (the conjecture named the great responsory 'the deep tail'; the actual deep tail is genre-flat too, and marginally R-heavy at the top rather than R-thin). No reading of this artifact leaves a directional claim worth carrying forward. (3) SINGLETON SHARE LOOKS LIKE CORPUS STRUCTURE, NOT GENRE (bounded claim): the two genre shares sit 0.40pp apart and both within ~3.2pp of the corpus-wide 41.79% share the house had measured on this same dump before registration (disclosed in known_priors), while the same prior compute's office-CLASS strata varied enormously (Mass 38.4%, Office-hours 44.2%, office-blank 72.9%). On this instrument, breadth varies along cataloguing/coverage axes and is flat across the one genre axis now measured - consistent with cross-source concordance breadth in Cantus being a property of which sources the member databases have indexed, not of a chant's liturgical genre. Scope discipline: this is measured for A vs R, within office scope, on one frozen dump covering ~84.9% of the live network; 107 other genre codes are untested and no claim about genre in general is licensed by this artifact. (4) NO REGISTERED-CONSISTENT READING REACHES THE BAR: a flip to SUPPORTED needs +2,193 R singletons (2,238 -> 4,431 of 5,734, holding A fixed) or -2,385 A singletons (4,818 -> 2,433, holding R fixed); the disclosed method degrees of freedom move IDs in the single digits to low hundreds. (a) Source column: srclink is the only shared column that actually keys into sources.csv (strict 1:1, 2,278/2,278, zero orphans either direction) and is therefore the registered 'source-identifier column'; the rejected alternative siglum carries just 5 duplicated values, so even that off-reading could collapse at most 5 source pairs and mint at most a handful of new singletons across both genres. (b) The mid-run tie-vs-merge precedence fix touched exactly 5 IDs and the post-fix exclusion partition was verified exact over all 53,282 IDs; any alternative handling of those 5 moves the shares in the fourth decimal place. (c) The office-fold choice (offices of merged-away verse suffixes not folded into stems; recipe-silent, stated by the compute) could only churn membership at the MASS boundary - and the artifact's own figures imply office scope excluded zero R IDs at all (R's stated pre-office-scope total, 5,734, equals its final n), so the choice had no purchase on the R side. (d) The exact-code genre reading ('A'/'R'; compound codes like InR, CmR, RSV not folded in) is what the registration's 'the value carried by a strict majority of its non-blank genre-column rows' pins; folding compounds would measure a different population, not a reading of this registration. (e) Even the maximally adversarial OFF-recipe stack - counting all 411 excluded genre-ties as R singletons - yields R share 0.4311 and ratio 1.12. Nothing available on this instrument closes to within a factor of ~1.8 of the pin; the outcome is not method-fragile. (5) THE VERSE-MERGE ASYMMETRY CUTS TOWARD A, AND R STILL ONLY TIED: by the prediction's own rule, only R stems union in verse-suffix sources (5,422 of 5,734 R IDs received at least one merged verse; every realized chain 1-deep). That construction can only raise R breadth and depress R's singleton share, so the single degree of freedom with nominal headroom toward the pin is UN-merging the verses - a reading forbidden by the prediction's verbatim text ('verses are counted with their responsory') and by the pinned merge op. The artifact does not report the pre-merge share, so the merge's realized effect is unmeasured; what is bounded is the direction (merging can only lower R's singleton share, i.e. the construction was, if anything, generous to A in this comparison - and R's share still came out above A's, by a hair), and the scale a rescue would need: even a total off-recipe un-merge would have to convert ~2,193 R stems back to singletons, i.e. roughly 40% of all merged stems owing their entire multi-source status to verse-contributed sources alone - a regime nothing in the artifact suggests. The asymmetry is the registration's own construction and grounds no grievance against the kill. (6) GUARDS, INTEGRITY, ORDERING: both sha256 hashes matched the registration exactly (verified twice, byte sizes matching the release listing); the 500-item design floor cleared by 11.5x on the thinner genre; registered_at 2026-07-19T11:23:15Z (status open, no prior resolution row, is_calibration=True under the leaked/adjacent triage rule), artifact computed_at 11:52:16Z the same day - ordering verified read-only in the DB. (7) CALIBRATION: the sixth multiplicative-magnitude pin to die (>=3:1 at 1.69, >2x at 1.28, <1/3 at 0.87, 10x at 9.4, >=5x at 3.78, now >=2x at 1.01) and the first in which the underlying effect is absent rather than undershot. The registration saw the arithmetic in outline and wagered anyway with disclosure: known_priors stated that a 2x separation atop a ~44% pooled office share needs something like A near 35% / R near 70%, and flagged the multiplicative class as the house's historically overpinned one. The lesson sharpens accordingly: earlier multiplicative kills were correct mechanisms with overconfident magnitudes; here the proposed mechanism (proper offices multiplying responsories into single-source depth) simply does not register in the measured corpus at any magnitude. No v2 chase: re-registering on another genre pair, another corpus, or a folded-code population after seeing genre-flatness would be threshold-shopping; if the breadth-is-coverage-structure observation in (3) is worth pursuing, it should be posed as its own ex-ante conjecture, not as a rescue of this one.
Registered against the frozen CantusCorpus v1.0 dump of the Cantus Index network (github.com/dact-chant/CantusCorpus, release tag v1.0, chants.csv, sha256 9c34b2de342cbb668fbc8883fe56e7a598f18e0b4f6637358421e47f888a19de) - the same house-validated instrument used by compute_cantus_singleton_20260718, which live-spot-checked its distinct-source counts against cantusindex.org JSON with 5/6 exact matches; asset re-verified live at registration 2026-07-19 (HEAD 200, 246,554,665 bytes). Pinning the frozen dump rather than a cantusindex.org crawl is the politeness-optimal route (one download versus tens of thousands of Crawl-delay-10 requests) and freezes the edition (lesson 3). PREDICTION VERBATIM: "Prediction: in Cantus Index, the median cross-source concordance breadth of great responsories (genre R) is lower than that of antiphons (genre A) by a wide margin, and the single-source share among great responsories is at least twice the single-source share among antiphons (primary clause: the at-least-2x responsory-over-antiphon singleton share; the verdict follows it). Genre is read from the Cantus genre field and verses are counted with their responsory; coverage guard: the comparison is within the office to hold repertory scope fixed, and the test voids if genre-tagged source-count data is available for fewer than 500 items per genre." FULL OPERATIONALIZATION PINNED AT REGISTRATION: UNIT = distinct cantus_id in chants.csv. SOURCE COUNT = number of distinct values of the source-identifier column per cantus_id (the identical grouping used by compute_cantus_singleton_20260718; the compute names the column and confirms it keys to sources.csv, sha256 175043250b1cd8d29c2f23de991733d8926d8b41d6ddeadf9601e58076a06e4b). GENRE ASSIGNMENT (pinned): an ID's genre = the value carried by a strict majority of its non-blank genre-column rows; ties and all-blank IDs are excluded and their counts reported. VERSE MERGING (the prediction's own rule): any cantus_id consisting of a stem plus one trailing letter a-z, whose stem is itself an ID in the corpus with assigned genre R, has its distinct sources unioned into the stem's source set and is not counted separately; suffixed IDs whose stem is absent or non-R are ordinary IDs under their own genre, except genre-V (verse) IDs not attachable to any R stem, which are excluded and reported. OFFICE SCOPE (pinned realization of 'within the office'): after genre assignment, exclude any ID all of whose non-blank office-column values are 'MASS'; IDs with blank office columns are retained (their A/R genre is the scope evidence; several member databases leave office blank). QUANTITIES: for g in {A, R}: singleton_share_g = share of genre-g IDs with exactly one distinct source after verse-merging; also median breadth per genre (reported).
Resolution criteria — the registered fine print
Resolution criteria: COMPUTE RECIPE (blind agent): (1) download chants.csv and sources.csv from the pinned v1.0 release; verify both sha256 hashes match the registration; (2) build per-ID distinct-source counts; (3) apply the pinned genre-assignment, verse-merging, and office-scope rules exactly as registered; (4) compute singleton_share_A, singleton_share_R, and the two medians. CLAUSE PRECEDENCE: (1) INCONCLUSIVE_BY_ACCESS if the pinned files cannot be obtained hash-intact; INCONCLUSIVE_BY_DESIGN if fewer than 500 qualifying items remain in either genre (the prediction's own void; the dump holds tens of thousands of A and R items, so this guard should be nowhere near binding); (2) SUPPORTED if singleton_share_R >= 2 x singleton_share_A; (3) REFUTED otherwise. REPORTED, NON-VERDICT: the median-breadth comparison (the prediction's 'by a wide margin' is unquantified, so it is reported, not adjudicated - stated here ex ante), the full per-genre breadth histograms, and the excluded-ID counts (ties, orphan verses, MASS-only). Compute firewalled from thresholds, directions, and the house's prior corpus-wide results.
Known-priors disclosure — what the registrant already knew
Known priors disclosure: Triage 2026-07-17 graded ADJACENT: CAO III/IV register sizes and Hughes' LMLO make the responsory repertory's bulk visible in print, and Helsen 2008 analyzes responsory transmission, but no genre-stratified source-count comparison exists. HOUSE PRIOR (material, disclosed): compute_cantus_singleton_20260718 measured, on this exact dump, the corpus-wide singleton share 41.79% (53,282 IDs) and an office-class breakdown (Mass 38.4%, Office-hours 44.2%, office-blank 72.9%, mixed 0.2%) - but NO genre stratification; the R-vs-A split the verdict rides on is unknown to the registrant. Note the base-rate arithmetic the registrant cannot avoid knowing: with the pooled office singleton share near 44%, a 2x separation requires R and A to sit far apart (e.g. A near 35% and R near 70%) - the pin is aggressive relative to the pooled figure, which is exactly what makes it a live wager. COVERAGE CAVEAT (disclosed): the dump covers ~84.9% of the live network's current master-chant IDs (scraped 2025-05-20, 10 of 11 member databases); the registered measurement is of the frozen dump by design. CALIBRATION NOTE: the verdict clause is a MULTIPLICATIVE >=2x pin - the historically overpinned class (3:1 died at 1.69, 2x died at 1.28, 10x died at 9.4x; proportion pins held). Registered faithfully per the anti-threshold-shopping rule; selection accepted the risk because the two genres' singleton shares are structurally, not marginally, separated if the conjecture's mechanism (proper offices multiply responsories) is real.
Method and dataset — how it was measured
Mechanical application of the registered clause precedence to the blind compute artifact (docs/generated/compute_cantus_responsory_20260719.json), with arithmetic independently re-verified from the artifact's raw histogram counts (A: 4,818/12,472 = 0.386305; R: 2,238/5,734 = 0.390303; both histograms sum exactly to their n; medians re-derived from the cumulative histograms = 2.0 for both genres). (1) INCONCLUSIVE_BY_ACCESS not triggered: both pinned sha256 hashes verified intact (twice, per the artifact; byte sizes match the release listing). INCONCLUSIVE_BY_DESIGN not triggered: 12,472 and 5,734 qualifying items, both >= the registered 500-item floor (the thinner genre clears by 11.5x). (2) SUPPORTED requires singleton_share_R >= 2 x singleton_share_A = 0.772611; observed singleton_share_R = 0.390303 (ratio R/A = 1.010350). Not met. (3) The registered REFUTED clause fires => verdict 'killed' (house enum). Pre-registration ordering verified read-only in the DB: ConjecturePrediction (conjecture slug liturgy-cantus-011-the-great-responsory-is-the-deep-tail, variant_key v1) registered_at 2026-07-19T11:23:15.496843+00:00, status open, no prior resolution row, is_calibration=True; artifact computed_at 2026-07-19T11:52:16.142412+00:00 strictly postdates it by 29m01s. The registered non-verdict reports (median comparison, full histograms, exclusion counts) are carried in computed_values and weighed in the caveats. prompt_hash convention: SHA-256 hex over the UTF-8 bytes of the resolution brief from the '## The registration' header line through the final line of the '## Your task' section ('...Decide the verdict yourself per the registered mapping.'), headers inclusive, reproduced verbatim as 8 lines (3 section headers, 3 one-line section bodies, 2 blank separator lines), every line including the last terminated by a single LF.
Dataset: Frozen CantusCorpus v1.0 dump of the Cantus Index network (github.com/dact-chant/CantusCorpus, release tag v1.0), the politeness-optimal instrument pinned at registration (one release download vs tens of thousands of Crawl-delay-10 requests; covers ~84.9% of the live network's master-chant IDs per the disclosed coverage caveat, scraped 2025-05-20, 10 of 11 member databases). chants.csv: 246,554,665 bytes, 888,010 data rows, 53,282 distinct cantus_ids, sha256 9c34b2de342cbb668fbc8883fe56e7a598f18e0b4f6637358421e47f888a19de verified twice against the registration. sources.csv: 307,145 bytes, 2,278 source rows, sha256 175043250b1cd8d29c2f23de991733d8926d8b41d6ddeadf9601e58076a06e4b verified twice. Source-identifier column: srclink, validated by the blind compute as a strict 1:1 key into sources.csv (2,278/2,278 distinct, 0 blanks, 0 orphans in either direction; the alternative siglum rejected for 5 duplicated values). Analysis universe after the pinned ops (strict-majority genre, R-stem verse merging, office scope): genre A (antiphon) n=12,472 and genre R (great responsory) n=5,734, drawn from an exact verified partition of all 53,282 IDs (411 genre-ties excluded, 0 all-blank, 6,670 verse-suffix IDs merged into R stems, 2,229 orphan-V excluded -> 43,972 post-merge survivors, of which 6,612 MASS-only IDs fall outside office scope).
computed 2026-07-19