Why a time-zone update can redraw an old chart
A birth chart calculation starts with a local clock reading, but astronomical positions are calculated for a precise moment. Software must therefore translate the recorded time—say, 2:15 a.m. in a particular town—into a universal timestamp. To do that, it needs the town’s time-zone rules for the birth date, including whether daylight saving time was in effect.
Those rules are political, not fixed laws of nature. Governments can change their clocks, and time-zone databases can also correct older records. When an app updates its database, the conversion for a past birth may change. A chart stored only as a finished graphic can keep showing the old result; one rebuilt from the birth details may produce a different one.
Why a small clock change can matter
A different universal timestamp changes where the planets are in their apparent motion at that moment. For a shift of an hour, most planetary positions move only a little. But chart features tied closely to the exact local time—especially the Ascendant, the sign rising on the eastern horizon, and the house divisions—can change more noticeably. Near a sign boundary, even a modest shift can move a feature into a neighboring sign.
This is why the same birth information can yield different results across software versions or apps: they may use different historical time-zone data, or one may have already recalculated the chart. The practical fix is to check the recorded birth time and location, and whether the app has applied the relevant historical clock rule. A local policy change can thus reach backward into a personal chart—not by changing the sky, but by changing the timestamp used to map it.
