1 files changed, 44 insertions, 1 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))))))