diff options
Diffstat (limited to 'data')
| -rw-r--r-- | data/ef/adjustments.sexp | 50 |
1 files changed, 50 insertions, 0 deletions
diff --git a/data/ef/adjustments.sexp b/data/ef/adjustments.sexp index f41d0d1..790665b 100644 --- a/data/ef/adjustments.sexp +++ b/data/ef/adjustments.sexp @@ -257,6 +257,49 @@ ; rewrite (bucket recomputation) and .superpowers/sdd/2026-08-12-colitur- ; rg16a/sanctoral-audit-report.md. Two shapes of finding follow. ; +; `Add rogation-wednesday` -- NEW (movable-date-specs task, 2026-08-17). +; RG 87, primary-verified: "Litaniae minores seu Rogationes, per se, +; assignantur feriis II, III et IV ante festum Ascensionis Domini" +; (scan1.txt:691) -- Monday, Tuesday AND WEDNESDAY. colitur's temporal cycle +; already builds `ef-rogation-{monday,tuesday}` (Easter+36/+37) but never +; Wednesday: Easter+38 is by construction the Ascension Vigil (RG 91 entry +; 21), which wins the day structurally, so `Temporal_ef.named` emits the +; Vigil and there was no channel for the Rogation observance at all. +; +; That gap was architectural, not an oversight, and it is THIS task that +; closes it: until Date_spec grew `Easter_offset`, there was no (month, day) +; pair a Fixed spec could anchor to, which is exactly why the register +; concluded this "is not Commemoration_only sanctoral data by nature". With a +; movable spec it plainly is -- the identical shape `Add major-litanies` +; above already uses, differing only in how the date is expressed. +; +; RG 88: nothing is done in the Office, only the Mass -- so the Vigil's own +; office identity is CORRECTLY untouched; this entry is a commemoration and +; never competes for the observed slot (`Commemoration_only` -> band returns +; `unclassified`, checked first, ahead of every rank-keyed branch). +; +; RG 89: "Ad processionem aut alias peculiares supplicationes et Missam aut +; COMMEMORATIONEM quod attinet, serventur quae supra de Litaniis maioribus +; statuta sunt (nn. 81-83 et 86)". Note what follows: RG 109's closed list of +; privileged commemorations names only "de Litaniis MAIORIBUS" (f), never +; minoribus, so by RG 107's closing rule this is an ORDINARY commemoration -- +; unlike the Major Litanies' privileged one. That asymmetry is deliberate and +; is asserted in test_rite_ef.ml. +; +; Name: "feria IV Rogationum" is the Missal's own (scan1.txt:20495-20497, +; "Et in minoribus ante Ascensionem: feria II Rogationum, statio ad S. Mariam +; maiorem; feria III, statio ad S. Ioannem in Laterano; feria IV, statio ad +; S. Petrum"). Colour violet, matching the Rogation Monday/Tuesday offices +; `Temporal_ef` already builds. +; +; `subject Saint` matches `major-litanies` above. It is behaviourally INERT +; here, verified rather than assumed: `band` returns `unclassified` for any +; Commemoration_only candidate before reading subject at all, and the only +; other readers are RG 112(a) (fires on `Lord` only) and RG 112(d)'s +; `is_bvm_office` (`Bvm` only). `Temporal` would arguably describe both this +; and the Major Litanies better; changing them is a separate, zero-blast- +; radius tidy-up, deliberately not folded into this task. +; ; `Add barbara` -- a genuine DATA GAP, the same shape as the ef-rebootstrap ; task's five (agnes-secundo/boniface-martyr/eusebius-confessor/evaristus/ ; theodore, above): both scans, 4 December, carry a second line under S. @@ -330,6 +373,13 @@ (rank Class4) (status Commemoration_only) (colour Violet) (subject Saint) (citations ()) (layer ef-universal))))) (Add + ((date (Easter_offset 38)) + (cel + ((slug rogation-wednesday) + (names ((la "Feria IV Rogationum") (en "Rogation Wednesday"))) + (rank Class4) (status Commemoration_only) (colour Violet) + (subject Saint) (citations ()) (layer ef-universal))))) + (Add ((date (Fixed (month 12) (day 4))) (cel ((slug barbara) |