COMPARE
21) No Calendar Gets Everything
Marian Among Martian Calendars

The most useful thing about comparing Martian calendars is that they all have the same planet to deal with.

Mars does not rotate differently for Darian. It does not become less eccentric for Zubrin. It does not shorten its year for Exodus or rearrange its seasons for Marian. The physical problem is substantially shared; the civil answers are not.

That tells us something important. Calendar architecture cannot be derived from astronomy alone. Somewhere between the length of the sol and the date printed on a wall calendar, human priorities enter the system.

One design preserves something close to the familiar duration of a terrestrial month. Another preserves twelve annual divisions. One gives orbital position greater weight; another prioritises equal elapsed periods. One protects an uninterrupted weekly cycle; another protects recurring date–weekday relationships. Another reduces the learning burden by retaining familiar names.

Marian adds its own emphasis: several standard civil horizons inside a long Martian year.

The useful question is therefore not which calendar wins. It is:

What is each calendar trying hardest to preserve, and where does it place the resulting inconvenience?

The comparison in one view

The main architectures considered in this book can be reduced to a handful of design choices.

There is no neutral weighting hidden behind the table. A climate researcher may value equal elapsed blocks more than a civil administrator does. A religious community may attach unusual importance to uninterrupted weekly succession. An early Earth-born settlement may place more value on familiar terminology than a later Mars-born population.

The table therefore does not identify a best calendar.

It identifies different design briefs.

Levitt, Darian and Marian: the same arithmetic at two scales

The closest structural comparison to Marian lies in the Levitt and Darian lineages.

Levitt's 1954 proposal uses twelve Martian months arranged in the repeating common-year pattern:

56 – 56 – 55

four times.

That produces twelve primary annual divisions and four equal 167-sol common-year quarters. The cost is obvious: a 55- or 56-sol Martian month is almost twice as long as the terrestrial interval normally associated with the word month.

Darian chooses differently. Its primary months are normally 27 or 28 sols long, much closer to terrestrial month duration, but the Martian year now contains twenty-four primary annual divisions rather than twelve.

The arithmetic relationship between the two approaches is remarkably close. A Levitt-style month is approximately two Darian months.

Marian turns that relationship into an explicit functional architecture. The 55/56-sol scale becomes the Marian month, preserving twelve-part annual orientation. The 27/28-sol scale becomes the Marian minth, preserving the shorter cadence.

It therefore does not resolve the Levitt–Darian choice by declaring one scale correct. It treats the two scales as answers to different questions.

Levitt makes the twelve-part annual scale primary. Darian makes the familiar-duration scale primary. Marian formalises both and assigns them different jobs.

The price is another unit.

Darian users do not need to distinguish between month and minth. Its roughly four-week period simply is the month. Marian accepts additional vocabulary in exchange for making annual orientation and shorter cadence simultaneously explicit.

This is probably the clearest example of Marian's characteristic move: when Mars separates functions that Earth conveniently bundles, give the functions different homes.

Exodus: familiarity versus false equivalence

Exodus places much greater weight on continuity with terrestrial habits.

Its twelve-month structure retains familiar Earth month names. January through November contain 56 sols, with much of the annual adjustment concentrated in December.

That approach takes a serious human-factors position:

people do not arrive on Mars culturally empty.

Early settlers already understand January, Tuesday and a twelve-month year. Preserving familiar structures can reduce the amount they have to relearn.

The trade-off is that familiar names may imply more equivalence than actually exists. An Exodus January is 56 sols long, so it shares a name with an Earth January while describing a substantially different interval.

Marian makes a different interface choice. It preserves recognisable roots while changing the visible labels: January becomes Janiix; Monday becomes Monsol. The intention is not to deny the terrestrial inheritance, but to signal that the Martian unit is not identical to the Earth one.

The contrast can be put simply.

Exodus says:

make the new calendar feel as familiar as practical.

Marian says:

make it recognisable, but visibly Martian.

The structural difference is equally revealing. Exodus concentrates much of the annual irregularity in the final month, allowing eleven months to remain identical at 56 sols. Marian distributes four one-sol reductions through Months 3, 6, 9 and 12.

One concentrates irregularity.

The other distributes it.

Neither removes it.

Hargitai and Zubrin: what should the month represent?

Hargitai and Zubrin reveal another axis of calendar design: should a civil month primarily represent elapsed time or orbital position?

The Hargitai 12 × 56/270 climate calendar gives high priority to repeated equal-duration blocks. Eleven periods contain 56 sols, with the remaining annual difference absorbed by a shorter final period.

For climate-data presentation, that is attractive. Researchers repeatedly compare like with like in elapsed time. The conspicuously shorter terminal period is the price of keeping most of the year in equal blocks.

Marian has a different brief. Its months participate in recurring civil structure, equal common-year quarters and several operating scales. Distributing the shorter periods through the year suits those objectives better than concentrating nearly all the adjustment at the end.

Zubrin moves along another dimension. His twelve-part approach gives stronger weight to orbital progression, so the civil periods carry more information about where Mars sits in its seasonal orbit.

The cost is less equal elapsed duration. Mars moves at different speeds around its eccentric orbit, so equal angular sectors take different numbers of sols to traverse.

Marian assigns those jobs differently. Its civil months remain close to equal in elapsed duration, while precise seasonal position remains available separately through Ls.

Zubrin asks the month to carry more astronomical information.

Marian asks the month to remain a more regular civil interval and lets another coordinate carry the astronomy.

Neither choice is free. Equal elapsed duration and equal orbital angle cannot both be maximised in the same fixed twelve-part structure.

The hardest choice: what happens to the week?

The weekly comparison matters more than the month comparison because a week is not merely an administrative interval. It can become a social rhythm: work and rest, school and family, ritual and recurrence.

This is where Marian makes one of its clearest — and most contestable — design judgements.

Levitt, Darian and Marian all give strong weight to three properties:

• civil years kept tightly around the Martian astronomical target;
• stable month starts;
• invariant recurring Month–Week–Day relationships.

In Marian, those priorities produce 668- and 669-sol civil years, a repeating month structure and dates that retain the same weekday identity from year to year.

The cost is that selected terminal civil weeks contain six weekday positions rather than seven.

The physical point must be stated precisely:

No physical sol is skipped or removed.

There is no circadian discontinuity.

Physical time continues normally.

Mars keeps rotating. One sol follows another. At the end of a 55-sol month, the terminal civil week ends after Day 6 and the next physical sol begins the following month as Day 1 rather than receiving the otherwise expected Day 7 label.

What is interrupted is the civil weekday naming sequence.

That makes the sacrifice social and calendrical rather than physical.

It does not make it trivial.

A continuous seven-sol weekly rhythm may matter deeply to a community. Religious observance may depend upon uninterrupted weekly succession. Work-rest patterns may become socially significant in their own right. People may simply prefer a system in which the seventh weekday always follows the sixth.

Marian asks them to surrender that property in the civil labels in exchange for invariant recurring dates and tightly bounded year lengths.

That is a real trade-off, not a semantic trick.

Šurán shows that another answer is possible

Šurán's work matters because it demonstrates that the Levitt–Darian–Marian solution is not forced by Martian astronomy.

A calendar can preserve both uninterrupted seven-sol weekly succession and fixed recurring dates if its annual adjustment is made in whole weeks.

In the Šurán approach considered earlier, one annual form contains:

96 × 7 = 672 sols

while another contains:

95 × 7 = 665 sols

Every civil year therefore consists of complete seven-sol weeks. The weekly naming sequence remains continuous and recurring dates can retain fixed weekday relationships.

That is an elegant result.

It moves the cost into the year.

The Martian annual target is about 668.6 sols. A 672-sol civil year sits several sols above it; a 665-sol year sits several sols below. A suitable sequence can keep the long-run average aligned, but individual civil years move farther from the astronomical target than Marian's 668- and 669-sol forms.

Šurán therefore protects the week by allowing civil-year correction to occur in seven-sol blocks.

Marian protects tightly bounded individual year lengths by allowing selected terminal civil weeks to end after six weekday positions.

Neither design abolishes the mismatch.

They choose different places to put it.

Marian does not solve the week problem

Modern software weakens one part of the traditional case for perpetual calendars.

A computer does not find it difficult to calculate which weekday 14 March falls on next year. The value of Marian's fixed date–weekday structure is therefore no longer primarily computational.

Its stronger case is that predictable recurrence may still be cognitively and institutionally useful: reusable schedules, stable calendar layouts and dates whose weekday identities are known without lookup.

That benefit has to be weighed against something potentially more fundamental: the social meaning of an uninterrupted weekly cycle.

There is no arithmetic capable of proving which matters more.

Marian's brief gives greater weight to tightly bounded 668/669-sol years, predictable repeating month structure and fixed recurring civil dates than to an uninterrupted civil weekday-label sequence.

That is a design judgement, not an astronomical necessity.

It may be the most contestable decision in Marian.

Marian does not solve the week problem. It chooses where to put the cost.

Four axes explain most of the difference

Once the individual proposals are placed side by side, much of the field can be understood through four recurring design axes.

The first is familiar duration versus familiar annual structure. Darian keeps the primary month near familiar terrestrial duration. Levitt and Marian retain twelve primary annual months. Exodus retains the twelve-month frame and familiar terrestrial nomenclature.

The second is elapsed regularity versus orbital meaning. Hargitai gives high priority to repeated elapsed-time blocks. Zubrin gives more weight to orbital progression. Marian keeps civil periods comparatively regular and delegates precise seasonal location to Ls.

The third is week continuity versus tightly bounded years and fixed recurrence. Levitt, Darian and Marian accept interruptions in civil weekday naming to keep month starts fixed while individual civil years remain close to the Martian target. Šurán preserves the weekly sequence by moving the correction to whole weeks.

The fourth is simplicity of hierarchy versus separation of function. Darian asks its approximately four-week month to remain the primary annual unit. Marian introduces both month and minth because it wants annual orientation and short cadence to remain independently visible.

These axes are more useful than trying to count which calendar contains the fewest unusual features.

An unusual feature is often simply the visible price of something the design chose to protect.

Marian as composition

Historically, Marian is better understood as a composition than as an isolated invention.

From Levitt, it takes clear precedent for the twelve-month 56–56–55 macrostructure, equal common-year quarters and shortened terminal civil weeks.

From the Darian lineage, it takes seriously the usefulness of a roughly 28-sol human-scale period.

From Levitt and Darian together, it inherits the recurrence trade-off: fixed month starts at the cost of uninterrupted weekday naming succession.

From the human-factors problem foregrounded strongly by Exodus, it takes seriously the value of recognition and learning burden in calendar design.

From Zubrin and Hargitai, the wider comparison makes clear that elapsed duration and orbital representation are different objectives.

From Šurán, the field already has strong precedent for treating week continuity and the scale of intercalation as deliberate design choices.

Marian's novelty claim should therefore remain modest.

It is not that nobody previously found twelve long Martian months. They did. It is not that nobody previously used roughly four-week Martian periods, shortened civil weeks, tropical anchoring or familiarity as a design criterion. They did.

The distinctive move lies primarily in the composition and assignment of functions.

Four elements of that composition are particularly characteristic.

First, Marian formally separates annual orientation from short cadence. Twelve months and twenty-four minths coexist rather than competing for the word month.

Second, it adds the Sixth as a standard medium-range interval between the month and the longer quarter.

Third, it treats the calendar explicitly as operating infrastructure. Its several civil scales are intended to provide shared coordinates for recurring institutions without prescribing how those institutions must operate.

Fourth, it builds in Earth–Mars legibility. The Ls = 15° year origin gives the two twelve-part civil years a useful relationship around the intended founding era, allowing their circular month gap to provide coarse intuition about Earth–Mars orbital phase and communications conditions.

Those features make Marian recognisably its own architecture.

None requires pretending that its components arrived without precedent.

Novelty is not a particularly useful requirement for infrastructure. Nobody asks a bridge to contain entirely original steel. They ask whether the pieces have been assembled coherently for the load the bridge is expected to carry.

There is no historical ladder

It would be easy to turn the history into a progression.

Levitt discovered the long Martian month. Darian improved it. Exodus made it familiar. Marian finally integrated everything properly.

That would be satisfyingly neat.

It would also be false.

These proposals are not software releases marching towards a final version. They protect different relationships.

A design built around familiar-duration primary months naturally moves towards Darian. A design that strongly protects inherited nomenclature may resemble Exodus. A calendar expected to encode more orbital information may look more like Zubrin. A system that treats uninterrupted weekly succession as fundamental should take Šurán and other continuous-week approaches particularly seriously.

Marian becomes coherent under a different cluster of priorities: twelve-part annual orientation, shorter recurring cadence, medium-range structure, fixed recurring dates, tightly bounded civil years, deterministic arithmetic and Earth–Mars legibility are all given significant weight.

That is not a neutral optimisation.

It is a particular design position.

Marian's place among them

So where does Marian sit?

Among the existing Martian calendar tradition, not above it.

Its lineage is visible. The twelve-month frame is strongly Levitt-like. The minth occupies territory associated with Darian's shorter Martian month. Its recurrence mechanism has precedent. Its concern with familiarity has precedent. Its separation of civil regularity from exact orbital representation becomes clearer precisely because Zubrin and Hargitai make different choices.

What Marian contributes is a particular way of putting those ideas together for a particular problem:

a permanent, technologically complex, still Earth-connected Martian civilisation that may benefit from several standard recurring civil horizons.

That is a coherent proposition.

It is not the mathematically inevitable calendar of Mars.

There is no such thing.

Mars supplies the physical constraints. The calendars differ because their designers assign different weights to the civil properties that must coexist within them.

A good calendar does not emerge because every alternative is foolish. It emerges because its trade-offs fit the problem it was designed to solve.