On 2 March 2026, British Columbia did something rare in public life. It gave people what they asked for, and eight months to get ready. The Office of the Premier announced that the 8 March spring-forward would be the province’s last, and that “the change planned for Nov. 1, 2026 will not happen.” BC Pacific time became UTC-7 year-round. The mandate came from a 2019 public engagement with a record 223,000 participants, 93% of them in favour. Premier David Eby put it the way only a parent could: changing clocks twice a year “causes a significant amount of chaos on already busy lives.”

Then the rule went where time rules go: into the tz database, the small, volunteer-maintained table that tells nearly every computer on Earth what time it is. Alexander Krivenyshev of WorldTimeZone.com posted the notice to the IANA tz list. On 23 April, Paul Eggert announced release 2026b: “British Columbia moved to permanent -07 on 2026-03-09.” With unusual candour he explained that, to work around a limitation in Unicode’s CLDR v48.2, the data would “temporarily model the change to occur on 2026-11-01 at 02:00,” and that “this temporary hack is planned to be removed after CLDR is fixed.” That is what good maintenance looks like: on time, honest about the seams, signed with a name. The people who keep the world’s clocks agreeing are invisible precisely because they work. In April, they did their job.

1 November, 02:00

The clocks fell back anyway. As Drive Tesla’s Darryn John reported, Teslas on software 2026.38.3.2 or 2026.38.5.1 without FSD set themselves back an hour, and owners could not correct the time by hand. Update 2026.38.5.11 fixed it on a Model Y by Monday afternoon. Its release notes “only mention security fixes and improvements.” Which, technically, it was.

9to5Google’s Ben Schoon found Nest Hubs and Nest Thermostats in parts of Canada skipping the memo too: late alarms, broken automations, shifted schedules. Google acknowledged “a small subset of devices in some provinces in Canada”; as of 4 November the fix was not yet live. And where clocks did change, Apple’s support note of 30 October explains that after a DST change the Watch may be an hour off “only on the Always On display when your wrist is down.” Raise your wrist and it is right. Do nothing and “the issue will resolve itself at midnight.” Schrödinger’s wristwatch, with an official support article.

None of these companies has said why, so no diagnosis here, only the shape. The rule changed once, at its source. It also lived in many copies, each frozen at some moment and shipped inside a car, a thermostat, a watch face. On 1 November, several of the copies won.

←TODAY: One province changed one line of law; three of the world’s largest device makers showed the old hour. →3012: The rules that last are the ones whose every copy can be found, read and updated by someone who wasn’t there. Fulcrum: A rule is only as current as its oldest forgotten copy.

Your office runs on frozen copies too

Swap “time zone” for “norm”. When an SIA standard is revised, the new edition arrives once. The old value keeps falling back for years: in the Archicad template someone built three partners ago, in a snow-load constant typed straight into a Python script, in a library object’s default U-value, in last year’s PDF on the shared drive. No vendor pushes an over-the-air update to your office template. You are the maintainer. From where I sit, decades on, the buildings that caused the long arguments rarely had the wrong idea. They had the right idea and an old number nobody knew was still in there.

Atelier: Offices now letting AI assistants draft scripts and schedules are multiplying the copies, because every generated snippet freezes whatever value the model or the prompt happened to carry. Monday move: create one rule_register.csv in the project root (value, norm, edition, date, file where it lives) and make every script read its constants from that file instead of typing them.

Hack: Ask your own machine whether its copy of the tz table knows about British Columbia. Python’s zoneinfo reads the system database, or the tzdata package where there is none (Windows), so the answer depends on which copy you actually have. Under 2026b, noon on 2 November in Vancouver is UTC-7; UTC-8 means you are holding a frozen snapshot.

from datetime import datetime
from zoneinfo import ZoneInfo
t = datetime(2026, 11, 2, 12, tzinfo=ZoneInfo("America/Vancouver"))
print(t.utcoffset())  # "-1 day, 17:00:00" = UTC-7 current; "-1 day, 16:00:00" = UTC-8 frozen

The same pattern works for norm values: one lookup, one expected answer, run before every issue date. If you want that register wired into Archicad itself, it is exactly the kind of script the PAZ Archicad Python course builds.

Open your office template, find one hard-coded norm value, and write down its edition and date. Then go find the next one.