diff options
| author | Lukasz Kasprzak <lukas@labunix.xyz> | 2026-08-18 14:46:23 +0200 |
|---|---|---|
| committer | Lukasz Kasprzak <lukas@labunix.xyz> | 2026-08-18 14:46:23 +0200 |
| commit | dffc8f885211849ce21cb5bbdbdc46890fca04bc (patch) | |
| tree | 35322780e09a29b6ced32243ea816b233ffec8da /data | |
| parent | 906a84e626ed49c6bd995c6fad7d53355baf582a (diff) | |
| download | colitur-dffc8f885211849ce21cb5bbdbdc46890fca04bc.tar.gz colitur-dffc8f885211849ce21cb5bbdbdc46890fca04bc.zip | |
docs: the lineage is broken at one link, and layer 4 is now the outlier
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.
Diffstat (limited to 'data')
0 files changed, 0 insertions, 0 deletions
