E - Earth-Mars Reference

Conversion, Clock Drift and the Month-Gap Heuristic

E.1 Purpose

Marian is a local civil calendar for Mars. It is not intended to isolate Martian chronology from Earth.

Any permanent settlement would remain connected to terrestrial families, organisations, governments, scientific systems, archives and legal frameworks. Marian dates must therefore be capable of deterministic conversion to Earth-referenced chronology while remaining locally meaningful on Mars.

This appendix summarises that relationship.

It covers four distinct issues:

• conversion between Marian and terrestrial chronology;
• the changing relationship between a Martian sol and UTC;
• the changing Earth–Mars communications delay; and
• the circular month-gap heuristic, which uses the two calendars' twelve-part annual structures to provide coarse intuition about Earth–Mars orbital geometry.

These should not be confused with one another. Calendar conversion can be exact once the epoch is established. The month-gap relationship is deliberately approximate.

E.2 Two calendars, one physical timeline

A single event can legitimately carry several temporal coordinates.

A message transmitted from Mars might be recorded locally as:

MY42-08-03-05

The same event could also carry:

• a Gregorian date;
• a UTC or other terrestrial timestamp;
• Mars Sol Date;
• Ls;
• local Martian clock time; and
• precise ephemeris information.

These representations answer different questions.

The Marian Civil Date answers:

Where does this event sit in Mars's civil calendar?

The Gregorian date answers the equivalent civil question for Earth.

A continuous or absolute timescale provides the technical bridge between them.

Interplanetary chronology should therefore be understood as translation among coordinate systems, not as one world's calendar replacing the other's.

E.3 Conversion requires the Marian epoch

Absolute conversion cannot be completed until the Marian epoch exists.

MY0 begins at the recognised first human step on Mars. MY1 begins at the first Airy-0 midnight following Mars's next passage through:

Ls = 15°

The timestamp of that future event is not yet known.

Before the epoch exists, Marian dates may be mapped against synthetic or hypothetical epochs for modelling and testing. They cannot yet be given authoritative Gregorian equivalents.

Once the start of MY1 has been instantiated against an agreed absolute timescale, conversion becomes deterministic.

Conceptually:

Marian Civil Date → Marian ordinal sol → offset from MY1 → absolute chronology → Gregorian/UTC

and in reverse:

Gregorian/UTC or absolute chronology → offset from MY1 → Marian ordinal sol → Marian Civil Date

Appendix D defines the Marian integer arithmetic on either side of that bridge.

A future implementation standard will need to define the exact astronomical and timescale conventions used for the bridge itself.

E.4 Conversion is not synchronisation

The ability to convert perfectly between two calendars does not mean that their dates remain aligned.

They cannot.

Earth and Mars have different:

• day lengths;
• year lengths;
• month structures; and
• intercalation systems.

A particular Gregorian date therefore moves through the Marian year over time, just as a particular Marian date moves through the Gregorian calendar.

There can be no permanent equivalence such as:

1 Janiix = 3 January

Any such coincidence would immediately begin to drift.

Cross-world systems therefore need a conversion function, not a permanent date lookup table.

That distinction matters for birthdays, holidays, accounting periods, contracts and any institution operating on both planets.

E.5 The Martian sol and terrestrial elapsed time

A Martian mean solar day lasts approximately:

24 hours, 39 minutes and 35 seconds

of terrestrial elapsed time.

The difference from an Earth day is therefore approximately:

39 minutes and 35 seconds per sol

or about:

2.75 per cent

This similarity is enough to make the Martian sol intuitive as a human civil day.

It is not enough to keep Martian and terrestrial clocks synchronised.

E.6 Airy-0 midnight drifts through UTC

Suppose, purely for illustration, that one Airy-0 midnight happened to coincide exactly with:

00:00 UTC

The following Airy-0 midnight would occur approximately at:

00:39:35 UTC

The next roughly at:

01:19 UTC

and the next around:

01:59 UTC

The offset continues to move because each Martian sol is about forty terrestrial minutes longer than an Earth day.

After approximately 36 to 37 sols, the Martian daily boundary has moved through an entire terrestrial 24-hour clock.

This cycle then continues.

A Martian local working day therefore has no permanently fixed relationship with London, New York, Tokyo or any other terrestrial time zone.

E.7 Operational consequence of clock drift

An Earth–Mars organisation cannot rely on a fixed rule such as:

Mars office hours overlap London from 14:00 to 17:00 UTC

The overlap itself moves through the terrestrial day.

At one stage, Martian working hours may align conveniently with Europe. Later they may align better with North America. At another point, the same nominal Martian working day may fall across inconvenient terrestrial night hours.

This is not caused by Marian. It follows from the physical difference between the terrestrial day and the Martian sol.

Software should therefore calculate current local-time relationships rather than relying on a permanent offset.

The infrastructure should perform the conversion.

People should not have to.

E.8 Communications delay is a separate problem

Clock drift is not the dominant constraint on Earth–Mars communication.

The larger difference comes from changing physical separation.

Earth and Mars move independently around the Sun, so their distance varies substantially. In the Marian analysis covering 2031–2120, modelled one-way light time ranged approximately from:

3 minutes to 22 minutes.

A three-minute one-way delay already means that a question and reply require more than six minutes of signal travel before either participant's thinking or response time is included.

At roughly twenty-two minutes each way, the physical minimum for a question-and-answer exchange approaches three quarters of an hour.

This is not a terrestrial video call with unusually bad latency.

It is asynchronous communication.

E.9 Two twelve-part annual maps

Gregorian and Marian calendars share one useful structural property:

both divide their local years into twelve months.

The months are very different lengths, and the two years do not proceed at the same rate. The shared twelve-part structure nevertheless allows their annual positions to be compared visually.

Marian's annual anchor at Ls = 15° was chosen partly because, around the intended founding era, Mars at Marian New Year lies close to the broad heliocentric direction associated with Earth around Gregorian New Year.

Very approximately:

Gregorian Month 1 and Marian Month 1 begin from similar directions around the Sun.

As the two planets progress around their orbits at different rates, the two month numbers move apart and later return towards one another.

That difference provides a simple mental model of their broad relative orbital phase.

E.10 Circular month gap

Let:

g = Gregorian month number, from 1 to 12

and:

m = Marian month number, from 1 to 12

The absolute numeric difference is:

|g − m|

Because the calendars are circular, the shorter distance around the twelve-position ring is:

G = min(|g − m|, 12 − |g − m|)

where:

G = circular month gap

and:

0 ≤ G ≤ 6

For example:

Gregorian Month 4, Marian Month 5

gives:

G = 1

while:

Gregorian Month 1, Marian Month 7

gives:

G = 6

The circular treatment matters because:

Month 12 and Month 1 are one position apart, not eleven.

E.11 Month-gap reference table

The modelling used in Marian found the following median one-way Earth–Mars light times for each circular month gap:

These values come from the underlying Earth–Mars analysis used in the Marian design and should be treated as empirical summary values for that modelling interval, not immutable physical constants.

The progression is nevertheless clear enough to be memorable:

Gap 0–1 → generally shorter-delay conditions

Gap 2–4 → intermediate conditions

Gap 5–6 → generally longer-delay conditions

The heuristic therefore provides broad orientation rather than precision.

E.12 Worked examples

Suppose a display shows:

Earth: Month 3
Mars: Month 4

Then:

G = min(|3 − 4|, 12 − |3 − 4|)

G = 1

The historical modelling suggests that this belongs towards the shorter-delay end of the Earth–Mars communications cycle.

Now suppose:

Earth: Month 4
Mars: Month 10

Then:

|4 − 10| = 6

so:

G = 6

That places the relationship towards the longer-delay end.

A user does not need to know the planets' instantaneous coordinates to acquire a rough expectation that the second situation is likely to involve substantially more latency than the first.

E.13 What the heuristic means

The month-gap relationship works because the two month numbers provide rough annual positions around two heliocentric orbits.

When those annual positions are close, Earth and Mars tend to occupy more similar broad directions from the Sun.

As the circular gap grows, their angular separation generally grows as well.

That broad relationship is reflected in the median light-time data.

The month gap can therefore be useful as:

a civil orientation heuristic

It should not be treated as:

a communications instrument

That distinction is essential.

E.14 Why the heuristic is approximate

Several effects prevent month gap from determining exact Earth–Mars distance.

First, Earth and Mars do not travel on perfect circular orbits.

Their heliocentric distances vary, so similar angular relationships can correspond to different physical separations.

Second, neither civil month system divides its orbit into equal angular sectors.

Gregorian months are unequal elapsed periods. Marian months contain 55 or 56 sols.

Third, orbital speed varies throughout both planetary years.

Equal fractions of civil time therefore do not correspond to equal amounts of orbital longitude.

Fourth, the month gap compresses a continuous geometric relationship into only seven possible values:

0, 1, 2, 3, 4, 5, 6

A large amount of information is deliberately discarded.

E.15 The distributions overlap

The table in Section E.11 gives medians, not deterministic mappings.

A date with:

G = 1

does not necessarily have a shorter actual light time than every date with:

G = 2

Likewise, two dates with the same month gap can have materially different communications delays.

The heuristic describes a broad statistical relationship.

It does not determine the instantaneous geometry.

Applications presenting the month gap SHOULD therefore avoid wording that implies a guaranteed delay.

E.16 Month gap is not a conjunction warning

A circular month gap of 6 does not, by itself, identify solar conjunction.

Operational conjunction conditions depend upon the precise geometry among:

• Earth;
• Mars;
• the Sun; and
• the communications path.

A high month gap indicates broadly unfavourable Earth–Mars orbital separation in the civil model.

It does not determine link safety, solar interference or operational communications availability.

Those require actual ephemeris and communications data.

E.17 Exact latency always wins

Any operation that depends upon actual communications delay MUST use real orbital geometry.

Examples include:

• spacecraft commanding;
• communications routing;
• network buffering;
• link scheduling;
• autonomous-system supervision;
• time-critical scientific operations; and
• remote medical support.

For such applications, the relevant value is ephemeris-derived light time, not a calendar heuristic.

The month-gap model has a different purpose. It allows people to understand, approximately, why communications conditions are currently relatively favourable or unfavourable without requiring them to calculate orbital mechanics.

Its value lies in intuition.

Precision belongs elsewhere.

E.18 Why Ls = 15° matters

The month-gap relationship is related to Marian's choice of:

Ls = 15°

as its annual anchor.

Around the intended founding era, that seasonal position places Mars close to the broad heliocentric direction associated with Earth around Gregorian New Year.

That helps make the two twelve-position annual maps visually comparable.

The logic should not, however, be reversed.

Marian New Year was not defined solely by maximising the month-gap relationship. The design analysis found that nearby synthetic starting positions could marginally improve particular statistical measures.

The annual anchor remains Ls = 15° because it provides a simple Martian seasonal reference with a useful secondary Earth-facing property.

The year belongs to Mars.

Interplanetary legibility is a benefit, not the master constraint.

E.19 The relationship changes over centuries

Ls = 15° is a fixed Martian seasonal reference.

Its particularly neat relationship with Gregorian New Year is not expected to remain numerically identical forever.

Long-period orbital and seasonal relationships evolve. Marian does not respond by moving New Year in order to preserve the cleanest possible Earth-facing heuristic.

Doing so would make the Martian calendar chase a secondary interface property.

If the relationship becomes less tidy in future centuries, the month-gap calibration can be re-evaluated.

The Martian annual anchor should not casually be moved to rescue it.

E.20 Dates and durations must specify their world

Cross-world legal and institutional documents will need more explicit temporal language than terrestrial documents often require.

A statement such as:

payment due within 30 days

is ambiguous between worlds unless the intended unit is specified.

Thirty terrestrial days and thirty Martian sols are different durations.

Likewise:

renewal every year

must identify whether year means a Gregorian year, Marian year or some separately defined contractual interval.

A robust cross-world record may need to identify:

• the governing civil calendar;
• the civil date;
• whether durations use terrestrial days or Martian sols;
• the applicable local-time convention;
• an absolute timestamp; and
• any legal rule governing transmission or receipt across communications delay.

Marian defines the Martian civil coordinate.

It does not define cross-world contract law.

E.21 Recommended interoperable event record

For an event whose precise timing matters across worlds, a robust system might retain several fields:

Not every application needs every field.

The important principle is not to overload one coordinate with jobs already performed by another.

E.22 Earth–Mars date conversion in practice

Once the MY1 epoch is known, a conversion service can be conceptually simple.

For a Marian date:

1. validate the Marian Civil Date;
2. convert it to Marian ordinal sol;
3. calculate the integer sol offset from the start of MY1;
4. apply the authoritative Mars–absolute-time bridge;
5. produce the corresponding terrestrial timestamp and Gregorian display.

For an Earth timestamp:

1. convert the timestamp through the authoritative absolute chronology;
2. determine the corresponding Marian sol relative to MY1;
3. identify the Marian year;
4. determine the ordinal sol;
5. derive Month, Week and Day.

The Marian calendar arithmetic is deterministic.

The absolute astronomical bridge is the specialised layer.

This is another application of Functional Separation: civil dates organise life; continuous timescales connect physical events.

E.23 Conversion software should hide the machinery

Ordinary users should not need to perform these calculations manually.

An interplanetary calendar application could simply display:

Before the real MY1 epoch exists, the terrestrial side remains synthetic.

Afterwards, it can become routine.

The ideal end state is unremarkable:

conversion should be boring.

E.24 Earth–Mars reference summary

The relationship between the two civil systems can be summarised as follows:

The key distinctions are therefore:

conversion is not synchronisation;

calendar position is not orbital position;

month gap is not exact light time;

and:

interoperability does not require uniformity.

Earth can remain on terrestrial civil time.

Mars can develop its own.

A shared technical chronology can connect them without requiring either world to organise ordinary life around the other's calendar.

Two local calendars. One physical timeline. A good interface between them.