diff options
| -rw-r--r-- | CLAUDE.md | 32 |
1 files changed, 21 insertions, 11 deletions
@@ -636,7 +636,7 @@ original, distinct architectural reason. 5. **The Sacred Triduum (RG 91 entry 2) — RESOLVED (2026-08-13, `ef-triduum-litanies` task); Major Litanies (RG 80/81/109(f)) — RESOLVED (2026-08-13, `ef-major-litanies` task); Rogation Wednesday's - own commemoration (RG 87-89) remains genuinely unbuilt.** Holy Thursday/Good + own commemoration (RG 87-89) — RESOLVED, see below.** Holy Thursday/Good Friday/Holy Saturday kept their existing slugs (`ef-passiontide-2-{thursday,friday,saturday}` — RG 91 entry 2 is identified structurally by `Precedence_ef.band`, off rank and Easter @@ -704,16 +704,26 @@ original, distinct architectural reason. privilege. Full account: `.superpowers/sdd/2026-08-12-colitur-rg16a/major- litanies-report.md`. - **Rogation Wednesday remains genuinely blocked**, and for the ORIGINAL - architectural reason, now confirmed distinct from the Litanies' own - (dissolved) one: its trigger is not a fixed civil date at all, but the - day's OWN temporal identity (Easter+38), which coincides structurally - with the Ascension Vigil — there is no `(month, day)` pair a `Fixed` - spec could ever anchor to, so the Litanies' own "reuse the RG 96 - transfer machinery" trick does not apply here (nothing is being - transferred FROM a civil date; the commemoration would have to be - synthesised from the day's own Easter offset, which still has no - channel). No partial build exists. + **Rogation Wednesday — RESOLVED (2026-08-17, the movable-date-specs + task, v0.2.0).** *(CORRECTED 2026-08-18: this paragraph previously read + "remains genuinely blocked" and was still being quoted as an open item + a release later. It was accurate when written and was superseded by the + very next task.)* The blocker it describes was exact — "there is no + `(month, day)` pair a `Fixed` spec could ever anchor to" — and it names + its own remedy: the missing channel is a date spec that can express an + Easter offset. `Date_spec` gained `Easter_offset` precisely then, so + the entity is now an ordinary `Add` in `data/ef/adjustments.sexp` + (`Easter_offset 38`, `Class4`, `Commemoration_only`, RG 87 verified at + scan1.txt:691 — "Litaniae minores seu Rogationes, per se, assignantur + feriis II, III et IV ante festum Ascensionis Domini", Monday, Tuesday + AND Wednesday). Live: 1 981 days across 1583–9999 carry it, and in the + remainder an impeded feast takes the single slot RG 111 allows. Two + golden pins cover both outcomes. + + The lesson worth keeping: a blocker stated as an architectural + impossibility was really a statement about one type's expressiveness, + and it dissolved the moment that type grew a constructor. Read such a + claim as "what would have to change", not "this cannot be done". 9. **RG 91 entry 27, the votive Office of the BVM on Saturday — RESOLVED (2026-08-13, `ef-bvm-saturday` task).** `Precedence_ef.band` already |