2 files changed, 73 insertions, 9 deletions
diff --git a/data/ef/adjustments.sexp b/data/ef/adjustments.sexp
index 85d7fa1..05ee401 100644
--- a/data/ef/adjustments.sexp
+++ b/data/ef/adjustments.sexp
@@ -10,4 +10,47 @@
 ; or special-cased in code, per the task brief -- an auditable, diagnosable
 ; removal (Overlay.apply's own diagnostic fires if this slug is ever absent,
 ; e.g. after a re-bootstrap that renames it), not a silent drop.
-((id ef-adjustments) (directives ((Suppress vigil-of-christmas))))
+;
+; RG16(a) task (docs/research/rules-register.md §6.0): corrects one of
+; data/ef/sanctoral.sexp's six `(subject Lord)` entries, inherited unchecked
+; from lectio's own `class = lord` field (tridentine-calendar.ini) --
+; `most-holy-name-of-mary` (12 Sep): calendarium line "Sanctissimi Nominis
+; Mariae, III classis" -- "Nominis Mariae", the Name of MARY, not of the
+; Lord, with no counter-evidence found anywhere (the "D. N. I. C." formula
+; the genuinely Lord-tagged entries carry, e.g. 6 Aug "IN TRANSFIGURATIONE
+; D. N. I. C.", is simply absent here, and nothing else in the calendarium
+; suggests otherwise). This tag has no behavioural effect either way today
+; ({!Precedence_ef.band}'s entry 14, the only place [subject] is tested for
+; a II-class candidate, requires [Class2]; this entry is [Class3]) -- kept
+; for the data's own accuracy, not because anything currently reads it.
+;
+; The tag [Bvm] itself carries no further systematic meaning in this
+; codebase beyond "not Lord" -- after this correction it exists on exactly
+; this one entry, while every other Marian feast (the Assumption, the
+; Immaculate Conception, the Nativity of the BVM, ...) stays `(subject
+; Saint)`. Nothing reads [Bvm] specifically; {!Subject.t}'s four-way split
+; is not fully exercised by this codebase's own logic, only [Lord] is.
+;
+; RG16(a) task, fix round 1 (CRITICAL finding, reverted): a companion Edit
+; here previously also retagged `purification-of-the-blessed-virgin-mary`
+; (2 Feb) to [Bvm], on the same calendarium-title argument ("B. Mariae
+; Virg.", not "D. N. I. C."). REVERTED -- the user has ruled: follow the
+; oracle. missalemeum (this project's designated EF oracle) treats the
+; Purification as taking an occurring II-class Sunday's place OUTRIGHT, with
+; NO commemoration of the Sunday (`2020-02-02`, `2014-02-02`: title
+; "Purification of the Blessed Virgin Mary", `"commemorations": []`),
+; exactly RG 16(a)'s own "festum Domini" treatment -- and NOT the treatment
+; it gives an ordinary Marian feast on a Sunday (`2019-09-08`, the Nativity
+; of the BVM: title "XIII Sunday after Pentecost", the FEAST demoted to a
+; commemoration, the Sunday observed -- the opposite pattern). Genuine
+; primary-text counter-evidence for the Marian reading remains on record
+; (RG 120(b): the white-colour rule groups 2 February under "B. Mariae
+; Virg.", a SEPARATE category from "Domini" -- register §6.0 quotes it in
+; full), so the calendarium TITLE and the oracle's BEHAVIOUR disagree here;
+; the user's ruling resolves that disagreement in the oracle's favour for
+; this codebase's own purposes, not by declaring the calendarium argument
+; wrong. See register §6.0 for the full account of both sides.
+((id ef-adjustments)
+  (directives
+    ((Suppress vigil-of-christmas)
+      (Edit most-holy-name-of-mary ((Set_subject Bvm))))))
diff --git a/data/ef/expected-divergences-missalemeum.sexp b/data/ef/expected-divergences-missalemeum.sexp
index f50898b..53e93d4 100644
--- a/data/ef/expected-divergences-missalemeum.sexp
+++ b/data/ef/expected-divergences-missalemeum.sexp
@@ -19,10 +19,21 @@
 ; absorbed as if colitur were right. TWO entries (M11 and M13) are
 ; [verdict open] -- corrected, final fix wave, item 7: this note previously
 ; said "one entry (M13)", missing M11 (whose own verdict changed from
-; [colitur] to [open] in fix round 1, see M11's own entry below). Both are
-; adjudicated as UNRESOLVED after real primary-source effort, not defaulted
-; past -- see each entry's own note and the task report for the full
-; search.
+; [colitur] to [open] in fix round 1, see M11's own entry below). Task B
+; (branch ef-rg16a) briefly added a THIRD, M17, adjudicated [open] as a
+; "genuine same-band tie RG 113 does not resolve" -- CORRECTED, Task B fix
+; round 1: M17 was wrong. The tie was manufactured by Precedence_ef.band
+; lending a Commemoration_only candidate the same table entry as a genuine
+; Feast of its own rank (RG 91's table has no row for a bare commemoration
+; at all); fixed in band itself, and the divergence disappears entirely --
+; M17 was REMOVED, not re-adjudicated to a different verdict. ONE entry
+; (M15) carries a fourth verdict, [unresolvable] -- a LIMIT of this
+; comparator (no English name exists on colitur's side for a temporal-
+; origin commemoration to compare), not a rubric dispute or a data gap
+; either engine is wrong about; see M15's own note. All remaining OPEN
+; entries are adjudicated as UNRESOLVED/UNRESOLVABLE after real
+; primary-source effort, not defaulted past -- see each entry's own note
+; and the task report for the full search.
 ;
 ; [expected_rows] is the exact row count this entry accounts for over the
 ; fixture's 2026-2027 span: a REGRESSION PIN, not documentation --
@@ -59,9 +70,9 @@
  (note "Independently confirmed by the oracle, not a new finding: missalemeum's \"Pro rogationibus\" commemoration on St Mark's day (25 April, the Major Litanies' fixed date) is exactly the missing office register §6 already tracks. Only 2026 shows as a comparator MISMATCH: 25 April 2026 is a Saturday with Mark winning outright, so colitur's commemoration list is empty where the oracle's carries \"Pro rogationibus\" -- a real presence gap. 25 April 2027 is a Sunday: the Sunday wins on BOTH sides, and each side's own single commemoration slot goes to a DIFFERENT candidate (colitur: St Mark himself, an ordinary II-class sanctoral loser admitted under RG111(b)'s \"de festo II classis\" slot; missalemeum: the Major Litanies) -- both non-empty, same count, so this comparator's count-only axis (deliberately not slug-identity, see test_oracle.ml's own header) cannot see that mismatch; the underlying gap is the same, just invisible to this year's row.")
  (expected_rows 1))
  ((id M6)
- (citation "1962 calendarium, 14 August row: \"Vigilia, II classis.\" -- nothing else listed -- primary-source-verified 2026-08-12")
- (verdict colitur)
- (note "The reverse of M4/M7/M9: no commemoration is listed for 14 August anywhere in the primary source this project treats as authoritative. data/ef/sanctoral.sexp agrees (a single entry, vigil-of-the-assumption). missalemeum's \"St. Eusebius\" for this date has no support found here -- a DIFFERENT St Eusebius (bishop and martyr) is genuinely commemorated 16 December, matching lectio's own [eusebius] entry at THAT date, not this one.")
+ (citation "CORRECTED 2026-08-12, transcription-audit task (branch ef-rg16a): the previous citation below read the ELECTRONIC TRANSCRIPTION (1962-06-23,_SS_Ioannes_XXIII,_Missale_Romanum,_LT.pdf), which silently drops calendarium commemorations, and mistook its silence for the calendarium's own. A photographic scan (missale-romanum-1962.pdf), 14 August row: \"Vigilia, II classis, Commemoratio S. Eusebii Conf.\", with its own proper immediately following (\"Eodem die ... Et fit commemoratio S. Eusebii Conf.\") -- independently confirmed in the second scan, Missale Romanum 1962_text.pdf. Primary-source-verified 2026-08-12.")
+ (verdict missalemeum)
+ (note "The same shape as M4/M7/M9/M14, not the reverse of them: a genuine commemoration -- S. Eusebius, Confessor, 14 August -- is present in the 1962 calendarium and in missalemeum's own data, but absent from data/ef/sanctoral.sexp and from lectio's own tridentine-calendar.ini (no 08-14 entry beyond vigil-of-the-assumption). This Eusebius Confessor (14 Aug) is a genuinely DIFFERENT saint from Eusebius Bishop and Martyr (16 Dec, already correctly in data/ef/sanctoral.sexp, matching lectio's own [eusebius] entry at THAT date) -- both exist, at their own separate dates; the calendarium carries both. Not fixed here: single-source data, the same bootstrap-reach constraint as M4/M7/M9/M14 (would require touching ~/git/projects/lectio). Register docs/research/rules-register.md, Decisions item 4 and the transcription-audit record in section 6, has the full account and the wider calendarium sweep this correction came from.")
  (expected_rows 2))
  ((id M7)
  (citation "1962 calendarium, 26 October row: \"Com. S. Evaristi Papæ et Mart.\" -- primary-source-verified 2026-08-12")
@@ -101,5 +112,15 @@
  ((id M13)
  (citation "OPEN -- not adjudicated. 1962 calendarium's March table: \"Feria VI post dominicam I Passionis: Commemoratio septem Dolorum B. Mariæ Virg.\" (confirmed real, every year) -- but RG 91's plain table (entry 11-13, Joseph, I class, vs entry 22, an ordinary III-class Passiontide feria) gives Joseph the day outright, with no RG 96 collision requiring a transfer, so the primary text found here does not by itself explain missalemeum's result")
  (verdict open)
- (note "19 March 2027: St Joseph (I class) falls on the Friday of Passion Week. missalemeum shows Joseph entirely displaced, with the Friday's own III-class violet office observed and the Seven Sorrows commemorated instead. Three possibilities, none confirmed: (a) colitur's plain RG 91 reading is right and missalemeum is wrong; (b) a more specific rubric attached to St Joseph's own Proprium Sanctorum entry (the same shape as the Annunciation's own Attamen clause) overrides the general table for this exact collision, and this task did not find its text; (c) the Seven Sorrows commemoration itself outranks an ordinary I-class feast on this one Friday, unsupported by anything found here either. Extensive but non-exhaustive primary-source search did not settle it -- register §6 open item, explicitly unresolved rather than defaulted to either side. Separately, but confirmed regardless: colitur does not implement the Seven-Sorrows-of-Passion-Friday commemoration at all, in any year -- a real, primary-attested gap on its own.")
+ (note "19 March 2027: St Joseph (I class) falls on the Friday of Passion Week. missalemeum shows Joseph entirely displaced, with the Friday's own III-class violet office observed and the Seven Sorrows commemorated instead. Three possibilities, none confirmed: (a) colitur's plain RG 91 reading is right and missalemeum is wrong; (b) a more specific rubric attached to St Joseph's own Proprium Sanctorum entry (the same shape as the Annunciation's own Attamen clause) overrides the general table for this exact collision, and this task did not find its text; (c) the Seven Sorrows commemoration itself outranks an ordinary I-class feast on this one Friday, unsupported by anything found here either. Extensive but non-exhaustive primary-source search did not settle it -- register §6 open item, explicitly unresolved rather than defaulted to either side. Separately, but confirmed regardless: colitur does not implement the Seven-Sorrows-of-Passion-Friday commemoration at all, in any year -- a real, primary-attested gap on its own. CORRECTED 2026-08-12 (Task B, branch ef-rg16a, commemoration-identity comparison): this date now ALSO trips [Comm_identity_unresolved] (colitur's own commemorated candidate there, [ef-passiontide-1-friday], is temporal-origin and carries no English name) -- the SAME root cause as M15 below, folded into this entry's own subset check rather than a separate id, since it is the identical Seven-Sorrows gap this note already names, not a new finding.")
+ (expected_rows 1))
+ ((id M15)
+ (citation "docs/research/rules-register.md §4's own \"THE MAPPING, AND EXACTLY WHAT IT CANNOT RESOLVE\" note (test_oracle.ml's own header) -- not an RG citation, a comparator LIMIT: Rite_ef.Temporal_ef never sets an English [names] field on any candidate it builds (temporal_ef.ml has no \"en ...\" string anywhere in it)")
+ (verdict unresolvable)
+ (note "19 rows where colitur's own admitted commemoration is TEMPORAL-origin (an impeded Advent or Lent feria) -- there is no English name on colitur's side to compare against missalemeum's title text at all, so identity cannot be attempted, only reported as unresolved. Not a rubric dispute and not a data gap either engine is wrong about. Every oracle title on these 19 rows reads as a plain prose description of the SAME temporal ferial slot colitur independently computes for that date (e.g. 2 Dec 2026: oracle \"Feria IV after I Sunday of Advent\" against colitur's own ef-advent-1-wednesday; 4 Dec 2027: oracle \"Sabbato after I Sunday of Advent\" against ef-advent-1-saturday) -- suggestive corroboration, recorded for a human reader, NOT claimed as a verified match: this comparator has no mechanism to verify English prose against an opaque slug. Fixing this at the root (an English name on every temporal-cycle candidate) is a data/lectionary-bootstrap task, not something this comparator can do for itself -- register §6, neighbouring the RG 113 tie-break section, records it as an open item. The 19 dates: 2026-02-24, 2026-03-19, 2026-03-25, 2026-12-02, 2026-12-03, 2026-12-04, 2026-12-07, 2026-12-11, 2026-12-21, 2027-02-24, 2027-12-02, 2027-12-03, 2027-12-04, 2027-12-06, 2027-12-07, 2027-12-11, 2027-12-13, 2027-12-16, 2027-12-21.")
+ (expected_rows 19))
+ ((id M16)
+ (citation "1962 calendarium's March table (same primary text as M13's own citation): \"Feria VI post dominicam I Passionis: Commemoratio septem Dolorum B. Mariae Virg.\" -- a fixed commemoration of Our Lady's Seven Sorrows for the Friday of Passion Week, every year, confirmed real")
+ (verdict missalemeum)
+ (note "27 March 2026 (Friday of Passion Week): colitur admits \"St. John Damascene\" (a real Class3 universal feast that genuinely falls that day, data/ef/sanctoral.sexp's own john-damascene entry, 27 March); missalemeum shows \"For Our Lady of the Seven Sorrows\" instead. The SAME standing gap M13 already names: the Seven-Sorrows-of-Passion-Friday commemoration is confirmed real in the primary text but not implemented anywhere in temporal_ef.ml, so colitur has no candidate for it and falls back to whichever ordinary Class3 saint actually wins that Friday. Verdict missalemeum: colitur is missing a real, primary-cited office, not differently opinioned. Register §6 open item (the same one M13's own note already tracks). Only 2026 shows here as an IDENTITY mismatch -- 2027's Friday of Passion Week IS 19 March, M13's own date, where identity comparison cannot even be reached (M13's own rank/colour mismatch already excludes that day from count-matched identity comparison, folded into M13's own widened subset above). NOTE for whoever builds the office (fix round 1, coordinator finding 7): 27 March 2026 is a III-class day, where RG 111(d) admits TWO commemorations -- yet missalemeum admits only the Seven Sorrows and DISPLACES John Damascene entirely, not merely drops him to second place. A naive implementation (one more ordinary III-class commemoration competing for the day's two slots) would give colitur two commemorations where missalemeum shows one; whatever privilege the Seven Sorrows carries must itself explain the exclusion, not just win admission.")
  (expected_rows 1))