Recurrence — history

The dated record of how Recurrence got here, moved out of the spec on 2026-11-16 because a reader does not need it to use the spec today. Everything smaller is in git log -- atoms/recurrence.md.

Decisions

  • 2026-11-08 — Drafted through the Grace connector, the second atom of the hard set. Chose: a Recurrence atom on the maintainer’s ruling of 2026-11-06 (after-grounding item 14: “what a repeat rule says (‘every second Tuesday’, ‘the last business day’, exceptions), modeled on iCalendar’s repeat rules as the answer key, composing Calendar Time”), begun on the maintainer’s word of 2026-11-08 02:23Z (“lets go”) once Calendar Time grounded, drafting begun 2026-11-08 02:27Z, from which its rounds to ground count; an atom, as the ruling’s “two atoms, one purpose each” says, which names no other atom (spec-format.md, Atom shape), so it answers calendar dates and the pattern that composes it with Calendar Time resolves them. Over: a composition of Recurrence with Calendar Time in one page; a time of day and a place carried in the series. Because: a repeat says which days; what moment a day’s time names in a place is Calendar Time’s, already grounded, so the daylight-saving cases the ruling gives a TLA model belong to the wiring of the two, and this page’s formal layer is the Alloy model of its shape.

  • 2026-11-08 — RFC 5545’s repeat rules for the parts most software needs. Chose: daily, weekly, monthly and yearly frequencies with an interval and a week start (Term period, Term repeating period); months, month days and day entries, each picking or keeping dates by RFC 5545’s table for those four frequencies (Term daily picks through Term yearly picks); positions over each period’s picks (Term selected dates); a limit or an end date, never both (Operation 11); exceptions that take dates out without moving the limit (Term end bound, Term occurrence). Over: repeats within a day, BYHOUR, BYMINUTE and BYSECOND (a scheduler’s, Non-goal 1); BYWEEKNO and BYYEARDAY (rare, and outside the needs the ruling names); RDATE and moved occurrences (an event’s, Non-goal 7, 8); an RRULE text the atom would parse. Because: the ruling names every second Tuesday, the last business day and exceptions, and these parts say each of them in both its readings, the Examples showing how; what the atom leaves out is named with its owner.

  • 2026-11-08 — Where RFC 5545 leaves a choice open. Chose: a start the series does not generate is no occurrence, the series counting its periods from the start’s period (Term generated date); a date the calendar lacks never generated and never counted (Term day match), so the 31st falls only in months that hold one; an ordinal on a day entry only on monthly and yearly series (RFC 5545 erratum 1911) and never beside month days; positions only beside a selector (Operation 10); an end that moves a series’ end sooner and drops its limit, never later (Operation 27, Operation 28). Over: the start counted as the first occurrence whatever the series says (RFC 5545 calls an unsynchronized start undefined, and every Tuesday from a Friday would answer a Friday); RFC 7529’s SKIP, moving a missing date back or forward (month days 28 through 31 with position -1 say the clamped 31st in RFC 5545’s own terms, so the atom keeps one behavior); a day entry with an ordinal read beside month days in some order. Because: each choice keeps a series’ meaning one meaning and matches what the common implementations of RFC 5545 answer, as the conformance table’s rows show.

  • 2026-11-08 — A cap on the limit. Chose: the largest limit a series may carry is a cap, 1,000 where a deployment declares none (Term limit cap, Capability requirement 4), and an [Open] over it answers invalid-end (Operation 37). Over: no cap, which left the work of [End]’s check (Operation 27) and of the dates [Occurrences] keeps within a limit growing with a limit nothing bounds; a cap that cuts the series short, which would give one series two meanings. Because: 1,000 matches the occurrence cap, so every date of a limited series fits one [Occurrences] call, and a longer series takes an end date, which bounds it without counting (the corpus’s posture on what the host must bound, Cart’s 2026-11-02 entry).