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=v1.0.0 2026-08-22T11:55:15Z 2026-08-22T11:55:15Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-22T11:55:15Z urn:sha1:1ee397c5a09bb5c999e1681f0a6a5d884f2f9ff4 Task 6 (celebrant-rubrics-phase1) added test_lms_ordo.ml as a sixth validation layer, comparing 400 days against a printed Latin Mass Society Ordo -- a genuinely independent fourth lineage, never passed through Divinum Officium/missalemeum/lectio. README.md's own table still said "Five validation layers"; man/colitur.1 still said "two published-calendar oracles"; CLAUDE.md still said "5 layers" in two places and, worse, stated as fact that "the published Ordo... Not wired in as a layer" in the file every future session is instructed to read first. Updated all three, describing what the new layer covers (the Creed, the BVM Saturday votive Mass's own seasonal selection, the reading formulary override) and what it cannot see (one civil year, only three of the formulary axis's five sources, England & Wales diocesan propers excluded from every comparison) -- consistent with docs/research/ordo/PROVENANCE-lms.md, not overstating it. CLAUDE.md's own stale claim is corrected in place, not silently rewritten, matching the file's own established convention: the paragraph it lived in was about a DIFFERENT, earlier Ordo (unreliable PDF column extraction, still genuinely unwired for that reason), and its own closing prediction -- "a structured Ordo would be the only way to add a fourth lineage" -- is exactly what the LMS Ordo's structured extractor (tools/extract_lms_ordo.ml) has since done. Historical "five layers" mentions elsewhere in CLAUDE.md, describing completed state as of earlier branches, are left alone -- they were true then, and rewriting them would misrepresent the record the same way overstating layer 6's own coverage would. Left README's pre-existing v0.9.0/569-tests staleness untouched, as instructed -- it predates this branch and is a separate matter. 2026-08-18T12:46:23Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-18T12:46:23Z urn:sha1:dffc8f885211849ce21cb5bbdbdc46890fca04bc CLAUDE.md's lineage note said layers 3 and 4 are one chain -- Divinum Officium, missalemeum, lectio, colitur -- and that a defect inherited at the root is invisible to both. That is still true everywhere except on the days lectio has now corrected. lectio adopted eight corrections colitur argued from the Missal. On those days the chain no longer runs DO to lectio: lectio follows the Missal, and missalemeum is the only party still carrying the inherited error. C27, C28 and C37 went to zero and are closed; C38 narrowed to a readings-only divergence that cannot close without lectio gaining a Commons concept. The practical consequence for layer 4 is a base rate, and it is worth stating because it is easy to get backwards: on those days the oracle disagrees with BOTH engines, so M29 and M30 should be read as "missalemeum is the outlier" rather than "colitur is unusual". A fresh colitur-vs-missalemeum divergence is no longer presumptively colitur's fault. And the limit, stated so it is not over-read: everywhere else the two layers remain one lineage, and lectio's sanctoral is still generated from missalemeum by a script that would silently revert all four calendar corrections if re-run. That warning now lives in lectio's two ini headers and the generator's own doc comment as well as here. 2026-08-18T10:57:18Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-18T10:57:18Z urn:sha1:084ff22997af208715656924d9fc23bf2ec10050 colitur has been downstream of lectio since its data was bootstrapped from it. These are the fields where that relationship should now invert: eight changes, each annotated with the colitur allow-list entry carrying its rubric. Deliberately a PATCH and not a regeneration. colitur carries 205 of the 327 Polish names lectio ships, so regenerating lectio's ini from colitur would silently drop 122 of them; colitur also uses a different slug vocabulary for Passion/Holy week and different Paschaltide week numbering. What colitur is authoritative for is the adjudicated fields, and only those are emitted. Comparing the two datasets field by field also caught a counting error in colitur's own register that no assertion in this project was watching for: six sanctoral entries carry subject = Lord, not the four recorded, because the regex that counted them truncated on the two longest Polish names. The RG 112(b) reachability measurement was re-run against all six and is unchanged at 0/0; both docs are corrected. 2026-08-18T10:43:36Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-18T10:43:36Z urn:sha1:4d143d762713783d35b2b1d20f8a21d79884dafe They have been carried as a bare 'unbuilt' for weeks. The reason is not neglect, and it differs per clause -- now measured across 1583-9999 rather than asserted. (c) cannot fire in this architecture at all: Temporal_ef.temporal returns one office per day, so two de Tempore candidates never coexist. Nothing to build. (b) is already produced by RG 16(a), which is implemented: 0 days in either direction, because a Lord feast takes an occurring Sunday's place with no commemoration, and no Class1 Sunday shares a date with any of the four Lord-subject entries. (d)'s saint half has no candidate pair. Three apparent pairs are distinct saints sharing a forename -- recorded so the false positive is not rediscovered -- and the one real pair, agnes and agnes-secundo, is 7 days apart and co-occurs 0 times. (b) and (d) are data-unreachable rather than architecture-unreachable, so an overlay can make either live. That is the entry_14_movable_band shape. Left as an explicit open decision rather than silently resolved. 2026-08-18T10:41:26Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-18T10:41:26Z urn:sha1:7ee8aaf865203aa2134d0af661cb011f87650fd2 CLAUDE.md still described it as architecturally blocked, and that claim was being carried forward into task lists a release later. It was true when written and was superseded by the very next task: the blocker was that no (month, day) pair could anchor an Easter-relative trigger, and Date_spec gained Easter_offset in v0.2.0. The entity has shipped since then as an ordinary Add in adjustments.sexp -- 1 981 days across the domain carry it. Also recorded the general lesson, since this cost a stale item twice: a blocker phrased as an architectural impossibility was really a claim about one type's expressiveness, and it dissolved when that type grew a constructor. 2026-08-18T08:54:01Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-18T08:54:01Z urn:sha1:cb07b035170eb22e0cff30be6449c74af897cda1 Two research findings, and the first changes how every earlier adjudication should be read. missalemeum's own repository states it uses Divinum Officium's data files via a git submodule. lectio's ini is generated from missalemeum. colitur was bootstrapped from lectio. So the chain is Divinum Officium -> missalemeum -> lectio -> colitur, and the other projects in this space are the same tree: OfficiumDivinum is an object-oriented rewrite of Divinum Officium, Breviarium Meum is based on its texts. That is worse than the caveat already recorded. CLAUDE.md described layer 3 as sharing colitur's lineage and layer 4 as a separate oracle. It is not separate: layer 4 is layer 3's own upstream. The two oracles are one source seen at two removes, so every colitur-versus-missalemeum adjudication is in substance colitur versus Divinum Officium -- the de facto standard for this whole software space. That makes the six prior adjudications more consequential, and it means the project has one external software witness plus the scans, not two. The second finding is a witness outside that tree entirely: the published Ordo, compiled by clergy applying the rubrics. The 2025-26 Ordo for the Traditional Latin Mass shows commemorations AND distinguishes privileged from ordinary, which is precisely colitur's thinnest axis. Its liturgical timeline matches colitur exactly, and it confirms seven colitur positions -- including M16, reversed against Divinum Officium two days ago on RG 111(d), and the Nativity Octave work from this morning, both halves, including the RG 69 Sunday guard. Three of the confirmations matter most: the Major Litanies, the RG 110 30-June Peter companion, and St Barbara are entries colitur hand-authored because they are missing from lectio AND missalemeum, that is from Divinum Officium. The Ordo carries all three, and even notes the Peter commemoration is said "w/ 1 conclusion" -- RG 110's own pro unica habeantur. Those were the least-supported entries in the dataset and are now the best-corroborated. The one apparent disagreement resolves in colitur's favour: the Ordo lists St Evaristus as 26 October's Mass where colitur observes the feria and commemorates him, but the calendarium reads "Commemoratio S. Evaristi... Comm." in both sources, and the Ordo's own preamble explains it lists Masses that may be said on a class 4 feria. An Ordo is a practical document, not a rank authority. Not wired in as a layer: the PDF's columns shift between pages, automated extraction recovered 271 of 364 rows and truncated text mid-word, and a fragile layer that silently mis-parses is worse than none. A structured Ordo would be the only way to add a genuinely independent fourth lineage. Register: section 6.20. 2026-08-17T15:46:31Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-17T15:46:31Z urn:sha1:0a4bb4e6c3cbcafb302962d9d1e70b5a0bb554b8 The Overlay algebra has been built and tested since Plan 2, and Date_spec grew movable variants last commit, but there was still no way to hand colitur a file: bin/main.ml applied exactly one overlay, the shipped data/ef/adjustments.sexp, with the path hardcoded. This is the plumbing. --overlay is repeatable and ordered, and applies ON TOP of the shipped adjustments rather than instead of them. That ordering is the whole point: adjustments.sexp carries RG 110's own 30 June companion, the Major Litanies, St Barbara and Rogation Wednesday, and a user file that replaced it would silently drop all four while appearing merely to add a local feast. Overlay.merge is last-writer-wins, so a local calendar can still override a universal entry deliberately, by naming its slug. The dispatch needed real argument parsing. It matched Sys.argv as an exact array, which does not survive a repeatable flag -- two --overlay arguments are a different array shape from one, and each further flag would multiply the patterns again. Flags are now stripped first and the remaining words matched as command plus year. Hand-rolled, because the dependency list is frozen and this is fifteen lines. One defect found by the cram suite on the first run: the unknown-option guard rejected --help and --version, having excluded only their short forms. Refused, not ignored, on easter and temporal. Neither reads sanctoral data -- temporal deliberately runs the cycle before any layer exists -- so accepting the flag there and silently doing nothing is the failure mode this project refuses everywhere else. A file that fails to load is fatal, exactly as the shipped overlay is; a directive naming a slug that does not exist warns on stderr and the run continues. The second matters more for a user file than for ours: a typo in a diocesan calendar should say so rather than quietly do nothing. test/fixtures/overlay-example-diocesan.sexp is a worked example and is labelled as invented, not calendar data. It carries both shapes a real local calendar needs: a fixed-date patron, and a dedication on "the first Sunday of October" -- which is the case the Date_spec work existed to unlock and which lands on 4 October in 2026, 3 October in 2027, 1 October in 2028. The dedication is I class because a church's own dedication anniversary is I class in that church; at III class it lost to the II-class Sunday every year, which a first draft demonstrated correctly and uselessly. The man page gains an OVERLAYS section saying plainly that an overlay is applied, NOT validated: the five test layers assert things about the shipped calendar and none of them can vouch for a file the user supplies. This is the first feature that lets someone change what colitur computes, and that distinction should not have to be inferred. 2026-08-17T15:22:43Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-17T15:22:43Z urn:sha1:2b9f8133a22ce6dc309644a98bbe61507f574b38 Date_spec carried one variant, Fixed(month, day), and its own header said Sunday- and Easter-relative forms would arrive with the OF sanctoral. They arrive early because two things needed them at once: a user-supplied overlay carrying a local movable feast had no way to express "the first Sunday of October", and Rogation Wednesday's commemoration has been recorded as architecturally blocked since 2026-08-13. That blockage turns out to have been a premise, not a fact. The register concluded the Rogation "is not Commemoration_only sanctoral data by nature... it needs a genuinely THIRD kind of thing this architecture has no name for" -- but the reasoning rested on there being "no civil (month, day) pair to anchor a Fixed entry to". That is a statement about Date_spec's expressiveness. With Easter_offset the entity is ordinary sanctoral data, the identical shape Add major-litanies already ships, differing only in how the date is written. No third channel was needed. The register is corrected rather than left contradicting the code. Two variants: Easter_offset of int, and Nth_weekday of {month; nth; weekday} with negative nth counting from the end. Fixed's sexp representation is untouched, so all 327 sanctoral entries and the whole overlay parse unchanged. Both are re-validated in t_of_sexp through their smart constructors, extending the idiom Fixed already used -- the failure that guards against is invisible, a spec deserialising into something that silently never resolves and a celebration vanishing with no diagnostic. Easter is supplied by the rite, not computed in the kernel. Computus ships Gregorian and Julian both, and picking one here would hard-code a Roman assumption into rite-agnostic code and be silently wrong for a Julian-reckoning rite. Rite.t gains an easter field; Rite_ef supplies the Gregorian one. Layer keeps a split index. Fixed entries stay in the year-independent (month, day) table, which preserves the fast path and the "30 November counted twice in a 371-day span" behaviour validate.mli documents for St Andrew. Movable entries have no year-independent key by construction -- the same spec lands on a different (month, day) each year -- so they resolve per civil year into a rata-die table. index_by_date is removed rather than kept as an alias: two ways to index a layer, one of which silently ignores movable entries, is the trap this change exists to avoid. Two domain-edge defects, both found by the suite rather than reasoning. A liturgical year is Advent-anchored, so resolving civil year y names y +/- 1, and at the edges those are 1582 and 10000, which Computus correctly refuses by raising. The ceiling surfaced through the domain-ceiling test, the floor through `colitur day 1583` failing outright. Fixed once, in Layer.index, the single point that calls the rite's easter -- a clamp repeated per caller would have been two places to get wrong a third time. Rogation Wednesday: RG 87 assigns the Litaniae minores to the Monday, Tuesday AND Wednesday before Ascension (scan1:691); colitur built the first two from the start and never the third. RG 88 keeps it out of the Office, so the Ascension Vigil remains observed. RG 89 routes it through the Major Litanies' rules, but RG 109's closed list names only maiores, so by RG 107 it is an ORDINARY commemoration -- confirmed in the output, not assumed. Name from the Missal's own "feria IV" (scan1:20495-20497), violet to match the Monday and Tuesday offices. Blast radius, full 1583-9999 sweep against the pre-change binary: 2257 days, every one the same shape, zero unclassified, line counts equal both sides. The complement is the informative half -- in the other 6160 years the Rogation does not appear at all, because RG 111 admits one commemoration on a II-class day and an impeded feast takes it under RG 113, a Commemoration_only candidate having no row in RG 91's table. Both shapes are pinned. Allow-lists unmoved: layer 3 compares no commemorations and is blind by construction, and layer 4's 2026-2027 window has a competing feast on both Wednesdays, so the Rogation is capped out in exactly the years the oracle can see. C8 is unchanged, asserted by its own count pin. Not built: Sunday-relative specs, which nothing needs yet, and the --overlay plumbing that would let a user actually supply a local movable feast. Nth_weekday therefore ships with synthetic and property coverage only; inventing a shipped entry to exercise it would be fabricating calendar data. Register: section 6.10. 2026-08-17T14:11:25Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-17T14:11:25Z urn:sha1:7055723f8b79240ab2df1353eaaf3761f65414a9 Three things the project had no answer for: how to install it without knowing dune, where to read about it, and what it does when asked. Makefile, same shape as lectio's -- PREFIX ?= $(HOME)/.local, BINDIR, MANDIR, and the '## '-comment help target -- so the two siblings are driven the same way. Every recipe wraps dune in `opam exec --`, which is the actual point of having one here: `make build` works from a plain shell with no `eval $(opam env)` first. install goes through `dune install` rather than a hand-rolled copy, because the binary finds its calendar data relative to its own path; the man page is installed separately to share/man/man1, matching lectio. install and uninstall were both run against a scratch prefix and checked: uninstall leaves zero files behind. PREFIX defaults to ~/.local because that is where lectio installs and where it actually lives on this machine, so colitur lands on an existing PATH with no shell change. An earlier install this session went to ~/opt/colitur, which was me over-applying a rule meant for third-party tools to one of the author's own projects; it has been removed rather than left as a second, staler binary competing on PATH. man/colitur.1 documents the four commands, both output formats and why they differ, COLITUR_DATA_DIR and its refusal to fall back, the data resolution order, exit statuses, and -- deliberately -- the limitations: EF only, Epistle and Gospel only with the chants unbuilt and rejected rather than guessed, and the BVM Saturday Mass-selection gap. A man page that only lists what works is half a man page. Renders clean under `groff -ww -z`, no warnings. --help prints to stdout and exits 0; a usage error prints one line to stderr and exits 2. That is the Unix convention rather than a preference: asking for help succeeded and should be pipeable, being invoked wrongly did not and must not pollute stdout. Both directions are asserted in cli.t, along with a loop confirming every command the help text advertises is one the dispatch actually accepts -- the check that catches help drifting away from the code. 2026-08-17T14:00:23Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-17T14:00:23Z urn:sha1:f03567a04b68ab19b5f16f0b6d56d9c08b14c818 Register section 6.7 recorded that step 4 of the reading chain -- the Common route -- had no external witness of any kind, and proved it by mutation: corrupting a Common citation left both the 16801-day differential and the 730-day oracle green. This closes that. 2038 is the only year in 2005-2050 in which two of the five Common-routed saints are the observed office (Perpetua and Felicitas on 6 March, Frances of Rome on 9 March). 365 days were captured live, one request per day, zero failures. A separate fixture, not more rows on the existing one. sources.md already records that the live endpoint has drifted from lectio's archived 2026-2027 snapshot; merging two versions of one source behind a single set of expectations would make any future disagreement unattributable -- calendar or drift, no way to tell. Nothing in the 2038 comparison is checked against the older fixture, and its provenance file says so, along with the fact that a live capture is not reproducible byte-for-byte on demand the way a snapshot-derived one is. 338 of 365 days match. 27 differ, every one of them in a named, already-adjudicated class, none unexplained: 13 the BVM Saturday votive Mass (M26 shape 1), 7 colour (M21), 2 Judith (M28), 2 Christ the King's week (M26 shape 2b), 1 Christmas multi-Mass (M27), 1 Perpetua's Common, 1 new. Each was decided in a different year, so 2038 re-confirms them independently -- the point of a second window is not new rulings but evidence the old ones are not artefacts of their own year. Two findings came out of it. Perpetua and Felicitas: missalemeum serves the Common of Virgins and calls them "Virgins and Martyrs" in its own oration, where the Missal directs "Missa Me exspectaverunt, de Communi non Virginum I loco" (scan1:27634-27635). Both Commons share the Introit Ps 118:95-96, which is exactly why the calendarium qualifies its direction, and both women were mothers. Verdict colitur; the mechanism is located on missalemeum's side, not merely asserted. Passion Tuesday: the Missal prints "Dan. 14, 27 et 28-42" (scan1:11106) and colitur reproduces that two-part form where missalemeum collapses it to 27-42. Same verses; the convention is deliberate, appearing also in the Seven Sorrows and the Common of Non-Virgins. Verdict colitur, cosmetic. Citations are notation-normalised before comparing, as layer 3 already does: Ecclus/Sir, Joann/John, Luc/Luke, Matth/Matt. Each pair was added because a real row needed it, and no target contains its own source as a substring, so the set is idempotent. Not compared, stated rather than left to be found: commemorations and observed-identity. That machinery is built around a date-literal 28-entry allow-list specific to 2026-2027, and re-deriving it for a second year is its own task. 2038 compares rank, colour, Epistle, Gospel. The extractor's day count was hardcoded to 730, which silently forbade any other window. It is now a parameter defaulting to 730, so the existing documented command keeps its guard and a partial fetch still fails loudly instead of producing a short fixture that passes a comparison it never ran. Teeth, by re-running section 6.7's own experiment: corrupting the Common of Non-Virgins II now reddens four tests, two of them external-oracle, where the same mutation previously reddened neither oracle layer. Residual: isidore-of-seville is still unwitnessed and needs 2035 or 2046; gregory-the-great and patrick are never the observed office in any year 2005-2050, so no fixture in that range can reach them. Register section 6.8 and 6.9.