colitur.git/data/ef, branch v0.7.0

feat(examples): ship two real local calendars, with their limits stated

2026-08-18T12:14:09Z

Poland and the Benedictines, in the flat INI form, installed beside the invented diocesan example. poland.ini -- 17 entries from the Calendarium Perpetuum pro Dioecesium Poloniae (1964), promulgated under Rubricarum instructum and applying to the 1962 Missal. Transcribed from a published Polish EF ordo that names that same calendar, cross-checked against missalemeum's supplement page for the two formularies 1964 added (13 and 15 July). Date, Latin name and class were read from the source for every entry; three classes could not be recovered from the PDF's column layout and are marked INFERRED where they appear, with the reasoning. The header carries an edition warning that is a real trap here: the Proprium Poloniae of 1921 and 1934 is still bound into many missals and carries an outdated arrangement of dioceses and ranks. It is not this calendar, and it is exactly the kind of plausible wrong-edition source that has cost this project time before. benedictine.ini -- two entries, and the comment explaining why is the point of shipping it. Counted across the Norcia ordo: 86 "I cl.", 43 "II cl.", ZERO "III cl." and ZERO "IV cl.", against 103 "Semidup." and ~96 "Dup.". The monastic rite uses the Roman classes at the top and the older Duplex / Semiduplex grades below, exactly where the Roman calendar has III and IV class. colitur's rank vocabulary cannot express those, so most Benedictine propers cannot be written here at all -- a mismatch of vocabularies between related rites, not a gap in the data. Rather than invent a Duplex -> Class3 mapping the source never states, that file ships only what its ordo gives in Roman terms and lists roughly two dozen excluded feasts BY NAME, so the omission is visible instead of silent. Both headers say plainly that they are examples and not authorities: they are transcriptions from published ordines, none of the five test layers can vouch for either, and both should be checked against the reader's own ordo. The cram test asserts only what we control -- that they parse, convert and apply -- and says so. They also demonstrate the precedence engine on real data: the Benedictine Transitus is I class and takes 21 March with the Lenten feria commemorated, and Maurus is II class and takes 15 January with Paul the First Hermit commemorated.

fix(ef): ubaldus and didacus are III-class feasts, not commemorations

2026-08-18T10:11:05Z

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.

fix(ef): the Assumption and St Lawrence vigils are violet (RG 128)

2026-08-18T09:36:33Z

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.

fix(ef): Good Friday is black, not violet (RG 128(b), RG 132)

2026-08-18T09:26:04Z

RG 128(b)'s own exception list, transcribed in the rules register and primary-source-verified since Task 16, excepts "Actione liturgica feria VI in Passione et Morte Domini usque ad Communionem exclusive" from the violet that otherwise runs from Septuagesima to the Easter Vigil. RG 132 assigns black there. The register recorded this as an acknowledged gap rather than a disputed reading -- the code comment beside the Holy Thursday exception says so in as many words -- and it is closed here. Found by two witnesses outside the Divinum Officium lineage that colitur, lectio and missalemeum all share: O'Connell, The Celebration of Mass, 4th ed. (1964), revised throughout to the Codex Rubricarum (1960) and the 1962 Missal, and a published 1962 Ordo. Both say black. So does missalemeum's own colour set, which orders the day "bv". The rubric is per-action ("usque ad Communionem exclusive") and the model emits one colour per day; black is the day's principal one, the same acknowledged limit RG 126's Palm Sunday blessing already carries. Blast radius: one day per year, colour only, across the whole 1583-9999 domain. Two golden pins re-pinned. Good Friday's 46 differential rows leave C23 for a new C36 gated on the exact triple [First_f; Gospel_f; Colour_f], so C23's own exact-pair gate still means what its note says for its remaining four days: 184 + 46 = 230, no residue, both counts from the comparator rather than hand-counted.

docs(ef): close C6 and M26; nothing is left adjudicated against colitur

2026-08-18T08:31:22Z

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.

fix(ef): days within the Octave of the Nativity, and RG 69 for 29-31 Dec

2026-08-18T08:21:39Z

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.

feat(data): ship a worked example overlay calendar

2026-08-18T07:26:26Z

`--overlay` shipped last week with nothing to point at. The only example was a test fixture, explicitly labelled invented and living where no user would find it, so "colitur supports local calendars" was true but undemonstrated. data/ef/examples/diocesan-example.sexp is installed to /share/colitur/examples/ and is runnable documentation: every celebration in it is invented, with example- slugs that cannot collide, and its header explains the four directives, the three date shapes, and the field vocabularies before showing any of them. It demonstrates the range deliberately rather than the minimum: a fixed-date local patron with its own propers; a movable dedication on the first Sunday of October, I class because a church's own dedication anniversary is I class in that church and at III it would lose to the Sunday every year; an Easter-relative commemoration; an Edit raising a universal feast for local use; and a Suppress shown commented out, because suppressing a universal feast is a real liturgical act and an example should not invite it casually. Two things the header says plainly, since this is the one file that lets someone change what colitur computes: an overlay is applied ON TOP of the shipped calendar and never instead of it, and an overlay is applied, NOT validated -- the five test layers assert things about the shipped data and cannot vouch for a user's file. A test asserts it loads against the real EF rank vocabulary, still demonstrates at least four directives, and applies with NO diagnostics. The last matters most: a directive naming a slug the universal calendar lacks would warn, and an example that warns teaches the wrong lesson. It deliberately does not pin which days it produces -- those celebrations are invented, and pinning their dates would make an illustrative file behave like calendar data.

docs(ef): M13 adjudicated colitur; Mass I is unreachable, not unwitnessed

2026-08-17T20:30:58Z

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.

feat(ef): the votive Mass of Our Lady on Saturday (RG 309(a))

2026-08-17T19:45:47Z

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.

feat(ef): the Seven Sorrows of Passion Friday, and M16 reversed

2026-08-17T19:23:57Z

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.