summaryrefslogtreecommitdiff
path: root/data
diff options
context:
space:
mode:
Diffstat (limited to 'data')
-rw-r--r--data/ef/expected-divergences.sexp21
1 files changed, 21 insertions, 0 deletions
diff --git a/data/ef/expected-divergences.sexp b/data/ef/expected-divergences.sexp
index d6cbc5b..60c4886 100644
--- a/data/ef/expected-divergences.sexp
+++ b/data/ef/expected-divergences.sexp
@@ -87,6 +87,27 @@ VERDICT, split by the SAME 138-row population, not two entries: on the 119 rows
Gated on the literal date window (month=12, day in {29,30,31}) AND colitur's own slug family (`nativity_octave_day_slugs`) AND `subset diffs [ Slug_f; First_f; Gospel_f ]` (widened this task from the exact-match `diffs = [ Slug_f ]` the pre-citation-comparison entry used -- narrowing back to exact-match would have silently re-excluded the very citation divergence this task exists to surface). Derived directly from the OCaml comparator's own failure output (test_layer_c_counts_match_citations), not hand-counted first and cross-checked after: 138. NARROWED (Nativity-Octave fix, 2026-08-18): 138 -> 119. Nineteen of these days are 26-28 December, which colitur now builds as days WITHIN the Octave of the Nativity (RG 67) rather than generic Christmastide ferias, so their temporal identity -- and with it their divergence shape -- changed. Not a re-adjudication: the same RG 69 disagreement on the days that remain. VERDICT CLOSED 2026-08-18, open -> colitur, because the defect this entry named was FIXED rather than re-argued. The note above splits the old 138 rows into 119 weekday rows, where it already recorded colitur's citation as CONFIRMED CORRECT and said verdict colitur would be accurate for that subset alone, and 19 Sunday rows where colitur emitted the weekday formulary in defiance of RG 69 and was plainly wrong -- a genuine Temporal_ef defect it deliberately left out of scope. Temporal_ef now excludes Sundays from the octave-day branch (register 6.17, confirmed against the oracle: missalemeum shows Sunday in the Octave of Christmas on 2035-12-30 where colitur showed a feria), so those 19 rows no longer occur at all and the count fell 138 -> 119 -- exactly the population this note had already enumerated by date. What remains is only the subset this entry itself certified correct: colitur says the Missal's own Diebus infra octavam formulary, lectio falls back to whichever civil Sunday precedes the date. Verdict colitur, on the reasoning already written here rather than on anything new. NARROWED, not closed, 2026-08-18: still 119 rows, but the CAUSE has halved. lectio now serves the Missal's own 'Diebus infra octavam Nativitatis Domini' Mass on 29-31 December (Titus 3:4-7 / Luke 2:15-20) instead of falling back to the Sunday's, so First_f and Gospel_f no longer differ on any of these days -- what remains is Slug_f alone, colitur's ef-nativity-octave-day-N against lectio's ordinary ef-christmas-N-weekday. That is naming, not disagreement: the two engines now read the same Mass on the same day. This entry's own gate already admits a Slug_f-only subset, which is why the count did not move even though the substantive half of the divergence did.")
(expected_rows 119))
+ ((id C39)
+ (citation "RG 33, primary text, docs/research/LT.txt: \"Vigilia II aut III classis penitus omittitur, si occurrat in dominica quavis, aut in festo I classis, vel si festum cui praemittitur in alium diem transferri aut ad commemorationem reduci contingat\" -- \"A vigil of the II or III class is entirely omitted if it occurs on any Sunday whatsoever, or on a feast of the I class, OR IF THE FEAST IT PRECEDES happens to be transferred to another day or reduced to a commemoration.\" The third clause is the one at issue; RG 34 places the feast on the day after its vigil, which is how the rule is evaluated. Register ยง6.31.")
+ (verdict colitur)
+ (note "colitur implements all three of RG 33's omission triggers; lectio implements the first two only. On these 10 days the vigil's own weekday is unremarkable -- it is the FEAST that fails to keep its day, either transferred away under RG 96 or reduced to a commemoration under RG 94 -- so lectio still emits the vigil and colitur omits it entirely.
+
+Two shapes, both in the rubric's own words. SIX rows are 'ad commemorationem reduci': 10 August falls on a Sunday, the II-class Sunday outranks St Lawrence's II-class feast (RG 15), the feast is commemorated rather than celebrated, and the vigil of 9 August goes (2008, 2014, 2025, 2031, 2036, 2042). FOUR are 'in alium diem transferri': the Sacred Heart takes 24 June, the Nativity of St John the Baptist transfers under RG 96, and its vigil of 23 June goes (2022, 2033, 2038, 2044). 6 + 4 = 10, each date checked against the comparator's own output rather than apportioned by hand.
+
+Domain-wide this clause fires on 1 744 of the 3 074 246 days in 1583-9999 -- 1 199 St Lawrence, 347 St John the Baptist, 198 Sts Peter and Paul -- measured by diffing a pre-change binary against HEAD over the whole domain and classifying every changed day: three shapes, zero unexplained, and every one independently re-checked to confirm the feast really is absent from its own day.
+
+CORRECTED 2026-08-21, BEFORE THIS ENTRY WAS EVER REVIEWED: an earlier version of this note claimed the published Ordo -- the project's one witness outside the Divinum Officium -> missalemeum -> lectio lineage -- INDEPENDENTLY CONFIRMS colitur here, because it omits St Lawrence's vigil on 2025-08-09 where both software engines keep it. That claim does not survive its own check and is withdrawn. The Ordo covers 2024-2027 and omits that vigil on BOTH 2025-08-09 (where this clause says omit) and 2027-08-09 (where it says keep, 10 August being a Tuesday); 2026-08-09 is a Sunday, omitted by the rule's FIRST trigger anyway, and the fixture has no row for 2024-08-09. So the Ordo never shows St Lawrence's vigil on any date it covers, and its agreement on 2025-08-09 is a coincidence of a blanket gap, not evidence of the third trigger. The Ordo has nothing to say here in either direction. Recorded rather than quietly deleted because the withdrawn claim was the reason this entry was first written up as unusually well corroborated, and a reader who saw that framing should be able to see it retracted.
+
+INDEPENDENTLY CONFIRMED AT THE RULE LEVEL (2026-08-21), after the Ordo claim above was withdrawn and the question 'can these be checked against an outside source' was put again. O'Connell, The Celebration of Mass (4th ed., 1964), docs/research/oconnell/oconnell-1964.txt:2626-2629 -- a published rubrics commentary contemporary with the 1960 Code, outside the Divinum Officium -> missalemeum -> lectio lineage and independent of the Missal scans, already cited in this project for RG 128: 'A vigil of II or III class is entirely omitted if it falls on any Sunday, or on a feast of I class, OR IF THE FEAST WHICH IT PRECEDES IS TRANSFERRED TO ANOTHER DATE OR HAPPENS TO BE REDUCED TO A COMMEMORATION.' That is RG 33's three triggers in English, the third included, from a source that is neither the primary text this engine transcribes nor any engine derived from it.
+
+The same passage independently confirms vigil_feast_table's exact membership, which is the other thing no type can check: I class are Christmas Eve and Pentecost ('these take precedence of all feasts and admit no commemoration' -- RG 30, and why they are excluded from the table); II class are 'the eves of the feasts of the Ascension, the Assumption, the birthday of St. John Baptist (June 24), and SS. Peter and Paul (June 29)'; and 'there is only one vigil of III class, ie., the eve of the feast of St. Laurence (August 10)'. Five vigils, the same five, with the same class split the table encodes.
+
+WHAT IT DOES NOT DO is witness the 10 DAYS. O'Connell states the rule; he publishes no day-by-day calendar, so the individual dates rest on the rule plus colitur's own occurrence machinery. The distinction is kept deliberately, because collapsing it is exactly the error the withdrawn Ordo paragraph above made.
+
+WHAT THIS ENTRY ALSO RESTS ON. Two things, neither of them a day-level witness. FIRST, the primary text, which admits no interpretive latitude: RG 33 joins three triggers with 'vel'/'aut' and the third is a plain conditional on the feast's own fate. SECOND -- and this is the substantive point -- lectio does not DISAGREE with the clause, it never evaluates it. 'RG 33' appears nowhere in lectio's production code, only in one test file's comments; its Sunday behaviour is emergent from ordinary rank comparison (a II-class Sunday outranks a III-class vigil), not from a transcribed rule. The third trigger cannot emerge that way at all, because it turns on what is observed the day AFTER, and a per-day precedence contest has no access to it. That is exactly why implementing it in colitur required a whole-year pass and a new field on Precedence.rules rather than a branch in disposition. So the divergence is architectural, not exegetical: on these 10 days lectio is not asserting that the vigil survives, it is producing the only answer its shape can produce. missalemeum and Divinum Officium inherit the same limit by lineage.
+
+Gated on lectio's own slug being one of the three vigils this clause can reach and colitur's not being a vigil -- identity on both sides, not a diff-set shape. The Assumption's and the Ascension's vigils are absent from that list because their I-class feasts always keep their own day: 0 occurrences across the whole domain, measured rather than assumed.")
+ (expected_rows 10))
; C8 -- CLOSED, REMOVED (2026-08-18): 0 of 16801 rows, was 26. lectio builds
; Rogation Monday and Tuesday now (RG 87, Easter+36/+37, violet under
; RG 128(d)). The Wednesday is NOT built there and deliberately so: Easter+38