From b14a3078c1a4db87010f5df955442bf1e440e0ec Mon Sep 17 00:00:00 2001 From: Lukasz Kasprzak Date: Wed, 2 Sep 2026 12:54:07 +0200 Subject: fix(of): correct ten reading references, regenerated from lectio Nine ended at verse 22 where the OLM ends them at 20; the tenth read "Matthew 17:9a,10-135", a verse Matthew 17 does not have. Every one was in a Year II entry, or in of-advent-2-saturday, which has no year cycle. Not one Year I entry was affected -- that distribution is what made this a transcription fault rather than ten independent slips. Corrected upstream in lectio's own internal/caldata/of-lectionary.ini (its suite green) and this file regenerated from it, per the header's own instruction not to hand-edit a generated artifact. The diff is exactly the source SHA-256 pin plus the ten references; both pins in test_lectionary_of.ml move with it. The Ordinary Time invariant added in the previous commit now asserts outright rather than pinning six exceptions: in Ordinary Time the OF weekday Gospel does not depend on the year of the cycle, so a -i/-ii pair whose Gospel differs is a defect, and the expected violation set is empty. Mutation-tested against the Year II entry alone -- an earlier attempt changed both halves of the pair and passed for the wrong reason, which is worth knowing about this shape of test. Measured: the 20-vs-22 divergence class against litcal goes 26 -> 0 over the twelve witnessed years. 917 tests, every year 1583-9999. Also, L6/L7 (the Sacred Heart / John the Baptist tie at an equal Tabula entry) gains the citation its note said did not exist. Tabula I.3 enumerates "Sollemnitates Domini, beatae Mariae Virginis, et Sanctorum" -- an order, not a bare category, and read that way it settles the tie against colitur's current alphabetical answer. Recorded with its counter-argument (entry 4 marks its own internal order with explicit lettering; entry 2's list cannot be an ordering at all) and with what would settle it. Verdict stays open, behaviour unchanged. --- data/of/expected-divergences-litcal.sexp | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) (limited to 'data/of/expected-divergences-litcal.sexp') diff --git a/data/of/expected-divergences-litcal.sexp b/data/of/expected-divergences-litcal.sexp index 633d2e0..a045415 100644 --- a/data/of/expected-divergences-litcal.sexp +++ b/data/of/expected-divergences-litcal.sexp @@ -139,6 +139,34 @@ ; RG 112(a) does on the EF side for a narrower case. NOT fixed here (a ; kernel-level tie-break policy is out of this task's own scope regardless ; of verdict). +; +; UPDATE 2026-08-28: a CANDIDATE citation has since been found, and it +; points AGAINST colitur's current answer. Tabula I.3 does not name a bare +; category; it enumerates one in a definite order -- "Sollemnitates DOMINI, +; beatae Mariae Virginis, et SANCTORUM in Calendario generali inscriptae". +; The Sacred Heart is a Solemnity of the Lord; the Nativity of St John the +; Baptist is a Solemnity of a Saint. Read as ordered, that entry puts the +; Lord first, litcal's answer is right and colitur's alphabetical tie-break +; is reaching a conclusion the text already settles. colitur's own EF side +; models exactly this shape already -- RG 91 entry 14's "primum mobilia, +; deinde fixa" is a within-entry order, and Precedence_ef.band expresses it +; by scaling the whole table x10 so a half-row sits between its neighbours. +; Precedence_of.band is scaled x10 too, so I.3 could carry 30/31/32 with no +; structural change. +; +; The counter-argument, which is why this stays OPEN rather than becoming a +; fix: Tabula entry 4 marks its own internal order with explicit a) b) c) d) +; lettering, so the drafters had a way to signal ordering and used it. Entry +; 3 is a plain "A, B, et C" list. Entry 2's own list ("Nativitas Domini, +; Epiphania, Ascensio et Pentecostes...") cannot be an ordering at all, +; since those days can never collide with each other -- which is evidence +; that a list inside an entry need not imply precedence. +; +; What would settle it: any authoritative source treating 24 June in a +; Sacred-Heart-collision year -- an ordo, a Notitiae reply, or a +; conference decree. The collision is rare (Easter must be late enough to +; put Easter+68 on 24 June) and none of the project's current witnesses +; covers such a year. Verdict stays open; behaviour unchanged. ((id L6) (citation "precedence.ml's compare_by (Slug.compare tie-break); no Tabula/Normae text found ranking Sacred Heart above/below the Nativity of John the Baptist at equal band") (verdict open) -- cgit v1.3