diff options
| -rw-r--r-- | CLAUDE.md | 41 |
1 files changed, 36 insertions, 5 deletions
@@ -587,11 +587,16 @@ candidate is exactly one and already spoken for). IV-class Saturday" — decided entirely by the existing occurrence machinery (`band`'s own entry-27 branch already reads `rank = Class4 && weekday = Sat` unconditionally and only wins when - nothing outranks it), so **no change to `band`, `disposition` or - `admit` was needed** — rank stays Class4 either way, and none of the - three reads slug/colour/name to decide anything. Colour is white, - unconditionally (RG 120(b), not RG 119/127/128's seasonal rules — this - office is never "de Tempore" for colour). The slug is deliberately + nothing outranks it), so **`band` and `admit` needed no change** — rank + stays Class4 either way, and neither reads slug/colour/name to decide + anything (`disposition` DID need one, in a fix round — see below, RG + 112(d)). Colour is white, unconditionally — the tighter chain, found in + a fix round (RG 431(e), the Missal's own classification of this exact + Mass as a "Missa votiva IV classis... de B. Maria Virg.", → RG 121(a), + votive Masses take the colour of the feast-type they "respondent" → + RG 120(b), BVM feasts are white — see below), not RG 120(b) alone + (a stretch: this Office is not itself a *festum*, RG 120(b)'s own + "de festis") and never RG 119/127/128's seasonal rules either way. The slug is deliberately UNCHANGED (reused from the ordinary `<season>-<week>-<weekday>` ferial fallback), the same precedent the Sacred Triduum (item 5) already set — identified structurally, never off the slug — and for a second, load- @@ -636,6 +641,32 @@ candidate is exactly one and already spoken for). the mutation, proving RG 26's rank-keyed omission fires before any subject-keyed rule ever could. + **Fix round 1 (2026-08-13, coordinator review) — one blocking finding, + fixed.** RG 112(d) (Caput XVI): the Office, itself "de B. Maria Virg.", + excludes another commemoration invoking the SAME BVM's intercession — + violated live: `our-lady-of-mt-carmel` (16 July, `Commemoration_only`) + was wrongly commemorated on every 16-July-Saturday. Fixed in + `Precedence_ef.disposition` (`marian_slugs` ∪ `subject = Bvm` on both + sides of the collision — the disjunction matters, neither signal alone + identifies both real sides). Checked exhaustively, not merely for + Mt Carmel: only `Commemoration_only`-status Marian entries can ever + reach this live, and the ONLY other one, `our-lady-of-ransom` (24 + September), is PROVABLY unreachable (forces the September Ember + Saturday every time, by construction). Re-measured: the original + 75,853-day blast radius is unchanged in total, splitting into 74,633 + `colour`-only + 1,220 `colour+comms`. Mutation-tested: exactly 3 tests + redden. Six further ride-along findings closed the same round: a + test pin corrected (26 December can never hold the office, St Stephen + always wins there — 3 January used instead); C17 gained a `subject`- + based identity guard; `band`'s own entry-27 comment gained its RG 78 + citation; a tighter RG 431(e) → RG 121(a) → RG 120(b) colour chain + (conclusion unchanged); and the oracle's own coverage recorded + precisely — of 26 office days in the 2026-2027 fixture only 17 are + colour-discriminating, and **Time after Epiphany (5,015 observed days + domain-wide) has ZERO oracle witnesses**, resting on the scan and the + dedicated unit test alone. Full account: + `.superpowers/sdd/2026-08-12-colitur-rg16a/bvm-saturday-report.md`. + ## How to work here - **Superpowers workflow**: `brainstorming` → `writing-plans` → `executing-plans` |