Case 09 of 26

Historical time zones

Lord Howe: a 30-minute DST offset

Not every daylight-saving transition is a full hour.

Boundary question

Does the time-zone adapter preserve Lord Howe's 30-minute DST rule?

Yes. The receipt records UTC+11:00 with a 30-minute DST component instead of assuming 60 minutes.

Synthetic input

Recorded facts

Date
2025-01-15
Recorded time
12:00
Location
Lord Howe Island, Australia
Time zone
Australia/Lord_Howe
Longitude
159.0800°
Gender input
Female

Pinned expected facts

Verified output

build verified

Year

甲辰

Month

丁丑

Day

甲申

Hour

庚午

Day Master
甲
True solar time
2025-01-15 11:27
Total correction
-32.31 minutes
Historical offset
UTC+11:00 · DST 30 min
Luck direction
逆排
Reference Jie
小寒 · 2025-01-05 10:32:47
Luck start
2028-05-20 01:15:41

Reading the boundary

What this case means for your own chart

Not every daylight-saving shift is a full hour. Lord Howe Island, off the east coast of Australia, uses a thirty-minute offset during its summer. A calculator that assumes sixty minutes whenever DST is detected will place this record half an hour away from where it belongs.

Half an hour rarely matters in the middle of a two-hour branch, which is exactly why the bug is easy to ship and hard to notice. It matters enormously when the record sits near a pillar boundary, because then thirty minutes is the whole difference between one hour pillar and the next.

This case is included because it is the kind of assumption that survives testing against comfortable data. Reading it, the useful question is not whether you were born on Lord Howe Island, but whether the tool you used has ever been checked against a place whose rules are unusual.

The general form of the problem is wider than daylight saving. Any place where the civil clock has been set by political decision rather than by geography can carry a surprise: a half-hour offset, a date line moved for trade, a wartime clock kept after the war. The cases in this category are samples of that class, not a complete catalogue of it.

Check your own record

  1. If you were born somewhere with unusual time rules, verify the offset from a historical record rather than assuming a whole-hour DST shift.
  2. Check whether your chart changed when you tested it against a different birth location in the same timezone. If the tool ignores location, that is a warning sign.
  3. For any record within about thirty minutes of a pillar boundary, treat a half-hour uncertainty as decisive.

Which convention is in play

Calculation fact
The pinned engine preserves the thirty-minute DST component and returns UTC+11:00 with 30 minutes of DST for this Lord Howe input.
Convention
Nothing here is a Bazi convention question. It is a timezone-database question that the tradition inherited rather than created.
Our explanation
Choosing an unusual timezone as a benchmark case is our decision. We use it to test the adapter rather than to make a claim about Bazi practice.

Conventions and limits

What this case does — and does not — prove

It verifies

Deterministic reproduction of this input under the named engine version and conventions. A pinned-field mismatch stops the production build.

It does not claim

Universal agreement across Bazi schools, interpretation of a real person, or certainty where the historical record is incomplete.

tyme4ts 1.5.2 · cantian-tymext 0.0.27 · sect 2 day boundary · BaziCalculator.ai NOAA/IANA true-solar adapter
calculation-benchmarks-v1 · reviewed 2026-09-05