diff options
| author | Lukasz Kasprzak <lukas@labunix.xyz> | 2026-08-22 13:55:15 +0200 |
|---|---|---|
| committer | Lukasz Kasprzak <lukas@labunix.xyz> | 2026-08-22 13:55:15 +0200 |
| commit | 1ee397c5a09bb5c999e1681f0a6a5d884f2f9ff4 (patch) | |
| tree | a5fa31cbd030b2f3a3764254517feb022fdc6623 /lib/render | |
| parent | 0a06541e4b894416e9211bd0d5b14f877de46d59 (diff) | |
| download | colitur-1ee397c5a09bb5c999e1681f0a6a5d884f2f9ff4.tar.gz colitur-1ee397c5a09bb5c999e1681f0a6a5d884f2f9ff4.zip | |
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.
Diffstat (limited to 'lib/render')
0 files changed, 0 insertions, 0 deletions
