deterministic OCaml engine to compute and validate liturgical calendars for multiple rites, template-driven output to year 9999 https://git.labunix.xyz/colitur.git/atom?h=main 2026-08-22T18:55:18Z 2026-08-22T18:55:18Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-22T18:55:18Z urn:sha1:9c96e0afc19925b651e0dfee3bc9182dee72acf0 Ascension has no octave under the 1960 rubrics -- confirmed structurally: the Proprium de Tempore's own table of contents runs straight from "In Ascensione Domini" to "Dominica post Ascensionem" with no per-feria headings in between. Step 3 of the reading chain therefore fell through to Preceding_sunday on every unoccupied weekday in that stretch, walking each one back to the 5th or 6th Sunday after Easter's own citation. The Missal's own Proprium de Tempore carries an explicit marginal rubric immediately after the Ascension's Mass propers, before "Dominica post Ascensionem" begins: "Diebus a feria VI post Ascensionem usque ad feriam VI ante vigiliam Pentecostes inclusive, dicitur Missa de festo Ascensionis, cum Gloria et praefatione de Ascensione, sine Credo et Communicantes proprio" -- every feria without its own proper, from the Friday after the Ascension through the Friday before the Vigil of Pentecost, repeats the Ascension's own Mass. RG 490(b) corroborates independently: it assigns the Ascension preface "tamquam de Tempore" across that identical window, which only makes sense if the Mass actually repeated there is the Ascension's, not a numbered Sunday's (whose own Mass would carry no need for a preface override at all). Witnessed directly, not only inferred from the rubric: the LMS Ordo prints "Mass of the Ascension" literally on every affected day across all three of its fixture windows, in BOTH the tail of Ascension's own week and the following week -- ruling out the alternative reading (that the second week instead resumes "Dominica post Ascensionem"'s own Mass, which a first pass over the FIUV Ordo's own week-labelled titles could suggest at a glance; its own [praef] field for the same two dates independently reads "Ascensionis", resolving the apparent conflict). Implemented as data, not logic, matching this codebase's own established precedent for the identical RG 299 shape (the week after Trinity Sunday, data/ef/lectionary.sexp's [trinity_week_entries]): six new hand-authored entries, [ascension_week_entries] in tools/bootstrap_lectionary.ml, regenerated against a git-pinned copy of lectio's own source ini (SHA-256 verified unchanged) so the regeneration carries no unrelated drift. The window's two Saturdays are deliberately excluded -- RG 78's votive Office of Our Lady on Saturday always wins an otherwise-unoccupied Class4 Saturday first, before step 2 (this fix's own entry point) is ever reached, so an entry for either slug would be dead data. Blast radius measured in-process across the full 1583-9999 domain (throwaway probe, not committed): 16 350 days total across the six slugs, every one resolved via step 2 (Own_slug), zero anomalies, and the window's two Saturdays confirmed to contribute zero hits via this cause across the whole domain, corroborating the RG78-interception reasoning by direct sweep. Closed L2 in data/ef/expected-divergences-lms.sexp. New cited entries: C41 in data/ef/expected-divergences.sexp (95 of 16801 rows, 2005-2050 -- lectio has no equivalent rubric and still walks these ferias back); M31 in data/ef/expected-divergences-missalemeum.sexp (3 rows in the 2026-2027 window, plus the same shape independently reconfirmed in the 2035 and 2038 live-capture windows) -- missalemeum, Divinum Officium's lineage, still gives the same wrong answer colitur itself used to give, which is why these rows used to agree with M18's shape and now escape it (M18 373 -> 370, the same mechanism M23-M27 established when the citation axis was first built). Golden pin: 2031-05-23, the exact date the bug report was filed against. Mutation-tested: reverting data/ef/lectionary.sexp alone (a git-diff capture/restore, not a source-code revert, since the fix is data) reddens 19 tests across the differential, both oracle fixtures, all three LMS Ordo windows, the golden pin, the lectionary unit test and every Render golden template; restored and reconfirmed green (681 tests; 683 under COLITUR_EXHAUSTIVE_SWEEP=1, ~175s). 2026-08-18T10:11:05Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-18T10:11:05Z urn:sha1:a6daed7820a97f4032f21964b5b1bb30fe00b36b Both carried rank Class3 with status Commemoration_only, bootstrapped from lectio, which inherits it from missalemeum, which is generated from Divinum Officium. The Missal's own universal calendarium ranks both "III classis" outright, with no commemoration rubric: "S. Ubaldi Ep. et Conf., III classis" (16 May) and "S. Didaci Conf., III classis" (13 November), corroborated in the second scan and in a published 1962 Ordo. Universal by construction, not by assumption: the calendarium carries no "pro aliquibus locis" marker in its 573 lines while the wider Missal carries 79 of them elsewhere. Each saint also has his own Mass entry in the Proprium, which a bare commemoration never has -- a commemoration carries an oration only. Found by auditing ALL 290 fixed-date entries against that calendarium, day by day, anchored on the Roman calends column because the arabic day column is OCR-wrecked and the dominical-letter column vanishes in some months. These two were the only status defects in the whole file. The 15 days the automated pass could not cover were read by hand and all agree. Neither needed a proper authored: each takes its Mass from a Common with only its own Oratio proper, per its own rubric at its own date. ubaldus shares patrick's Common exactly. didacus needed one newly transcribed -- common-of-a-confessor-not-a-bishop-2, the "Altera Missa" Iustus, 1 Cor 4:9-14 and Luke 12:32-34, read independently in both scans, which agree, so the page-image third reading this file's method requires on disagreement was not triggered. Blast radius, full 1583-9999 sweep, every day classified: 13 036. That is 5 564 ubaldus observed, 7 196 didacus observed, and 276 where the Ascension Vigil still wins on 16 May but its single RG 111(c) slot passes from rogation-wednesday to ubaldus -- correct and already pinned, since the Rogation days are the MINOR Litanies and so an ordinary commemoration, which RG 113's table order ranks below a III-class feast. Cited as C38 (70 rows) and M30 (3); C8, C17 and M18 shrink accordingly, each with the reason recorded rather than the count silently adjusted. 2026-08-18T09:36:33Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-18T09:36:33Z urn:sha1:0281a846ac7c22d22990a6664a37205930a94b7d RG 128, transcribed in the rules register since 2026-08-11, gives violet to "vigils of II and III class outside Paschaltide". The Vigil of the Assumption (14 August, II class) carried White and the Vigil of St Lawrence (9 August, III class) carried Red. Both are outside Paschaltide, so both are violet. The Ascension's vigil is untouched: it is the one II-class vigil inside Paschaltide and was already correctly white. The rule had been sitting in the register, disagreeing with the shipped data, since before the data was bootstrapped. It was invisible because colitur, lectio and missalemeum all carried the same two wrong colours -- colitur was bootstrapped from lectio, lectio's ini is generated from missalemeum, and missalemeum uses Divinum Officium's data files. Three sources agreeing is one source counted three times, and the differential and the oracle both went green on the shared error. It surfaced only against witnesses outside that tree: a published 1962 Ordo flagged the Assumption's, and O'Connell, The Celebration of Mass 4th ed. (1964), section 4(c) and footnote 169, gave the general rule and with it St Lawrence's, which the Ordo omits entirely. Two golden pins added, in years where each vigil is actually observed rather than impeded. The divergence this creates against every DO-lineage source is cited in both allow-lists: C37 (lectio, 77 rows -- 92 possible minus 15 where the vigil falls on a Sunday) and M29 (missalemeum, 3 rows in 2026-2027 and 2 in each of 2035 and 2038). Both gated on the exact slugs or dates and on colour alone, so any other divergence on those days would still surface. Also recorded, no code change: rose on Gaudete and Laetare stays. RG 131 is permissive ("adhiberi possunt") and the Ordo prints violet, so the colour field carries a permission rather than a requirement on those two Sundays a year -- a decided position now, not an unexamined one. 2026-08-18T08:31:22Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-18T08:31:22Z urn:sha1:66162b52b1e7c50fa945cab34e0a184b2623967b C6 was closed by the Nativity-Octave fix rather than by argument. Its own note had already split the 138 rows into 119 weekday rows, where it 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 against RG 69 and was plainly wrong -- a Temporal_ef defect the entry deliberately left out of its own scope. That defect is fixed, and the count fell 138 to 119: exactly the population the note had enumerated by date. Verdict open becomes colitur on reasoning already written there. M26 closed on a positive argument, not an absence. Both its other shapes are now built -- the BVM Saturday Mass selection and Trinity's week -- leaving Christ the King's week. RG 299's rule has an escape clause and the escape requires an assigned proper Mass; none is assigned for that week, checked at the source, unlike Trinity's week which prints one and unlike Holy Name and Holy Family which each carry a ferial rubric. That absence is not a research gap, it is the condition that triggers RG 299's default -- and by the default the ferias say the preceding Sunday's Mass, which on this week is Christ the King's own. The limit is stated in the entry rather than glossed: this reads a printed silence as the default rather than as an oversight, which the text cannot distinguish. It is the same reading applied everywhere else RG 299 governs, and applying it inconsistently here to match an oracle already adjudicated wrong six times would be the worse error. No entry in either allow-list is now verdict open or verdict missalemeum. The only non-colitur entries are M15 and M18, both unresolvable, and both are comparator limits rather than calendar disagreements: a temporal-origin celebration carries no English name, so its identity cannot be matched even where both streams plainly mean the same thing. Register: section 6.18. 2026-08-18T08:21:39Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-18T08:21:39Z urn:sha1:e25558fee984837389d0e53cd6e17a3820f8e5ea M11 was the one entry in the missalemeum allow-list adjudicated against colitur, and it was right to be. The calendarium directs "Com. octavae Nativitatis" under each of 26, 27 and 28 December (LT.txt:5454-5459) and RG 109(c) makes a commemoration of the days within the Octave privileged. colitur emitted none. The cause was a reasoning error stated in Temporal_ef's own comment: "26-28 Dec are Stephen, John and the Innocents, hence sanctoral". Their office is sanctoral -- those II-class feasts win the day -- but they remain days WITHIN the Octave (RG 67, "Dies infra octavam sunt II classis"), and colitur built them as generic Class4 ferias. With no octave-day candidate there was nothing for the feast to be commemorated over. Building days 2-4 exactly as days 5-7 always were makes the commemoration fall out of the existing machinery rather than needing a special case: the feast wins on rank, the octave day loses, RG 109(c) privileges it, RG 111(c)'s single slot goes to it. A second, independent defect surfaced while fixing it. The octave-day branch covered 29-31 December unconditionally, so a Sunday falling there got a feria identity -- where RG 69 says a Sunday occurring 26-31 December SEMPER keeps its own office and commemorates the feast. Confirmed against the oracle rather than argued: missalemeum shows "Sunday in the Octave of Christmas" on 2035-12-30, a Sunday, where colitur showed a feria. Both named and anchors now exclude Sundays; anchors had asserted the octave slugs unconditionally and was wrong the same way. Blast radius, full sweep against the pre-change binary: 25251 days, every one 26-31 December, exactly two shapes, zero unclassified -- 21653 carrying an octave-day slug and 3598 that are all Sundays, the RG 69 correction. Allow-lists: M11 closed and removed. C6 narrowed 138 to 119, nineteen of its days having changed temporal identity rather than verdict. M15 widened 18 to 22 -- both streams now commemorate the octave, but the candidate is temporal-origin and carries no English name to match against missalemeum's own, this entry's documented limit on four more dates. Stated rather than glossed: this trades a substantive divergence, colitur omitting a commemoration the Missal directs, for a comparator limit, the commemoration existing but not being name-matchable. That is a real improvement, but what the oracle now proves is that both streams commemorate something on those days; the identity rests on the rubric and the calendarium. Register: section 6.17. 2026-08-17T20:30:58Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-17T20:30:58Z urn:sha1:59e78716e5d7b13fd33f9c0245883c83712340e6 Two open questions closed, both by looking rather than reasoning. M13 listed three possibilities for 19 March 2027 and stayed open because none was confirmed. The live one was (b): a rubric at St Joseph's own Proprium Sanctorum entry overriding the general table, "the same shape as the Annunciation's own Attamen clause", its text simply not yet found. It was looked for directly. Joseph's entry runs from its heading straight into the Introit with no rubric of any kind -- and the analogue does not exist where the note placed it either: the Annunciation's entry does the same. That exception lives in RG 96, a general rubric about transferring an impeded I-class feast, not in its propers, so there is no precedent for a propers-level override at all. With (b) eliminated and (c) still unsupported, (a) stands: RG 91 ranks a I-class feast above a III-class Passiontide feria, Joseph is not impeded so RG 96 never engages, and colitur observes him. Recorded with its limit, because this is elimination and not proof: the specific hypothesis named is false, which is weaker than showing no rubric anywhere says otherwise. Separately, the note that Mass I of the BVM Saturday needed an Advent-Saturday oracle year to corroborate it is answered: there is no such year and cannot be. Advent has no IV-class ferias -- Class2 from 17 December, Class3 before -- and RG 78 requires a IV-class feria. Zero IV-class Advent Saturdays across 2000-2100. Its single witness is not a gap in the research but the only evidence obtainable. The branch is kept: the Missal does print the Mass for Advent, RG 309's subject being Masses that may be celebrated as votive, and an overlay producing such a day would otherwise fall through silently. Register: sections 6.13 addendum and 6.14. 2026-08-17T19:45:47Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-17T19:45:47Z urn:sha1:cffb879fa124c22acd400f59152a57d20cec036f RG 78's office has been built since ef-bvm-saturday: an otherwise unoccupied IV-class Saturday is de sancta Maria in sabbato, white, IV class. The Mass stayed the feria's, so the day observed Our Lady and then read Colossians on the parable of the weeds. That is M26 shape 1. RG 309(a) is the rule -- the Masses the Missal assigns "iuxta temporum diversitatem" -- and it prints five, each under its own season heading. All ten citations are transcribed from the scans with line numbers in the source. Masses II-V were confirmed twice, against the scan and against a live missalemeum capture of 2038 which names them and agrees on both readings. Mass I rests on the scan alone: no oracle year to hand has an Advent Saturday carrying this office. One witness where the others have two, and the code says so rather than blurring it. The mapping looked like the hard part and dissolved. The Missal's ranges are cut by civil dates and movable feasts, not by this rite's seasons -- II ends mid-season at the Purification, III spans four seasons. But measured against what a IV-class Saturday can actually be, it reduces to a seasonal mapping plus one date test at 2/3 February, with no Easter arithmetic at all: III's end to IV's start leaves the Triduum unassigned, unreachable because Holy Saturday is I class; IV's end to V's start leaves Pentecost week unassigned, also unreachable because that week's Saturday is an Ember Saturday. Time after Pentecost then begins exactly at Trinity, exactly where Mass V begins. Both gaps verified by sweep -- zero IV-class Saturdays in either across 2000-2059 -- not inferred. The office is identified structurally, never off the slug, which it deliberately shares with the ordinary feria: subject Bvm, IV class, Saturday. Blast radius: 87611 reading rows over the full domain, every one a Saturday. Allow-lists: M26 27 to 6, shape 1 gone, leaving only the Christ-the-King residue argued in colitur's favour last commit. The 2038 suite's BVM-SATURDAY-MASS class is removed rather than zeroed -- an id with no rows must not be declared. M18 355 to 376. C17 widened 397 to 445, taking its own Saturdays back from C1, C19 and C25, since one cause should not be filed under two ids; C31 89 to 103; C25 closed at 0 rows, its Holy-Name-week Saturdays now answered before step 3 is reached. Three unit tests pinned the old behaviour and are corrected rather than re-pinned: two asserted the day "keeps its ferial Mass", which was the honest thing to assert while this was unimplemented. The third still tests what it always did -- that step 4 refuses a temporal office -- and only what answers instead has changed. Register: section 6.13. 2026-08-17T19:23:57Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-17T19:23:57Z urn:sha1:6e42b2f524b283f43e05a967295e244e4083725f Not the II-class feast of 15 September, which colitur has had since the bootstrap, but the other Seven Sorrows: the movable commemoration of Passion Friday, of which colitur had no trace at all. The 1962 calendarium lists it at the foot of March, below the fixed dates, exactly where a movable entry belongs (LT.txt:5056): "Feria VI post dominicam I Passionis: Commemoratio septem Dolorum B. Mariae Virg." Note the word -- Commemoratio. Under the 1960 rubrics it is a commemoration, not a feast, so it can never win the day. Friday after Passion Sunday I is Easter-9, confirmed independently by both dates the oracle allow-list already disputed: Easter 2026 is 5 April and M16's date is 27 March; Easter 2027 is 28 March and M13's is 19 March. It could not be built before Date_spec grew Easter_offset -- the same wall Rogation Wednesday hit, and the second entity that work has now unblocked. M16 is re-adjudicated and its verdict REVERSED, from missalemeum to colitur. The entry existed because colitur admitted St John Damascene where missalemeum showed the Seven Sorrows, colitur having no candidate to admit. Both streams now name the Seven Sorrows and that mismatch is gone. What remains runs the other way, and the rubric is explicit: RG 111(d) admits TWO commemorations on a III-class day, RG 113 puts the seasonal one first, and RG 114 omits only what exceeds the number. 27 March 2026 is a III-class privileged Passiontide feria; colitur admits exactly two, the Seven Sorrows and John Damascene, a real III-class universal feast genuinely falling that day. missalemeum admits one and reports John Damascene as displaced, dropping a commemoration the rubric allows. That makes four divergences adjudicated colitur where missalemeum drops or mis-assigns something -- Monica's Epistle, Perpetua's Common, Christ the King's week, and this. Recorded as a pattern rather than four coincidences: the oracle stays a comparison instrument, but its error rate on adjudicated cases is no longer negligible. M13 is untouched and stays open: 19 March 2027 is a different dispute, whether Joseph is displaced from Passion Friday at all, and on a I-class day RG 111(a) admits one privileged commemoration which the feria takes. Blast radius, full 1583-9999 sweep against the pre-change binary: 7874 days, every one carrying the new commemoration, zero unclassified, line counts equal both sides. Register: section 6.12. 2026-08-17T19:12:35Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-17T19:12:35Z urn:sha1:dcce3a5936c2232aaabbb2e8552be24ea7decdbf RG 299 located (scan1:1096-1098), which does two things at once. First it closes a standing gap: the ferial-Mass selection rule was recorded in the register as unconfirmed against the primary source, and step 3 said so in its own comment -- "lectio's own observed behaviour, not a confirmed Missal citation". It is confirmed now. "In reliquis feriis dicitur Missa dominicae praecedentis, nisi a rubricis aliter provisum sit", restated in the propers as "...nisi propria Missa assignetur". Second, that escape clause splits M26 shape 2 in half, which is why the shape was never resolvable as one thing. Shape 2(a), the week after Trinity, is fixed. Trinity is the temporal identity of its own Sunday, so a plain walkback lands on Trinity's Mass -- but the Missal prints a named formula for the following week, "Missa dominicae I post Pentecosten" (scan1:21758), precisely because the feast has taken that Sunday's own. Those ferias now resolve at step 2 from it and never reach the walkback. Shape 2(b), Christ the King's week, turns out not to be a bug at all. No proper Mass is assigned there -- checked directly, no rubric precedes that Mass heading (scan1:39163ff) -- so RG 299's default governs and "the Mass of the preceding Sunday" genuinely is Christ the King's own, which is what colitur emits and missalemeum does not. Kept open only because no rubric specific to that week was located either way; the verdict is now argued from the primary text rather than resting on oracle disagreement. No Thursday in the slug list: Corpus Christi is Easter+60, which IS that week's Thursday every year, so the ferial slug never exists. Found by the bootstrap's own reachability guard refusing to emit a key no Temporal_ef slug can match, not reasoned out in advance. Allow-lists: C35 opened (69 rows, verdict colitur -- lectio still walks back); C17 narrowed 406 to 397, nine Saturdays moving to C35 because they carry both a citation and a colour difference, with C35 gated to require the citation so a colour-only Saturday still falls to C17; M26 narrowed 30 to 27; M18 widened 352 to 355, the same three days keeping only their observed-identity difference. Register: section 6.11. 2026-08-17T12:13:02Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-17T12:13:02Z urn:sha1:3565ebd1608a7d87e0d890f9953845efcfe743ca A live-missalemeum sweep over a full liturgical year (2028, 364 days) returned 333 matching and 31 differing days: 17 already-known or pure notation, 3 new. All three now adjudicated against the photographic scans of the 1962 Missal. The Assumption's Epistle reads "Iudith 13, 22-25; 15, 10" (scan1:35357). Both engines carried "Judith 13:22-25; 13:15; 13:10" -- a chapter carry-over defect that re-applied chapter 13 to the second citation and so invented two verses the Missal never cites. The Seven Sorrows reads "Iudith 13, 22 et 23-25" (scan1:36938, corroborated at 28468); both carried "Judith 13:22; 13:25", dropping the range. The third, St Monica, resolves the other way: the Missal gives 1 Timothy (scan2:32679, heading and incipit both legible; scan1:29524 agrees) where missalemeum serves the Common of Holy Women's Proverbs -- colitur is right, no change. Layer 3 could not have found either citation defect. colitur's data is bootstrapped from lectio, and lectio is the other side of that differential, so while both engines produced the identical wrong answer the comparison held it against itself and reported agreement -- the shared-lineage blindness CLAUDE.md names, now with a second live witness beside Holy Thursday's colour. Only an external oracle could see it, and only outside the committed fixture's own window. Fixed upstream in lectio, re-bootstrapped here (provenance SHA-256 moved to 54f6bfc5, verified against the source), fixture regenerated. The upstream fix inverted layer 3 from blind to load-bearing here: reverting the Assumption citation now reddens both layers, where before it would have reddened neither. Verified by mutation, both directions. Allow-lists: - C22 closed and removed (128 rows -> 0), not re-adjudicated -- the other engine was fixed to agree, the same shape as the C2-C5/C7/C9-C13/C21 closures. Its own note had already flagged the Lenten Ember dead-key bug for upstream; lectio now also fails its build on any unreachable lectionary key rather than serving a plausible wrong Mass. - M28 opened (3 rows, verdict colitur), pinning both sides' citation text rather than the date and diff shape alone, so a different divergence landing on the same date cannot be swallowed. - M8's gate widened, expected_rows unchanged at 2: 2027-08-15 carries both its cause and M28's, and one entry is admitted per day. It stays under M8, which now requires its own commemoration difference to be present and admits the citation difference only when it satisfies M28's two-sided predicate. Neither cause absorbs the other. layer_m_reason's oracle-row parameter, kept named since M2 closed for exactly such a future reader, is live again. Register: docs/research/rules-register.md section 6.6.