Leap Year Correction

mechanism

A calendar turns a fractional natural cycle into whole civil days. The leftover hours accumulate as drift until a leap-year correction brings the date grid back toward the solar cycle.

Makar Sankranti does not simply wander at random: it arrives about six hours later each year, then jumps back after a leap year. The festival exposes a mismatch hidden inside the calendar itself.

E1

The quarter-day the calendar cannot display

A civil calendar counts whole days, but the year is about 365.25 days. After assigning 365 days to the grid, roughly six hours remain. Those hours do not disappear: they accumulate, pushing the same solar event later against the calendar each year. A leap day periodically absorbs the accumulated remainder, producing a repeating pattern of gradual drift followed by correction. This is a Discretization Tradeoff: the grid becomes convenient by rounding a continuous cycle, then needs a rule to repair the rounding error.

E1

Where it shows up

Sankranti’s four-year sawtooth

Following Makar Sankranti across successive years reveals the mechanism directly: later by roughly six hours each year, then earlier again when the leap-year adjustment enters the calendar.

E1

Not every moving date is a leap-year problem

This mechanism explains the short repeating shift caused by fitting a fractional year into whole days. It does not, by itself, explain drift between calendars anchored to different things—such as seasons, stars, solar boundaries, or lunar cycles. For those cases, first check for a Reference Frame Mismatch.

Look for the reset before blaming the date

When an annual event appears to move, record its date and time across a leap-year boundary. A steady annual delay followed by a leap-year jump is evidence of accumulated fractional days being corrected; drift without that reset points you toward a different mechanism.

E1

Episodes that teach this