Skip to content

Latest commit

 

History

34 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 

Repository files navigation

Why "Quantum" Calendar?

Because the adjustment is not done by a mechanical leap day. It is done by measuring the year's duration in atomic seconds and extending or contracting the final day by exactly the required number of seconds — down to the nanosecond — using quantum-precise timekeeping.

The word "quantum" signals:

· Precision at the atomic scale · No astronomical guessing · Full determinism via cesium clocks

  • 365÷12 = 30.41666666666666667 day / month

  • 0.4 day + extra hour

  • 1,3,6,9,12 .. 31 day / months

    The Calender has exactly 365 day the extra drift is deducted from the 1st day of the New Year (Substraction Day) ... thus every beginning of the years starts with a flex day ..

Working Example:

The first year ( 0 Year ) starts at Y2K or Gregorian Year 2000 ... but nothing happens there yet .. it's in it's DarkAges like in the BB .. truthfully its the Leap Year in the Gregorian Calendar do start clean at 2001.

The first light start at Monday 1 January 2001 ( 1st day of Quantum Calendar Year 1) alongside the Gregorian Calendar with the Zero day or Hours on Sunday last day of the Year 2000.

The month strictly follows 1-3-6-9-12 with 31 day period else is 30 days.

At the end of the year 2001 the extra drift or the 31 day of December is extended 5:48:43 hours.

Meaning The New Year of 2002 Starts precisely at Dawn 5:48:43 AM UTC while the day is shorter than other usual 364 days.

Than the drift will shift New Year of 2003 at 11:37:26 AM do forth .

This pattern will continue until it overlaps a day of the New Year thus completing it's replacement of the leap day in the Gregorian calendar.

There is no seasonal drift everything is still intact and realigns with the Gregorian Calendar after 4 years but a different challenges will arise . ( Banking Journal Closing , Clock reprogramming..etc )

Its a New Computing , Global , Accounting Challenge minus the inefficient, messy & inaccuracies of the current system.

Temporary iteration for order vs entropy in the glitch

It could mark the beginning of the rhetorical (±1 days / 80000 years ) of the 8th day ..

  • But it's not complete error free (±1d/80000y) .. since 2 day is elongated and shorter.. there be a day where a day is exactly 48h and there be no New Year or starts precisely at 2nd January on that special year which marks The next Millineum Bug in the Quantum Calendar System.. but this only happens once every ~80000 years

  • No matter what the length of the year is precisely 365:05:48:53:±2

  • No rules broken ( 7 days a week , 12 months , no Seasons drift , 60 sec 60 min 24 h )

  • exception:

    1. No leap year & day
    2. Months with 31 .. 1,3,6,9,12 (ordered)
    3. 2 Special Flex days end of the year.
    4. 365:05:48:53:±2 / year
    5. ±1 day / 80000 year of a Bug weekday.
    6. 4 year sync cycle with Gregorians
    7. Omitted 0 year since Year 2000 was a leap year in the Gregorian. Start clean.
    8. Gregorian_C 2001 = Quantum_C 1st year
    9. Gregorian Monday January 1st 2001 is the first day or (w2/d1/m1/y1Q).. meaning w2=weekday2=Monday, d1= date 1st , m1= 1st months, y1Q = year 1 Quantum.
    10. 31st of the last day of the year is elongated while the next day has a shorter day and must end at midnight to mark the next day or 2nd January.
    11. The New Year is celebrated on the flex hours where the years end by the accumulation of 5:48:53 each year.. never a same New year celebration.
    12. Some New Years could only last for a second.
    13. Precision format (hh:mm:ss:mi:Wd:Dt:Mt:QY:Tz:Dst:Ev:Pl:St:Gx:CMB:MV) or hours , minutes, second, millis , weekday, date , months, Quantum year , Timezones , Daylight saving time, Elevation , Planet , Star System , Galaxy , Cosmic Microwave Grid & MultiVerseType .. if applicable in the near future..

New Fixed Quantum Calendar System : (28/4/26)

1.Constant elongated/Short New Year starts exactly at 5:48:43 AM.

  1. 1 hour distribution over 6 alternate 30 days months with extra 1 hours * 5 month + 48 min 43 sec * 1 month ( October).
  2. Month 2,4,5,7,8 extra 1 hours + remainders 10th month ..like DST = -5:48:43
  3. Bug resolved.
  • But finally i realized its wrong...

  • You can deduct day to compensate extra 5:48:43 .. that's just plain stupid

  • Than i thought about making it 366 day ..than substract from there.. remainder is the date next day..than there be extra hour in a year.. that ain't right either.. so Gregorian the best for now with a leap day every 4th year..

S&G c/o Suren (Gregorian 23/4/26 8:06 AM UTC+8)

About

... A solution to leap year

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors