aboutsummaryrefslogtreecommitdiff
path: root/lib
diff options
context:
space:
mode:
Diffstat (limited to 'lib')
-rw-r--r--lib/kernel/calendar.ml15
-rw-r--r--lib/rites/rite_ef/precedence_ef.ml13
2 files changed, 26 insertions, 2 deletions
diff --git a/lib/kernel/calendar.ml b/lib/kernel/calendar.ml
index f2a03a7..cffdf69 100644
--- a/lib/kernel/calendar.ml
+++ b/lib/kernel/calendar.ml
@@ -384,7 +384,20 @@ let build_day (rite : ('s, 'r) Rite.t) (idx : 'r Layer.by_date)
{!Precedence.resolution}'s own [observed]/[commemorations]/[omitted]
fields -- THREE of {!Precedence.resolution}'s four fields (the fourth,
[deferred], denotes a candidate that has NOT yet settled at this date,
- by definition, so it is correctly never consulted here). *)
+ by definition, so it is correctly never consulted here).
+ A SIGNAL TRADED AWAY, named because it is real (fix-round re-review):
+ channel (3) accepts both shapes of [omitted] -- the admission cap, and
+ a rite whose own [disposition] omits the candidate AT the target its
+ own [transfer_target] named. For the cap this is unambiguously
+ "settled". For the second it is a judgement: before this change that
+ shape produced a loud, if mislabelled, [Validate] "unconverged"
+ failure; now it is silent at the origin and honestly reported at the
+ target. The kernel cannot tell "the rite deliberately omitted it
+ there" from "the rite chose a bad target" without rite knowledge it
+ must not have, so accepting it is the right call -- but the diagnostic
+ it used to give up is gone. Unreachable in [Rite_ef] today: only the
+ Major Litanies transfer as [Commemoration_only], and RG 96's search
+ guarantees a transferred FEAST an unblocked target. *)
let settled_at target slug =
let _, _, target_resolution = resolve_with_injected rite idx injected target in
let matches (c : 'r Precedence.candidate) =
diff --git a/lib/rites/rite_ef/precedence_ef.ml b/lib/rites/rite_ef/precedence_ef.ml
index b3c9ab5..c9e6a55 100644
--- a/lib/rites/rite_ef/precedence_ef.ml
+++ b/lib/rites/rite_ef/precedence_ef.ml
@@ -1627,7 +1627,18 @@ let admit ~(observed : Vocab_ef.rank Precedence.candidate)
documents: "in dominicis II classis, nulla alia admittitur
oratio, praeter commemorationem festi II classis, quae tamen
omittitur si commemoratio privilegiata facienda sit" --
- WORD-IDENTICAL to the clause above, but explicitly scoped "post
+ IDENTICAL IN ITS OPERATIVE CLAUSE to the one above -- not word
+ for word throughout: RG 111(b) opens "una tantum admittitur
+ commemoratio, SCILICET DE FESTO II CLASSIS", n. 434(b) recasts
+ that into the orations register as "NULLA ALIA ADMITTITUR ORATIO,
+ PRAETER COMMEMORATIONEM festi II classis", and only the trailing
+ "quae tamen omittitur si commemoratio privilegiata facienda sit"
+ is verbatim in both. That trailing clause is the one this
+ adjudication turns on. And n. 434 is not merely a different part
+ of the same document: the running heads show RG 111 under
+ "Rubricae generales" and n. 434 under "Rubricae generales Missalis
+ Romani" -- two distinct rubrical corpora bound in one volume,
+ which is the whole force of the corroboration. Explicitly scoped "post
orationem Missae" -- an independent, Mass-structure-rubric
confirmation of the exact same privilege-overrides-ordinary rule
this branch already implements, from a different part of the