deterministic OCaml engine to compute and validate liturgical calendars for multiple rites, template-driven output to year 9999 https://git.labunix.xyz/colitur.git/atom?h=v0.7.0 2026-08-11T17:02:08Z 2026-08-11T17:02:08Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-11T17:02:08Z urn:sha1:8ab24da337a10993b98696df5d499706318beb8e The 1960 reform reduced many feasts to a bare commemoration. They keep a rank, because RG 111 orders admitted commemorations by dignity, but they can never be the observed day. Modelled as a separate status rather than a fifth rank: RG 8 fixes the classes at four. 2026-08-11T10:10:49Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-11T10:10:49Z urn:sha1:1512df6514f0e656d734f2bf03d050355d0dd0b7 The comment explaining Celebration's single type parameter claimed OCaml rejects a type variable that appears in no field. That is false: a phantom season parameter compiles cleanly. The real reason is a design choice, not a compiler constraint -- a celebration has no season of its own (season is contextual to the day, and lives in Temporal.t), and a phantom parameter would carry no information while forcing every consumer to thread a meaningless variable. 2026-08-11T09:59:43Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-11T09:59:43Z urn:sha1:abade24943f2f77c058b5ff768093b8babc9a8c3 Rite specificity is carried by type parameters plus a vocab record of operations rather than by functors: the same guarantee that a rite cannot name another rite's season, without threading module plumbing through every kernel module. Celebration takes only the rank parameter, since it has no season field and OCaml rejects a type variable that appears in no field.