8) Where the Irregularity Goes
Seasons, Familiarity and Other Trade-offs

Every Martian calendar has to put the inconvenience somewhere.

Mars presents a physical fact; the designer decides which human property to preserve around it. Twelve months can be long or twenty-four can be short. Weeks can continue without interruption or dates can retain fixed weekday relationships. Equal elapsed periods can be preserved, or civil divisions can carry more information about orbital position.

The arithmetic does not remove these choices. It merely makes them unavoidable.

The same problem appears with seasons. A calendar can divide the Martian year into periods containing similar amounts of elapsed time, which helps planning, comparison and administration. Or it can make those periods correspond more closely to equal movements of Mars around the Sun, giving them stronger orbital and seasonal meaning. Mars does not let those properties coincide neatly because it does not travel around the Sun at constant speed.

Then another requirement arrives from an entirely different direction: familiarity. The first generations living on Mars will not arrive without temporal habits. They will bring decades of intuition about weeks, months, birthdays, school years and phrases such as “next February”. Familiar structures can reduce the burden of learning a new calendar.

They can also mislead.

The remaining trade-offs are therefore less about clever arithmetic than about deciding what kind of interface should sit between the planet and the people using it.

Equal time or equal season?

There are two obvious ways to construct a Martian month.

The first is to divide the year into periods containing roughly equal numbers of sols. A 56-sol month then represents almost the same amount of elapsed time as every other 56-sol month. Planning becomes easier, comparisons become cleaner, and a project given one civil month in one part of the year receives much the same amount of time as a project given one elsewhere. The calendar behaves rather like a ruler.

But Mars's orbit is eccentric enough that equal intervals of time do not correspond to equal intervals of orbital movement. Mars travels faster around the Sun in some parts of its orbit than others, so a 56-sol period covers more orbital angle in one part of the year than in another.

If the purpose of the month is to measure elapsed civil time, that may be perfectly acceptable. If the purpose is to tell us where Mars is in its seasonal orbit, it is less satisfactory.

Robert Zubrin's twelve-month proposal gives greater weight to the second objective. Instead of making months roughly equal in elapsed duration, it divides the orbit into twelve equal angular sectors of about 30 degrees each. Every month therefore has a clear orbital meaning.

The price is unequal duration. Because Mars travels through those sectors at different speeds, some months contain materially more sols than others. “One month” no longer describes a particularly stable amount of elapsed time.

That matters where comparable duration is valuable. Financial periods become less equivalent. Administrative intervals vary. A one-month project in one part of the year may have more working time than a one-month project elsewhere.

None of this makes the architecture defective. It tells us what the architecture is trying to preserve. Zubrin gives the month stronger orbital meaning; a calendar optimised for regular civil operation might reasonably choose differently.

Hargitai and colleagues provide a useful contrast. Their 12 × 56/270 calendar was designed for presenting Martian climate data rather than prescribing the civil life of a future settlement. Eleven months contain 56 sols, while the final month absorbs the remaining annual difference; the year begins near Ls = 270°.

Most of the calendar therefore consists of identical elapsed-time blocks. For climate-data comparison, that is useful: a researcher comparing one 56-sol period with another is comparing equal amounts of time even though Mars has moved through different amounts of its orbit.

Zubrin and Hargitai begin from different users. One asks how calendar divisions can carry stronger information about orbital position. The other asks how data can be presented in conveniently comparable blocks.

Same Mars. Different brief.

Where should the irregularity go?

The Hargitai design exposes another recurring decision in calendar architecture. Suppose most of the year consists of identical 56-sol periods. The fractional Martian year still has to be reconciled somewhere, so the design concentrates much of that awkwardness in the final month.

That is a perfectly coherent strategy. Most months become exceptionally simple; one becomes conspicuously different.

Another design could distribute the same inconvenience more evenly through the year. Instead of one markedly unusual terminal period, several periods could be slightly shorter. Neither approach makes irregularity disappear. They decide where people encounter it.

This is one of the recurring themes of calendar design: one large exception or several small ones; a rare substantial correction or more frequent minor ones; irregular months or irregular years; floating dates or interrupted weekday labels. The arithmetic can tell us which arrangements are possible. It cannot tell us which inconvenience users will prefer.

There is also a limit to how much seasonal information a civil calendar should be expected to carry in the first place.

Mars's seasons are real, but its orbital relationships do not remain perfectly frozen over very long timescales. James Fairman's work on Martian calendar design has highlighted the resulting problem of seasonal dissonance: a fixed tropical civil calendar cannot permanently lock every desirable relationship among calendar position, seasonal events and other features of orbital geometry.

That is a useful warning against asking too much of the calendar. A civil month can provide useful seasonal orientation without replacing Ls. Scientists and engineers already have better tools when precise orbital or seasonal position matters. Environmental systems can use ephemerides; mission planning can use actual geometry.

More astronomy embedded in the civil calendar is not automatically better. The useful question is how much astronomical information ordinary civil users gain from having it there.

Familiarity helps — until it misleads

Seasonal fidelity is not the only thing competing with regularity. There is also the slightly less glamorous question of whether anybody wants to use the calendar.

Familiarity is easy to undervalue because it is difficult to express in equations. Yet familiar interfaces reduce training, cognitive effort and certain kinds of error. They allow people to transfer existing mental models rather than rebuilding everything from scratch.

The first Earth-born settlers will know January and Monday. They will know what birthdays, quarters, school terms and “next month” feel like. Discarding all of that has a cost.

Dennis Silin's Exodus Calendar gives familiarity unusually high weight. It retains twelve terrestrial month names and familiar weekday terminology. January through November contain 56 sols, while December absorbs the remaining annual adjustment under its intercalation cycle.

The design therefore asks a question very different from Zubrin's: how much unnecessary relearning should settlers be asked to do?

That is a legitimate design problem. A calendar that is mathematically elegant but unnecessarily difficult to adopt has not escaped human factors merely because the arithmetic works.

Exodus preserves several recognisable pieces of the terrestrial interface at once. January still follows New Year. February follows January. December still ends the sequence. What changes is what those words represent.

An Exodus January lasts 56 sols rather than 31 Earth days. The familiarity is therefore real, but incomplete, and that creates the central problem with familiar nomenclature.

Suppose someone is told:

Your appointment is next February.

The phrase is immediately understandable. But if February now lasts 56 sols, it no longer behaves like the February that an Earth-born user has known for decades.

The same difficulty appears with “monthly”. Does a monthly payment now recur every 56 sols because the civil period is called a month? Or was the institution trying to preserve something closer to the four-week cadence associated with terrestrial monthly life?

A new term forces people to learn more. An old term can encourage them to assume more.

There is no cost-free interface.

This is why names are not merely decoration applied after the calendar has been designed. They tell users what sort of thing they are looking at and invite comparisons with things they already understand. Familiarity can reduce cognitive load, but it can also create false equivalence.

A robust calendar therefore needs some separation between structural identity and human-facing language. Computers and archives need stable definitions; culture does not need to be frozen forever. Future Martians may retain terminology proposed on Earth, alter it beyond recognition or allow different communities to use different names for the same structural period.

All of that is normal. The machinery needs stable identities. It does not need to win an argument about what people should call them three centuries from now.

Simple for whom?

The familiarity argument reveals another slippery word in calendar design: simple.

A calendar with familiar month names may be simple to learn. One with equal elapsed periods may be simple to calculate. One with fixed recurring dates may be simple to schedule. One with a continuous seven-sol week may be simple socially. One with equal-angle months may be simple astronomically.

These are different kinds of simplicity, and improving one can make another worse.

So the claim that “the simplest Martian calendar would be…” is usually missing two questions:

Simple for whom?

Doing what?

A scientist analysing seasonal data, a school administrator, an Earth-born migrant and a software engineer can all have legitimate but different ideas about what simplicity means.

The same is true of familiarity. Someone arriving from Earth may value recognisable month names enormously. Someone born on Mars fifty years later may regard terrestrial nomenclature as historical baggage. We do not know.

The useful design response is not to pretend that those preferences are measurable astronomical quantities. It is to make the technical consequences of each choice clear.

Different briefs produce different calendars

The major approaches considered so far become easier to understand when they are compared by the property receiving greater weight.

There is no score hidden in the table. Each approach protects something people might reasonably value, and each pays somewhere else.

Astronomy strongly constrains the available design space. Mars determines the length of its sol and year. Its orbital eccentricity and axial tilt are physical facts. No calendar can vote them away.

But those facts do not tell us whether Mars should have twelve months or twenty-four. They do not tell us whether civil periods should favour equal elapsed time or equal orbital angle. They do not tell us whether uninterrupted weekday succession matters more than fixed recurring dates. They do not tell us whether future inhabitants should use terrestrial names, modified ones or vocabulary that has not yet been invented.

Those are design choices.

Different answers can therefore produce technically coherent calendars without one designer having misunderstood the astronomy.

There is no secret calendar in the orbit

It is tempting to imagine that sufficient mathematics will eventually reveal the correct Martian calendar. Calculate the orbit precisely enough, search enough month patterns, optimise the intercalation rule and minimise irregularity, and eventually one architecture must surely emerge as objectively best.

It will not.

Mathematics can identify bad arithmetic. It can measure drift, quantify unequal durations and seasonal displacement, and show when two desired properties cannot coexist under a particular set of rules. What it cannot do is tell a future civilisation how much it should value an uninterrupted week relative to a fixed recurring date, or whether twenty-four familiar-duration periods are preferable to twelve annual ones.

Those are judgements about civil use.

That is why Levitt, Darian, Zubrin, Šurán, Hargitai and Exodus are more useful as different architectures than as contestants in a tournament. Each makes visible a different allocation of weight among legitimate requirements.

There is no secret calendar hidden in the Martian orbit waiting to be discovered. Mars supplies the constraints. The design begins when people decide which human properties matter enough to preserve within them.