From 1ee397c5a09bb5c999e1681f0a6a5d884f2f9ff4 Mon Sep 17 00:00:00 2001 From: Lukasz Kasprzak Date: Sat, 22 Aug 2026 13:55:15 +0200 Subject: docs: six validation layers, not five -- the LMS Ordo is wired in 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. --- README.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index d1b2ed2..5f4724f 100644 --- a/README.md +++ b/README.md @@ -145,7 +145,7 @@ v0.9.0, EF only. **569 tests**, of which the property suite runs against every year in 1583-9999 rather than a sample — that is how confidence extends past the ~2050 horizon of any reference to check against. -Five validation layers, each blind to something the others catch: +Six validation layers, each blind to something the others catch: | | | |---|---| @@ -153,12 +153,18 @@ Five validation layers, each blind to something the others catch: | properties | invariants over all 8 417 years (QCheck) | | differential | 16 801 days compared against the sibling `lectio` engine | | oracle | three captured years compared against missalemeum | +| ordo | one liturgical year compared against a printed Latin Mass Society Ordo | | golden | 11 pinned template outputs | Knowing what each layer *cannot* see is load-bearing here: the differential and -the oracle share one data lineage (Divinum Officium → missalemeum → lectio → -colitur), so an error inherited by both is invisible to either. That is written -up in full in `docs/` rather than left implied. +the missalemeum oracle share one data lineage (Divinum Officium → missalemeum +→ lectio → colitur), so an error inherited by both is invisible to either. The +Ordo layer is a genuinely separate lineage — a clergy-compiled book, never +passed through that chain — but has its own blind spots: it covers one civil +year, only three of the reading-formulary's five sources (a documented +data-representation ambiguity excludes the rest), and England & Wales +diocesan propers are excluded from every comparison, universal-calendar days +only. That is written up in full in `docs/` rather than left implied. **Chants are deliberately absent.** Psalm, Tract, Alleluia and Sequence have no source and no oracle, so `Validate` rejects any citation part outside -- cgit v1.3