A2. Retrospective Logic of Design
The Marian calendar is best understood not as an invention but as a convergence in the first hundred years of settlement (late 21st century AD): a minimal set of civil choices layered atop scientific timekeeping, each selected because crews, families, and institutions found them predictable, interoperable, and, above all, livable.
The step-by-step logic ultimately was:
Prime meridian at Airy-0 gave a universal spatial “zero” for timekeeping; nothing else could proceed without it.
Long-second 24:60:60 preserved human intuition and reduced cognitive and technical switching costs; dual-track (SI + civil) timing bridged science and society.
New Year at Ls = 280° balanced astronomical stability with an operationally convenient seam and avoided over-identifying New Year with one hemisphere’s spring, and semi-synchronized with Earth, while remaining entirely independent.
Human Era epoch (Year 0 = first landing) anchored civil memory; science retained MY/Ls/MSD, with formal conversion between systems. The HE=Year and ME-Mear (Martain Year), ensuring local year counting syncing. Note – this codex is the Terran edition and so presents year dating anchors to HE so to align with the “annual” intuition of Earth based readers.
12-month civil architecture (mostly 56-sol months; selective 55-sol months; extra sol in Month 12) produced a legible year; seven-sol week with a Sunsol omission rule made every month begin on Monsol without breaking communities that needed a continuous seven, or making the system too complicated.
Names were light-touch and learnable (-iix months, Monsol…Sunsol), with localization permitted so long as the backbone remained intact.
Minths (A–X) and Sixths (I–VI) exposed the planning granularity operators used, while almanacs kept the Ls layer visible for season and science. The alphanumeric numbering of these allowed different groups to pick specific names, that where still intuitive due to the initial letter coding.
Drift controls (6/decade leaps + century/millennial tunings) held the calendar close to the vernal-equinox year for millennia without monthly surprises.
It approached each of these steps with a Muskian design philosophy. Firstly, prior to the mid-21st century most Martian calendar designers were using a “very dumb set of requirements” to begin with. Next they all added complexity and features to the existing baseline of humanity’s Gregorian calendar, rather than try to delete parts of it and simplify further fixing obvious legacy oddities (e.g. odd length months, leap days in strange places, etc).
Finally they spent time seeking to optimize what was left. The Marian calendar went back to first principles and started against a different set of requirements, from there deleted and optimized parts of the existing “calendar wheel” against the new constraints, and that included things like the approach to naming months and sols so that every month-date had a consistent week-sol across years.
Diving deeper into each of these:
1) Fixing where “zero” is: the prime meridian
The precondition for any shared time (and therefore any calendar) is a shared “where” on the planet. Mars’s prime meridian was established in the 19th century and later refined to the crater Airy-0, which became the origin for longitude and for mean solar time at the meridian. With Airy-0 accepted across the scientific community, subsequent civil standards could inherit a single reference without reopening cartographic debates.
Why this matters for a calendar.
A civil day boundary (midnight at a reference meridian) and a planet-wide reference time (the Mars analogue of UT/UTC) both lean on a fixed prime meridian.
Operational clocks for navigation, communications passes, and power scheduling need a global reference even if local settlements shift working hours for convenience.
Alternatives considered (not adopted).
Floating or multi-prime standards (e.g., per-hemisphere “zeros”): rejected as unhelpful for inter-settlement coordination.
Ephemeris-only time (counting sols from an epoch with no fixed meridian): sufficient for science, but not for everyday civil use.
2) Agreeing on the “long-second” 24:60:60 day
By the Viking era, practice converged on a 24 hours × 60 minutes × 60 seconds division of the Martian solar day (sol), with each unit stretched by ~2.75% relative to Earth. This kept clocks familiar while matching the sol’s true length (≈ 24 h 39 m 35 s of Earth time). The decision — made by use before statute — proved extraordinarily sticky: it allowed humans to carry their intuition for hours and weeks onto a new world with minimal cognitive friction.
Merits.
Human-factor continuity: “eight hours of sleep,” “a one-hour meeting,” “a 30-minute EVA prep” continue to mean what they feel like, not just numbers on a display.
Technical interop: Software, displays, and procedures can be ported with proportional scaling rather than rewritten for decimal or non-sexagesimal schemes.
Alternatives considered (not adopted).
SI-second sol (keep seconds fixed, redefine hours/minutes non-sexagesimally): technically pure, ergonomically brittle.
Decimal time (10×100×100): attractive on paper, historically fragile on Earth; offered no decisive benefit on Mars.
Dual clocks (Earth seconds for instruments, civil “long seconds” for people): adopted informally anyway, but the civil clock had to be singular, and that was the stretched 24:60:60.
Mitigation for edge cases. Scientific logs and instruments often recorded in SI seconds plus Mars Sol Date (MSD); civil records tracked long-second clock time. Conversion libraries bridged the two.
3) Selecting Ls = 280° as New Year
New Year needed a planet-shared anchor in Mars’s orbit: the solar longitude (Ls) at which Year Day is defined. Many proposals favored Ls = 0° (northern vernal equinox) by analogy with terrestrial traditions; others chose Ls = 270° (northern winter solstice), Ls ≈ 251° (perihelion), or Ls = 90°/180° (solstice/equinox symmetry).
The Marian calendar fixed Year Day at Ls = 280° — ten degrees after the northern winter solstice, early in northern late-winter/southern late-summer.
Reasons for the Ls = 280° choice.
Operational seam: The window just after the northern winter solstice sits between major seasonal peaks in atmospheric variability; for many mid-latitude sites this made a practical “book-closing” moment after dust-season complexities.
Clear separation from perihelion: Perihelion (≈ Ls 251°) is operationally busy; beginning the year slightly after avoids binding New Year to the most thermally and meteorologically distinctive period.
Cultural synchronization without imitation: Earth’s January 1 is not an equinox or solstice either; Ls = 280° provided a stable post-solstice marker that felt analogous, aligned without copying and still providing an Earth independent baseline. Synchronization enables cultural alignment both-ways across planets.
Stability across epochs: The vernal-equinox year and the winter-solstice year are both relatively stable on Mars; placing New Year close to, but not exactly at, the solstice balanced astronomical neatness with operational convenience.
Leading alternatives (and why they were not chosen).
Ls = 0° (northern vernal equinox): Popular, simple, and common in science; ultimately set aside to avoid over-identifying New Year with one hemisphere’s spring and to gain the operational seam noted above.
Ls = 270° (northern winter solstice): Clean symmetry, but too tightly coupled to dust-season crest and perihelion-adjacent operations.
Ls ≈ 251° (perihelion): Physical elegance, poor human factors; seasons on Mars are driven by both obliquity and eccentricity, but people live by light/weather cues more than by orbital anomaly.
Ls = 90°/180° (other solstice/equinox): No compelling human or operational advantage over 280°, and they re-centered year start on strong hemispheric metaphors.
Mitigations of issues with this solution. Scientific almanacs continued to index seasons by Ls, and agencies published conversion tables so that “Marian New Year” and “Ls=0° (vernal equinox)” remained easy to compare.
4) Choosing the epoch (what counts as Year 0/1)
Picking the epoch is a social decision more than a physical one. Options canvassed included: the Viking 1 landing (1976), the Kepler/Galileo 1609 scholarly epoch, the MSD/MTC epoch (1873-12-29), MY 1 (1955-04-11), and the first human landing.
The Marian calendar adopted a Human Era (HE): Year 0 HE = first human landing on Mars, with BHE (“Before Human Era”) for prior years. Scientific practice retained Mars Year (MY) for research chronology, and the appendix standards include a deterministic HE↔MY↔JD mapping.
Reasons for the Human Era epoch.
Civil relevance: A civil calendar marks civic history; the first landing is the obvious hinge for public memory.
Conversion discipline: Settlements relied on software layers to translate HE dates to MY and Julian systems; once established, this added no daily friction.
Negative-date avoidance: With Year 0 at the landing, most living memory runs in positive HE years; deeper history uses BHE, which is culturally legible.
Leading alternatives (and why they were not chosen).
Viking 1 landing (1976): Powerful scientific milestone but not a lived civil hinge for settlers.
MSD epoch (1873-12-29): Excellent for computation; opaque to citizens.
MY 1 (1955-04-11): Ubiquitous in research; too specialized as a civil epoch.
1609 scholarly epoch: Elegant symbolism, too remote; yields large positive year numbers with little intuitive meaning.
Mitigations. The code-level truth remained plural: HE for civil life, MY/Ls/MSD for science and operations, with robust round-trip conversion. Calendars in schools taught both.
Note the famous first human landing date was NOT the first sol of Year 0. It just anchored the year numbering. The first sol of Year 0 happened *before* the landing date at Ls = 280°.
5) Dividing the year: months, weeks, and leap years
With New Year and epoch in hand, the remaining question was how to structure the ≈ 668.5907-sol tropical year for human planning, building and operations.
The Marian solution.
Months: 12 months grouped into four seasons of three months each. Most months are 56 sols; months 3, 6, 9 have 55 sols; month 12 has 55 sols in common years and 56 sols in leap years.
Weeks: A seven-sol week (Monsol, Tuesol, Wednesol, Thursol, Frisol, Satsol, Sunsol), synchronized globally.
Week–month alignment rule: Every month begins on Monsol. To achieve this, Sunsol is omitted once at the end of months 3, 6, 9, and also at the end of month 12 in common years. (The omission is a civil convention; religious or labor-law accounting may still count continuous sevens.)
Leap-year cycle: Six leap years per decade: every odd-numbered year, plus years divisible by 10. The extra sol is always added to month 12. This yields a mean of 668.6 sols, close to the vernal-equinox year.
Long-cycle stability: Century and great-cycle tunings (e.g., 59 leaps per 100 years, with rare millennial adjustments) keep cumulative drift within a sub-sol over many millennia tolerance—implemented as institutional almanac rules, invisible to daily life.
Why this pattern.
Human legibility: Twelve is familiar; quarters and seasons stay comprehensible; most months present the same internal cadence (8 weeks in a 56-sol month).
Operational regularity: Fixed month starts (always Monsol) simplify rosters, invoicing, and statutory deadlines.
Intercalation simplicity: “Extra sol in Month 12” isolates complexity to year-end; upstream dates don’t move.
Leading alternatives (and why they were not chosen).
24-month schemes (e.g., Darian; 20×28 + 4×27 with orderly leap sols): elegant symmetry, but doubled month count complicated civil administration and muddied quartering for finance and law.
24×28 with “leap week” deletions (e.g., Šurán): beautifully uniform months; leap-week omissions at year-end proved culturally and legally awkward for payroll, benefits, and audit trails.
18-month schemes (e.g., Moore): plausible compromise, but offered no compelling advantage over 12 for public literacy and cross-cultural adoption.
Floating weeks (e.g., Gregorian-style): familiar to Earth, but forfeited the “every month begins on Monsol” clarity that settlers prized for planning.
Mitigations for week-sensitive communities. Where a continuous seven-sol observance mattered, communities kept an unbroken count parallel to the civil omission rule; civil service portals could display both.
6) Naming the parts (without overfitting culture)
Names were layered, not imposed. The calendar kept Earth-familiar cues while signaling a new world:
Months: Janiix, Febiix, Mariix, Apriix, Mayiix, Juniix, Juliix, Augiix, Sepiix, Octiix, Noviix, Deciix. The “-iix” suffix mnemonically marks the prevalent 8-week cadence of the 56-sol month.
Weekdays: Monsol … Sunsol, using the English stems with a planetary “sol” ending (local language equivalents coexisted).
Seasonal layer (optional): Almanacs reference Ls markers (solstices/equinoxes, perihelion/aphelion) and recognize a Mandarin alias set for the 24 sub-monthly markers (see minths below), by analogy with Earth’s jiéqì without importing its climate claims.
Naming alternatives (and why they were not frozen).
Entirely novel lexicons: charming but polarizing and complex; the standard adopted a minimal layer and left room for local custom.
Full classical/Latinization: internally consistent, externally opaque; the chosen mix favored memorability and ease of learning.
Phobos/Deimos month names: astronomical poetry, but misleading about their role (the moons do not define Martian months).
Mitigations. The standard is descriptive, not prescriptive: month lengths, week rules, and intercalation are fixed; labels can be localized so long as the structural backbone remains intact.
Note: As the naming here was not “owned” or “authored” by anyone in particular, the proposal was ultimately more acceptable to everyone. This point is often understated in historic reviews.
7) Sub-monthly scaffolding (minths and sixths)
Experience showed that teams planned in 2- to 8-week horizons (~10 to ~100 sleep cycles). The calendar therefore exposes two sub-monthly units that settled naturally into use:
Sixths: Six two-month blocks (I–VI), each containing ~112 sols (four minths). “Sixths” matched how operations, budgets, and educational terms often ran in practice — longer than a month, shorter than a season.
Minths: “Mini-Months”, 24 half-months per year. In a 56-sol month, minths are 28 sols each; in a 55-sol month, the first minth is 28 and the second is 27 (preserving stable month starts). Each minth has a canonical A–X index (Aurex … Xenax) and an optional Mandarin alias aligned to the spirit/order of the 24 jiéqì.
Why these, not others.
Cadence fit: They matched how people naturally grouped work, review cadences, and maintenance cycles.
Data aggregation: Public metrics (safety, energy, finance) reported cleanly by minth and sixth without bespoke custom periods.
Time standards and zones
Reference time: ATC (Airy Coordinated Time) at Airy-0 serves as the planetary backbone; local zones in ~15° longitude bands give settlements clock-time convenience.
Conversion stack: HE (civil) ↔ MY/Ls/MSD (science/ops) conversions are standard library functions; civil tools display both by default when context warrants.
Stability and drift tolerance
Mean alignment: 6-per-decade leaps keep the average year at 668.6 sols; century and great-cycle tunings bound residual drift.
Visibility: Adjustments are almanac-level (like Earth’s leap-second notices), not month-level surprises; the extra sol always lands in Month 12.
Records, law, and education
Records: Statutes define deadlines and fiscal boundaries by month/minth, not by Ls, while government almanacs maintain the Ls correlation table.
Education: Early curricula teach dual literacy (civil HE dates and scientific Ls/MY) so citizens can read both civic and scientific timelines with ease.