time: the zone database (TIME.md, the last slice of FIRST-PARTY gap 11) #755

New issue

Open

opened 2026-11-13 12:39:38 +00:00 by orion · 0 comments

orion commented

2026-11-13 12:39:38 +00:00

Collaborator

Context

docs/design/TIME.md is "designed, not built (2026-10-25)": std/time has Date, TimeOfDay, DateTime, UtcOffset and OffsetDateTime (#111, #387, #388) and no zone such as Europe/Berlin. The design was closed with #389; no issue tracks the build. A date library without zones cannot answer "what time is it there", and the web and framework milestones need it.

Source

Cleanup audit 2026-11 (#742), finding F11; the report is docs/project/2026-11-cleanup-audit.md.
docs/design/TIME.md sections 1 to 9.

Goal

The slices of TIME.md section 9, in the record's order, starting with the first: the zone type, the data source of section 2 within the size of section 3, the capability of section 4.

Design record point

docs/design/TIME.md sections 1 (what is decided), 2 (where the data comes from), 3 (size), 4 (capability), 6 (the API), 7 (POSIX rules after the last transition), 9 (slices).

Acceptance criteria

Each slice of section 9 is a checklist line here before the first one starts, with the acceptance test the record names for it
Slice 1 lands with its tests on tier A and tier B
The status line of TIME.md names the built slices after each PR
The four gates and the fixpoint are green

Dependencies

None for slice 1. The data source of section 2 may touch the release pipeline (the size budget of section 3); that part is named when it is reached.

Seed

None.

Size

One PR per slice of section 9; this issue becomes an epic if the record has more than three slices.

## Context `docs/design/TIME.md` is "designed, not built (2026-10-25)": `std/time` has `Date`, `TimeOfDay`, `DateTime`, `UtcOffset` and `OffsetDateTime` (#111, #387, #388) and no zone such as `Europe/Berlin`. The design was closed with #389; no issue tracks the build. A date library without zones cannot answer "what time is it there", and the web and framework milestones need it. ## Source - Cleanup audit 2026-11 (#742), finding F11; the report is `docs/project/2026-11-cleanup-audit.md`. - `docs/design/TIME.md` sections 1 to 9. ## Goal The slices of TIME.md section 9, in the record's order, starting with the first: the zone type, the data source of section 2 within the size of section 3, the capability of section 4. ## Design record point `docs/design/TIME.md` sections 1 (what is decided), 2 (where the data comes from), 3 (size), 4 (capability), 6 (the API), 7 (POSIX rules after the last transition), 9 (slices). ## Acceptance criteria - [ ] Each slice of section 9 is a checklist line here before the first one starts, with the acceptance test the record names for it - [ ] Slice 1 lands with its tests on tier A and tier B - [ ] The status line of TIME.md names the built slices after each PR - [ ] The four gates and the fixpoint are green ## Dependencies None for slice 1. The data source of section 2 may touch the release pipeline (the size budget of section 3); that part is named when it is reached. ## Seed None. ## Size One PR per slice of section 9; this issue becomes an epic if the record has more than three slices.

orion added the

loop

label

2026-11-13 12:39:38 +00:00

orion referenced this issue from a commit

2026-11-13 12:41:00 +00:00

docs(project): add the cleanup audit of November 2026

orion referenced this issue

2026-11-13 12:41:31 +00:00

docs(project): add the cleanup audit of November 2026 #756

orion referenced this issue

2026-11-13 12:41:38 +00:00