summaryrefslogtreecommitdiff
path: root/lib/rites
diff options
context:
space:
mode:
Diffstat (limited to 'lib/rites')
-rw-r--r--lib/rites/rite_of/precedence_of.mli21
1 files changed, 16 insertions, 5 deletions
diff --git a/lib/rites/rite_of/precedence_of.mli b/lib/rites/rite_of/precedence_of.mli
index 5866526..4ef81a5 100644
--- a/lib/rites/rite_of/precedence_of.mli
+++ b/lib/rites/rite_of/precedence_of.mli
@@ -107,11 +107,22 @@ val rules : (Vocab_of.season, Vocab_of.rank) Precedence.rules
conditional ("ubi est de praecepto servanda") and the following sentence
gives Episcopal Conferences discretion where it is not, so the universal
calendar legitimately not implementing it is defensible; not citing it at
- all was not, hence this note. No sanctoral data exists yet (Phase 3), so
- nothing is WRONG today -- but this must be settled before Phase 3 ships
- data, or 25 March co-occurring with Palm Sunday will send St Joseph to
- Easter + 8 via rule 3 (the same target the Annunciation would already be
- heading to that same year) instead of backward to 18 March.
+ all was not, hence this note.
+
+ CORRECTED: this note previously said "No sanctoral data exists yet
+ (Phase 3), so nothing is WRONG today" and located the trigger at
+ "25 March co-occurring with Palm Sunday". Both are now false and were
+ already wrong about the date: St Joseph is 19 March, not 25 March (25
+ March is the Annunciation, a separate solemnity with its own Holy-Week
+ handling). Phase 3 shipped sanctoral data on this same branch
+ (data/of/calendar-2002.sexp), so the defect this note warns about is now
+ LIVE: 19 March coincides with Palm Sunday in 16 of the 1583-2100 years
+ (e.g. 2062), and St Joseph lands forward at Easter+9 via rule 3 instead
+ of anticipated backward to 18 March. Pinned, not silently wrong: see
+ test_rite_of.ml's [test_joseph_palm_sunday_2062_known_wrong_forward_transfer]
+ (2062, both grade and identity) and allow-list entries L8/L9
+ (data/of/expected-divergences-litcal.sexp, 2035-03-17, a second, distinct
+ year witnessing the same limitation).
Implementing it would need either a kernel signature change (out of
scope for this rite module and forbidden by this fix wave) or a