Calendar Time — history

The dated record of how Calendar Time 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/calendar-time.md.

Decisions

  • 2026-11-08 — Drafted through the Grace connector, the first atom of the hard set. Chose: a Calendar Time atom on the maintainer’s ruling of 2026-11-06 (after-grounding item 14: “what a date means in a place, reverse-specified from JavaScript Temporal’s decisions, not its API”), chosen next by the maintainer on 2026-11-07, drafting begun 2026-11-08 00:01Z, from which its rounds to ground count; written against the Database contract from the first draft, the Database, Read and Refusal families cited once (Capability requirement 4) and restated nowhere; Recurrence left to a pattern of its own that composes this one (Non-goal 1). Over: a calendar folded into each pattern that shows or keeps a time; Recurrence drafted in the same page. Because: the ruling asks for two atoms, one purpose each, Calendar Time grounding first, so that Recurrence composes a grounded page.

  • 2026-11-08 — A place is the record. Chose: the place, a time zone and a week start, as the atom’s one record, with every other answer computed at the call from the place, the time zone rules and now (Term day span, Term reading); a place never removed (State 2), its earlier versions readable (Execution Contract Database 5). Over: a set of calculations with no record (the Execution Contract’s taxonomy gives every atom records of its own); a stored local time or instant (a pattern that keeps a meeting or a posting keeps its own); a raw offset as a place (an offset ignores the law that moves a zone’s clocks). Because: a reading needs the reader’s place, and a date covers a stretch of time only in some place, so the place is what the atom must remember; everything else follows from it.

  • 2026-11-08 — Temporal’s decisions for a skipped or repeated time and for a month that is too short. Chose: four choices for a wall time the clock skips or repeats (Term choice): compatible, Temporal’s default and RFC 5545’s, moving a skipped time forward by the gap’s length and taking a repeated time’s earlier match; earlier and later; reject, refused as skipped-time or repeated-time (Operation 15 through 21); [Shift] moving years and months first, keeping the day, clamping it to the landing month’s last day or refusing as the overflow says, then adding the days (Term landing day, Operation 24, Operation 26); years, months and days of one sign (Operation 22). Over: the old Date’s roll-over into the next month (January 31 plus one month as March 3); a choice the atom makes alone; mixed signs read in some order. Because: the ruling names these decisions as the answer key, and each is settled in Temporal’s design and in RFC 5545; Invariant 4.1 states the roll-over this atom never makes.

  • 2026-11-08 — A reading follows the calendar in the reader’s place. Chose: the relative days today, yesterday, tomorrow, current-week, last-week, current-month, last-month and full-date, decided by the read date’s and the reader’s date’s calendar days, weeks from the place’s week start and calendar months (Operation 28 through 36), never by the hours between (Invariant 3.1); current-week shown by the day of the week, and every reading carrying the exact local date, local time and offset (Operation 37). Over: a count of elapsed time (“12 hours ago”, “previous 30 days”); a fixed week start. Because: the maintainer ruled on 2026-11-06 that a date reads today, yesterday, last week, last month and then the date itself, by calendar boundaries in the reader’s place, so last month means the previous calendar month, with the exact date and time always one tap away; current-week, current-month and tomorrow fill the calendar between the ruling’s names, and a place’s week start says where its weeks begin.