diff options
| -rw-r--r-- | CLAUDE.md | 15 |
1 files changed, 15 insertions, 0 deletions
@@ -120,6 +120,21 @@ suite samples). Layer 3 compares 16 801 days against lectio; layer 4, 730 days against missalemeum; layer 5 pins ~30 dates. **Know what each layer cannot see** — this is load-bearing, not a caveat: +- **LAYERS 3 AND 4 ARE ONE LINEAGE, not two** (register §6.20, 2026-08-18 — + this supersedes the weaker "shares colitur's lineage" caveat below). + missalemeum's own repo 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 **Divinum Officium → missalemeum → lectio → + colitur**, and layer 4 is layer 3's own UPSTREAM rather than a separate + witness. Every "colitur vs missalemeum" ruling is in substance colitur vs + Divinum Officium, the de facto standard for this whole software space. The + project has ONE external software witness plus the scans — not two. + The genuinely independent witness found is the **published Ordo** (clergy- + compiled, not software): it confirmed seven colitur positions including + three hand-authored entries missing from the entire DO tree (Major + Litanies, the RG 110 Peter companion, St Barbara). Not wired in as a layer — + its PDF columns shift between pages and extraction is unreliable; a + structured Ordo would be the only way to add a fourth *lineage*. - Layer 3 **never compares commemorations** (lectio has no RG 111 admission logic, so its "others" are losing candidates, not the admitted set) and never compares the week column. It also **shares colitur's own lineage**: colitur's data was |
