diff options
| author | Lukasz Kasprzak <lukas@labunix.xyz> | 2026-08-18 10:54:01 +0200 |
|---|---|---|
| committer | Lukasz Kasprzak <lukas@labunix.xyz> | 2026-08-18 10:54:01 +0200 |
| commit | cb07b035170eb22e0cff30be6449c74af897cda1 (patch) | |
| tree | 1f10016a468a89750180f23c5f4ab87bec481076 /lib/kernel/overlay.mli | |
| parent | 66162b52b1e7c50fa945cab34e0a184b2623967b (diff) | |
| download | colitur-cb07b035170eb22e0cff30be6449c74af897cda1.tar.gz colitur-cb07b035170eb22e0cff30be6449c74af897cda1.zip | |
docs: name the lineage problem, and record an independent Ordo witness
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.
Diffstat (limited to 'lib/kernel/overlay.mli')
0 files changed, 0 insertions, 0 deletions
