A - Marian Calendar Specification
Normative Definition of the Marian Civil Calendar
A.1 Purpose and status
This appendix defines the normative structure of the Marian Calendar, a civil calendar intended for permanent human settlement on Mars.
The specification defines the calendar's civil units, annual structure, weekday recurrence, intercalation rule, astronomical anchor, civil rollover and historical epoch. It is intended to be sufficiently precise for independent implementations to produce the same Marian dates from the same underlying chronology.
The explanatory chapters of this book describe the reasoning behind the design. Where explanatory prose and this specification differ in level of detail, this appendix defines the intended calendar structure.
One element cannot yet be numerically instantiated: the historical epoch depends upon the future first recognised human step on Mars. The rule defining that epoch is specified here; its eventual timestamp must be established after the event occurs.
For the purposes of this appendix:
- MUST identifies a requirement of a conforming Marian implementation.
- SHOULD identifies a recommended convention that may be varied for a legitimate local or technical reason.
- MAY identifies an optional convention.
A.2 Scope
Marian is a civil calendar, not a complete Martian timekeeping system.
It defines how Martian sols are organised into weekday positions, minths, months, Sixths, quarters and years. It also defines the recurring structure of common and leap years, the astronomical position to which the calendar is anchored, the canonical planetary date boundary and the origin of Marian year numbering.
Marian does not prescribe the subdivision of the sol into hours, minutes or seconds; local time zones; local mean solar time conventions; daylight adjustments; holidays; religious observances; working weeks; school terms; fiscal practices; or other cultural and institutional uses of civil time.
Those systems may use Marian dates without becoming part of the Marian Calendar specification.
A.3 Fundamental civil unit
The fundamental Marian civil unit is the sol, defined by the Martian mean solar day.
No physical sol is omitted, repeated or shortened by the Marian Calendar.
Civil calendar rules may alter the sequence of weekday labels, but they do not alter the continuous physical succession of Martian sols.
A.4 The Marian year
A regular Marian year contains either:
668 sols — common year
or:
669 sols — leap year
Every regular Marian year contains:
| Civil structure | Count per year |
|---|---|
| Years | 1 |
| Quarters | 4 |
| Sixths | 6 |
| Months | 12 |
| Minths | 24 |
| Nominal week positions | 96 |
| Sols | 668 or 669 |
The relationship may therefore be summarised as:
1 year = 4 quarters = 6 Sixths = 12 months = 24 minths = 96 nominal week positions = 668 or 669 sols
These are overlapping partitions of one annual civil frame. They MUST NOT be interpreted as a single chain in which every larger unit nests exclusively inside the next.
A.5 Months
Every regular Marian year contains 12 months.
The common-year month pattern is:
56 – 56 – 55 | 56 – 56 – 55 | 56 – 56 – 55 | 56 – 56 – 55
Accordingly:
- Months 1, 2, 4, 5, 7, 8, 10 and 11 contain 56 sols.
- Months 3, 6, 9 and 12 contain 55 sols in a common year.
- In a leap year, Month 12 contains 56 sols.
Months 1 through 11 are therefore identical in common and leap years.
Every regular month MUST begin at the first weekday position of the Marian week.
The twelve-month layer provides the calendar's principal twelve-part annual orientation. Human-readable month names MAY be adopted separately; canonical implementation MUST remain possible without them.
A.6 Minths
Every month contains exactly two minths, giving 24 minths per regular Marian year.
A 56-sol month divides as:
28 + 28 sols
A 55-sol month divides as:
28 + 27 sols
In a common year, Minths 06, 12, 18 and 24 therefore contain 27 sols. All other minths contain 28.
In a leap year, Minth 24 contains 28 sols because the leap sol occupies the final position of Month 12. Minths 06, 12 and 18 remain 27 sols.
Every minth MUST begin at the first weekday position.
The canonical minth identifiers are 01 through 24. The letters A through X MAY be used as compact human shorthand, mapped sequentially to Minths 01 through 24.
Natural-language minth names MAY be used by communities or institutions, but such names MUST NOT replace the canonical identity of the underlying minth in machine-readable interchange.
A.7 The Marian week
The Marian civil week contains seven nominal weekday positions.
The recommended human-readable weekday sequence runs from Monsol through Sunsol. Implementations MUST preserve the ordering of the seven positions even if localised names are used.
The normal civil week contains all seven weekday positions. In designated terminal weeks, however, the seventh position is absent.
This occurs because a 27-sol minth consists of:
7 + 7 + 7 + 6 sols
rather than four complete seven-sol weeks.
Accordingly, in a common year the terminal civil weeks of Months 3, 6, 9 and 12 contain six occupied weekday positions. In a leap year, the terminal civil weeks of Months 3, 6 and 9 contain six; Month 12 contains a complete seven-position terminal week.
After a six-position terminal week, the following month begins again at the first weekday position.
This is a discontinuity in the weekday naming sequence, not in physical time. No sol is skipped.
The effect is that every regular Marian month and minth begins on the same weekday position, and corresponding dates retain recurring weekday relationships from year to year.
A.8 Quarters
The Marian year contains four quarters, each comprising three consecutive months:
| Quarter | Months |
|---|---|
| Q1 | 1–3 |
| Q2 | 4–6 |
| Q3 | 7–9 |
| Q4 | 10–12 |
In a common year, each quarter contains:
167 sols
because:
56 + 56 + 55 = 167
In a leap year, Q1, Q2 and Q3 remain 167 sols while Q4 contains 168.
The canonical identifiers are Q1 through Q4. The corresponding human-readable names are:
| Identifier | Name |
|---|---|
| Q1 | Primiv |
| Q2 | Secondiv |
| Q3 | Tertiv |
| Q4 | Quartiv |
The quarter represents a four-part division of the Marian annual cycle. It is not required to reproduce the elapsed duration or institutional use of a terrestrial thirteen-week quarter.
A.9 Sixths
The Marian year also contains six Sixths, each comprising two consecutive months:
| Sixth | Months |
|---|---|
| S1 | 1–2 |
| S2 | 3–4 |
| S3 | 5–6 |
| S4 | 7–8 |
| S5 | 9–10 |
| S6 | 11–12 |
Their common-year lengths are:
112 – 111 – 111 – 112 – 111 – 111 sols
In a leap year, S6 contains 112 sols.
The canonical identifiers are S1 through S6. The corresponding human-readable names are:
| Identifier | Name |
|---|---|
| S1 | Primus |
| S2 | Secundus |
| S3 | Tertius |
| S4 | Quartus |
| S5 | Quintus |
| S6 | Sextus |
Sixths and quarters deliberately overlap. A Sixth is not a subdivision of a quarter, nor is a quarter a grouping of Sixths.
They are separate civil grids applied to the same twelve-month year.
A.10 Functional structure
The principal civil roles of Marian's middle-scale units are:
| Unit | Principal civil function |
|---|---|
| Minth | Short operating cadence |
| Month | Twelve-part annual orientation |
| Sixth | Medium-range cadence |
| Quarter | Four-part annual orientation |
This distinction reflects the governing design principle of Functional Separation: civil functions that happen to share one unit on Earth need not remain bundled when the Martian annual cycle separates them.
The existence of a standard civil interval does not require individuals or institutions to use it for any particular activity.
A.11 Leap-year rule
Leap status is determined entirely from the Marian year number.
For regular Marian years MY1 onward:
- Odd-numbered years are leap years.
- Years divisible by 10 are also leap years.
- Years divisible by 100 are common years.
- The century rule takes precedence over the preceding rules.
Equivalent decision logic is:
If year mod 100 = 0 → common
Else if year mod 2 = 1 → leap
Else if year mod 10 = 0 → leap
Else → common
This rule produces exactly 59 leap years per 100 regular Marian years.
The mean civil-year length is therefore:
668 + 59/100 = 668.590000 sols
Leap frequency and leap placement are separate design properties. The 59/100 ratio determines the long-run frequency required to track the selected astronomical cycle; the odd / decennial / century rule determines the civil placement of those leap years.
A.12 Leap-sol position
The leap sol occupies exactly one possible civil position:
Month 12 · Week 8 · Day 7
In a common year, that position does not exist.
In a leap year, it exists as the final weekday position of the final civil week of Month 12.
The leap sol therefore:
- changes Month 12 from 55 to 56 sols;
- changes Minth 24 from 27 to 28 sols;
- changes Sixth 6 from 111 to 112 sols;
- changes Quarter 4 from 167 to 168 sols; and
- changes the year from 668 to 669 sols.
No earlier civil date changes between common and leap-year templates.
A.13 Astronomical anchor
The Marian annual astronomical anchor is:
Ls = 15°
where Ls is areocentric solar longitude.
This reference defines where the regular Marian civil year belongs within the Martian seasonal cycle.
Ls = 15° is an astronomical target, not a requirement to begin every subsequent civil year by observing or recalculating the instantaneous astronomical crossing.
Once the Marian epoch has been instantiated, the civil calendar MUST advance deterministically through its prescribed 668- and 669-sol years. Intercalation keeps that civil sequence tracking the astronomical reference over time.
Exact seasonal position remains an astronomical quantity and SHOULD be expressed using Ls or another appropriate scientific coordinate rather than inferred from the Marian civil date when precision is required.
A.14 Canonical civil rollover
The canonical planetary civil date boundary is:
midnight at Airy-0
The astronomical passage through Ls = 15° and the canonical civil rollover are deliberately separate.
For the establishment of MY1, Mars first passes through Ls = 15°. The first Airy-0 midnight following that passage begins the first complete regular Marian year.
Marian does not prescribe how settlements elsewhere on Mars must display local time. Local mean solar time, future time-zone systems or shared administrative clocks MAY coexist with Marian dates, provided they can be related unambiguously to the canonical planetary chronology.
A.15 Historical epoch
Marian year numbering begins with direct human history on Mars.
The recognised first human step onto the Martian surface establishes the historical epoch and begins Marian Year 0 (MY0).
MY0 is a transitional epoch interval. It is not required to contain 668 or 669 sols and is not a normal regular Marian year.
The sequence is:
recognised first human step → MY0 begins
next passage through Ls = 15°
first Airy-0 midnight after that passage → MY1 begins
From MY1 onward, all years follow the regular Marian structure and leap-year rule.
The precise timestamp and authoritative definition of the recognised first human step cannot be instantiated before the event occurs. A future standards authority MUST record that event sufficiently precisely to establish the epoch reproducibly.
A.16 Year numbering
Regular Marian years are numbered sequentially:
MY1, MY2, MY3, ...
MY0 precedes MY1 and is reserved for the transitional interval beginning with the recognised first human step.
The Marian Calendar does not require the projection of ordinary Marian year numbers into pre-human Martian history.
Any extension before MY0 would require an explicitly defined separate convention and MUST NOT be confused with the primary Marian civil chronology.
A.17 Canonical identities and localisation
A conforming implementation MUST preserve stable numeric identities for the structural elements of the calendar regardless of the human-readable language used to display them.
At minimum, the following canonical identities exist:
- Marian year number: MYn
- Month: 01–12
- Minth: 01–24
- Quarter: Q1–Q4
- Sixth: S1–S6
- Weekday position: 1–7
Compact or natural-language forms MAY be layered above those identities.
Localisation MUST NOT change the underlying structural mapping. For example, a locally named minth remains canonically the same numbered minth, and a translated weekday remains the same weekday position.
The exact canonical date syntax, ordinal-sol representation, machine interchange formats and conversion rules are defined in Appendix D.
A.18 Validity requirements
A Marian date is valid only if every component exists in the specified year template.
In particular:
- common years contain 668 sols;
- leap years contain 669 sols;
- Months 3, 6 and 9 always contain 55 sols;
- Month 12 contains 55 sols in a common year and 56 in a leap year;
- no date may occupy the seventh weekday position of a six-position terminal civil week;
- Minths 06, 12 and 18 contain 27 sols in all regular years;
- Minth 24 contains 27 sols in a common year and 28 in a leap year;
- the leap-sol position exists only in a leap year.
A conforming implementation MUST reject structurally impossible dates rather than silently reinterpret them.
Detailed date-validity tables are provided in Appendix B.
A.19 Determinism
For MY1 onward, the complete shape of any Marian year MUST be calculable from the year number alone.
An implementation MUST NOT require an astronomical observation, ephemeris lookup or discretionary authority decision to determine whether an ordinary Marian year is common or leap.
Astronomy defines the physical cycle the calendar is intended to track. The civil algorithm determines the calendar.
This separation is fundamental to reproducible implementation.
A.20 Long-term alignment
The ordinary Marian intercalation regime has a mean year length of 668.590000 sols and is intended to track the Ls = 15° recurrence closely around the founding era.
It is not claimed to constitute an exact astronomical rule for geological timescales.
If future astronomical modelling or accumulated phase behaviour eventually justifies a rare long-period correction, such a correction SHOULD be handled as a higher-order maintenance rule rather than by altering the ordinary definitions of the sol, week, minth, month, Sixth, quarter or 668/669-sol annual templates.
Any such future modification would constitute a revision or extension of this specification and MUST be explicitly versioned.
A.21 Matters deliberately outside the specification
The Marian Calendar does not define:
- sub-sol horology;
- Martian time zones;
- daylight-saving or seasonal clock changes;
- working or rest days;
- religious observance;
- public holidays;
- birthday conventions;
- age-of-majority rules;
- school or university terms;
- fiscal years;
- payroll schedules;
- organisational planning cadence;
- exact astronomical position implied by a civil date;
- cultural names for months or minths beyond any separately adopted nomenclature; or
- political authority over future Martian civil time.
Such conventions MAY use Marian units but remain separate from the calendar's normative civil structure.
A.22 Minimum conforming Marian implementation
A system may be described as implementing the Marian Calendar if it can, at minimum:
- represent regular Marian years as either 668 or 669 sols;
- apply the 56–56–55 × 4 common-year month structure;
- place the leap sol only at the final position of Month 12;
- represent 24 minths, 12 months, six Sixths and four quarters with the mappings defined above;
- implement the seven-position weekday system, including six-position terminal civil weeks where required;
- preserve continuous physical sol counting while allowing the weekday naming sequence to omit the seventh position in those terminal weeks;
- determine leap status using the odd / divisible-by-10 / divisible-by-100 rule;
- preserve Ls = 15° as the annual astronomical anchor;
- recognise Airy-0 midnight as the canonical planetary civil rollover;
- recognise the first human step as the origin of MY0 and the prescribed subsequent boundary as the beginning of MY1;
- preserve canonical numeric identities independently of localised human names; and
- reject dates that do not exist in the applicable common- or leap-year template.
Everything beyond those requirements is implementation, interface or culture.