ADMIT
22) What Marian Gives Up
Trade-offs, Uncertainties and Boundaries
A serious design should be able to describe its disadvantages without immediately trying to win them back.
Marian has disadvantages.
Some are direct consequences of deliberate choices. Others are uncertainties that cannot be resolved until people actually use the system. A third category consists of problems Marian does not attempt to solve at all.
Keeping those categories separate matters. A trade-off is a property surrendered in order to gain another. An uncertainty is something we do not yet know about the design. An out-of-scope problem belongs to another system.
Marian should not disguise a genuine cost by calling it somebody else's problem. Equally, it should not be criticised for failing to be a clock, an ephemeris, a constitution and a complete Martian culture.
The limits belong in the design.
The trade-offs Marian accepts
The first cost is the month.
A Marian month contains 55 or 56 sols, roughly twice the duration people currently associate with an Earth month. That is the price of retaining twelve primary annual divisions.
The minth restores a roughly four-week scale, but introduces another cost: more terminology. Marian asks users to understand months and minths as different units, and potentially Sixths as well.
That is what functional separation costs.
If those scales prove independently useful, the vocabulary earns its place. If they do not, the architecture will feel over-designed.
The Sixth is the most exposed case. Its 111- or 112-sol interval provides a clean medium-range scale between the Marian month and quarter, but its practical value remains unproved. Future institutions may use it heavily or almost completely ignore it.
Either outcome would be legitimate evidence.
A design should be allowed to discover that one of its rooms is rarely entered.
The weekly cost
The strongest structural compromise remains the weekday sequence.
Marian preserves fixed recurring date–weekday relationships by allowing selected terminal civil weeks to contain six weekday positions rather than seven. The physical sequence of sols continues normally, but the civil weekday naming sequence is interrupted at those boundaries.
The previous chapter examined the alternative architectures in detail. The important point here is simpler: this is a genuine social cost.
Some communities may care deeply about uninterrupted weekly succession. Religious observance may depend on it. Work-rest traditions may become organised around it. People may simply dislike a civil calendar in which Satsol can be followed by Monsol.
Marian has chosen fixed recurrence over uninterrupted civil weekday naming.
That choice may prove acceptable. It may prove to be the calendar's most important human-interface weakness.
The calendar itself cannot decide what shortened terminal weeks should mean for employment, rest or religious practice. Those consequences belong to the communities using it.
Regular civil months, weaker seasonal meaning
Marian also gives up stronger correspondence between its months and Mars's orbital progression.
Its months are designed to contain almost equal amounts of elapsed civil time. Mars does not move through equal amounts of orbital angle during equal durations because its orbital speed changes. Similar civil month lengths therefore do not imply equal changes in Ls.
A calendar could make its periods correspond more closely to equal seasonal angles by allowing their elapsed durations to vary more substantially.
Marian does not.
Its division of labour is deliberate:
Marian Civil Date provides regular civil position.
Ls and ephemerides provide precise seasonal position.
That works cleanly, but the cost remains real. A Marian month carries less exact astronomical information than a more seasonally oriented civil period would.
Earth alignment is allowed to age
The Ls = 15° year origin makes another exchange.
Around the intended founding era, it gives Marian New Year a useful relationship with the heliocentric direction associated with Gregorian New Year. That supports the Earth–Mars month-gap intuition developed earlier.
The relationship will not remain equally neat forever.
Marian could attempt to move its year boundary over the centuries in order to preserve the Earth-facing alignment more closely. It deliberately does not. Ls = 15° remains a Martian tropical reference, and the Earth-facing geometry is allowed to evolve around it.
The year stays attached to Mars.
The convenience is allowed to age.
The leap rule is memorable rather than phase-optimal
The 59/100 intercalation rule also makes a conscious trade.
Its ordinary form is easy to remember:
odd years leap; decennial years leap; century years are common.
That gives Marian the required long-run proportion of leap years and an excellent founding-era mean civil year.
The same 59 leap sols could be distributed more evenly to keep intermediate civil boundaries closer to the smooth astronomical target. Marian does not use that more phase-balanced pattern.
It gives up some phase optimality for mnemonic transparency.
That trade is now explicit. The long-run mean is preserved; the short verbal rule is preserved; some intermediate astronomical neatness is not.
The rule also cannot claim mathematical perfection for every future century. Mars's tropical recurrence changes slowly over long timescales, so a future standards authority may eventually need to decide whether a rare correction is warranted.
The ordinary calendar is deterministic.
Its very-long-range maintenance policy is deliberately unfinished.
The main uncertainties are human
The arithmetic has been examined considerably more thoroughly than the users.
That remains Marian's largest unresolved issue.
The design can prove that minths contain 27 or 28 sols. It cannot prove that people will find the concept natural. It can demonstrate recurring-date invariance. It cannot demonstrate that users will value that property enough to tolerate the interrupted weekday sequence.
It can define Sixths precisely. It cannot show that anyone will use them.
It can demonstrate the Earth–Mars month-gap relationship. It cannot establish that ordinary users will find the heuristic intuitive or remember it.
It can propose Monsol, Janiix and A–X. It cannot prove that those interfaces reduce errors or make the calendar easier to learn.
These are not mathematical weaknesses. They are missing human evidence.
That matters because Marian's practical claim is larger than “the arithmetic works”. The architecture is intended to be usable civil infrastructure. Eventually, the interface has to encounter people.
The experiments need not be exotic. Users could be taught competing calendar structures and asked to navigate dates, schedule recurring events and recover annual position. Continuous-week and fixed-recurrence systems could be compared for errors and learning time. The month/minth distinction could be tested against a twenty-four-month alternative. Sixths could be tested to see whether they improve medium-range orientation enough to justify another formal unit. Familiar, modified and entirely novel naming schemes could be compared directly.
In other words, subject the calendar to the indignity of actual users.
This is usually good for design.
Some apparently elegant choices may not survive the experience.
That possibility should remain open.
What Marian deliberately does not solve
A different category of limitation needs no experiment. The correct answer is simply:
another system handles it.
Marian is a civil calendar. Its scope should stop before the word time becomes an excuse to annex everything nearby.
Clocks and time zones
Marian does not prescribe how a sol must be divided into hours, minutes or seconds.
Its canonical date boundary uses Airy-0 as a reference, but this does not require every settlement to live permanently on an Airy-0 clock. A future Mars might use familiar 24-hour notation, another horological scheme, local solar time, regional zones or a shared administrative clock.
Those systems need defined relationships to the canonical civil date.
They do not need to become part of the calendar itself.
Calendar and clock must interoperate. They do not have to be the same standard.
Earth has managed something broadly similar, occasionally with enthusiasm bordering on administrative performance art.
Navigation and precise astronomy
Marian also does not tell a spacecraft where Mars is.
A civil date is not an ephemeris. Precise seasonal position belongs to Ls. Navigation, orbital mechanics and trajectory planning require proper astronomical systems. Earth–Mars light time should come from the actual geometry, not from a civil heuristic.
Anyone planning orbital insertion using “probably Month 4” has misunderstood the division of labour rather comprehensively.
The calendar can make astronomy more legible.
It does not replace astronomy.
Mission chronology
Nor does Marian make mission-relative sol counts obsolete.
A rover team may still care that an experiment occurs on Mission Sol 214. A crewed expedition may maintain an elapsed mission clock. Scientific systems may use Mars Sol Date or another continuous coordinate.
Those systems remain useful because they answer different questions.
Mission chronology describes a bounded operation. Scientific coordinates describe continuous physical time. Marian describes recurring civil time.
A mature Martian civilisation would probably use several simultaneously.
Success does not mean forcing Marian into every temporal problem. It means nobody has to use Marian for work it was not designed to do.
Politics, law and culture
Marian also cannot grant itself legitimacy.
A mathematically coherent calendar may remain socially irrelevant forever. Adoption would depend on institutions and communities deciding to use it, alongside existing practice, migration costs, law and politics.
Publishing a specification does not create a civilisation-wide standard.
Technical coherence is not adoption.
Nor does Marian decide what future Martians should make culturally significant. It does not prescribe holidays, religion, adulthood, birthday practice or which historical events deserve annual remembrance. It cannot know whether Janiix survives as ordinary speech, whether some minths become culturally important or whether whole parts of the proposed vocabulary disappear.
That is not missing specification.
It is proper scope control.
The structural layer can be defined now because interoperability benefits from stability.
Meaning cannot.
Three kinds of limitation
Marian's limits can therefore be summarised cleanly.
Deliberate trade-offs
It gives up:
- short primary months to preserve twelve-part annual orientation;
- vocabulary economy to separate civil functions;
- continuous weekday naming to preserve recurring date–weekday structure;
- strong month-to-season correspondence to preserve elapsed-time regularity;
- permanent Earth-facing alignment to keep the year attached to a fixed Martian tropical reference;
- some short-period phase optimality to keep intercalation memorable.
These are costs attached directly to design choices.
Genuine uncertainties
We do not yet know:
- whether minths feel natural;
- whether Sixths earn their place;
- whether shortened terminal civil weeks prove socially tolerable;
- whether the proposed nomenclature helps;
- whether fixed recurrence provides enough practical benefit to justify the weekly cost;
- whether the layered architecture is genuinely easier to live with than simpler alternatives.
These questions need evidence.
Deliberate exclusions
Marian does not define:
- hours, minutes or seconds;
- local time zones;
- navigation;
- precise astronomy;
- mission chronology;
- labour policy;
- religious practice;
- public holidays;
- political legitimacy;
- future Martian culture.
These questions need other systems.
The distinctions matter. Trade-offs should be defended or reconsidered. Uncertainties should be tested. Exclusions should remain outside the calendar.
A smaller claim is stronger
There is always a temptation near the end of a design project to expand its territory.
If the calendar defines dates, perhaps it should define hours. If it has an astronomical anchor, perhaps it should solve navigation. If it creates a civil year, perhaps it should prescribe festivals. If the arithmetic is coherent, perhaps the same document should decide how Mars adopts it.
Resist that temptation.
Marian is a proposed civil calendar architecture for Mars. It organises physical sols into recurring civil structures, provides deterministic dates and remains traceable to Martian astronomy. It supplies several standard timescales without prescribing how institutions must use them, and it gives the technical structure a stable identity without trying to freeze future culture around it.
That is already a substantial job.
The costs are real. The uncertainties are real. The boundaries are real.
A design that admits all three is more credible than one that turns every limitation into another feature.