summaryrefslogtreecommitdiff
path: root/lib/rites
diff options
context:
space:
mode:
Diffstat (limited to 'lib/rites')
-rw-r--r--lib/rites/rite_ef/precedence_ef.ml29
1 files changed, 25 insertions, 4 deletions
diff --git a/lib/rites/rite_ef/precedence_ef.ml b/lib/rites/rite_ef/precedence_ef.ml
index 2987312..5688640 100644
--- a/lib/rites/rite_ef/precedence_ef.ml
+++ b/lib/rites/rite_ef/precedence_ef.ml
@@ -658,10 +658,31 @@ let disposition ~(winner : Vocab_ef.rank Precedence.candidate)
(Advent/Lent/Passiontide, Low Sunday, {!band} entry 6) -- RG 16(a)'s
own text says "Dominica II classis", not "any Sunday", and a I-class
Sunday can never actually reach here as a [loser] against a
- Class1-or-2 Lord winner in the first place: entry 6's own band value
- (6) is lower than every entry a Lord feast of Class1 or Class2 could
- occupy (3, 11-14), so a I-class Sunday always wins outright -- this
- is exactly why the rubric restricts itself to II class. [is_sunday_slug]
+ Class1-or-2 Lord winner in the first place, for TWO DIFFERENT reasons
+ depending on the winner's shape (CORRECTED, fix round 1: the previous
+ version of this comment claimed "entry 6's own band value (6) is
+ lower than every entry [3, 11-14]" as a single numeric argument --
+ WRONG on its face, 6 is not lower than 3, and the claim would in any
+ case prove the opposite of what it was cited for: if a band-3
+ candidate really did contest a Class1 Sunday, the LOWER number (3)
+ would win, i.e. the Sunday would LOSE, not "always win outright" as
+ claimed):
+ - Against entries 11-14 (SANCTORAL-origin Lord feasts, e.g. the
+ Transfiguration): the numeric argument genuinely holds here --
+ entry 6 (6) IS lower than 11-14, so a I-class Sunday always wins
+ outright against these.
+ - Against entry 3 (TEMPORAL-origin Lord feasts -- Epiphany,
+ Ascension, Trinity, Corpus Christi, Sacred Heart, Christ the King):
+ not a numeric argument at all, but a STRUCTURAL one -- every
+ band-3 celebration is [is_temporal], and {!Precedence.resolve}
+ takes exactly ONE temporal candidate per day ([~temporal], not a
+ list), so a band-3 Lord feast IS that date's own single temporal
+ candidate, never a SEPARATE candidate contesting an
+ independently-produced Sunday on the same date. There is no
+ collision to resolve by band comparison in the first place.
+ Either way, no I-class Sunday can reach here as a loser against a
+ Class1-or-2 Lord winner -- this is exactly why the rubric restricts
+ itself to II class. [is_sunday_slug]
(the same marker RG 33's [impedes_vigil] and RG 109(a)'s
[privilege_of] already use, with no [is_temporal] guard there either
-- no sanctoral slug this codebase's data produces contains