MOVE
21) What Changes When You Move?
Moving Between Worlds

The real test of a common calendar architecture begins when somebody leaves home.

A person who spends their entire life on Mars can learn almost any competent Martian calendar and use it perfectly well. The harder question is what happens when that same person later moves to Ceres, takes a job in the Saturnian system and eventually lives in an artificial settlement whose physical environment bears little resemblance to any natural planet.

That kind of life will not necessarily become ordinary in the way international travel is ordinary today. Distances remain enormous, journeys may be expensive and communications cannot outrun light.

But some people will move.

Far more will work for organisations whose colleagues, customers, suppliers, assets or institutions span several astronomical environments. A useful multi-world calendar should make those relationships easier without pretending the destinations are physically the same.

Solarian's proposition is that:

Portability comes from shared structure, not shared duration.

Imagine one person making several moves through the Solar System.

Growing up on Mars

Our traveller is born on Mars.

Nothing about their childhood feels like a calendar experiment. Mars has long since become home to a permanent population, and its calendar is simply part of ordinary life in much the same way that most people on Earth rarely think about the design decisions buried inside Gregorian.

The local civil day is the Martian sol, around forty minutes longer than an Earth day. Seven sols make the week, giving schools, workplaces and households a recurring rhythm close to humanity's inherited one while remaining tied to the natural Martian day.

Above that sits the human operating cadence. Minths provide the few-week planning scale; twelve form a mear. Mars is R2, so two mears fit inside one Martian orbital year and two minths inside each orbital month.

For someone who grows up with the distinction, there is nothing particularly difficult about it. A minth describes ordinary human recurrence. A Martian month describes Mars's progress around the Sun.

The two are connected without being confused.

School terms might be expressed in minths. Maintenance may recur every half-mear. Festivals may attach themselves to particular Martian months, seasons or moments in settlement history.

Over time, the human-facing calendar will become culturally Martian. Future inhabitants may create names, holidays, commemorations and traditions that nobody today could sensibly design on their behalf. Solarian does not need to know what those will be.

Underneath them remains a structure that software, institutions and travellers can recognise.

That matters when our Martian eventually leaves.

Moving to Ceres

Ceres feels different immediately.

Its rapid natural rotation is not a useful basis for a common human civil day, so the settlement uses the standard 86,400-second day instead of a local rotational cycle. Its astronomical scale is different too.

Ceres takes roughly 4.6 Earth years to orbit the Sun and uses R5: five mears per local orbital year and five minths per orbital month.

For the new arrival, several visible things therefore change. The Martian sol disappears. The local year becomes much longer. The astronomical months have different durations and different local names. New Year follows Cererian rather than Martian astronomy. The intercalation schedule changes.

Yet surprisingly little changes at the human level.

A week is still a week. A normal minth is still four weeks. A mear is still twelve minths. An orbital month still means one of twelve broad positions within the local heliocentric year.

Our traveller therefore has to learn where they are, not relearn what time means.

That distinction is the practical value of a protocol. Moving between Solarian worlds should feel less like changing mathematical systems and more like learning the local implementation of a familiar grammar.

The details change.

The categories do not.

What stays the same

The contrast becomes clearer if we separate local values from common meanings.

That table captures most of the practical ambition.

The values vary.

The meanings remain recognisable.

Nobody needs Mars to have a Ceres-length year or Titan to adopt Martian holidays. What matters is that an R5 calendar tells the traveller the same kind of information that an R2 calendar did, at a different astronomical scale.

Portability is therefore semantic rather than metric.

Then comes Titan

The next move is more dramatic.

Our traveller accepts a role on Titan, or perhaps in a large orbital settlement serving the wider Saturnian system. By now both Mars and Ceres seem comparatively brisk.

Saturn takes almost thirty Earth years to orbit the Sun, and its Solarian calendar belongs to the whole planetary system rather than to each moon separately. Titan, Enceladus, Rhea, Iapetus and artificial settlements around Saturn all share the same heliocentric journey.

The system is R32.

Thirty-two human mears pass during one Saturnian orbital year. Thirty-two minths pass during one Saturnian orbital month. One such month lasts roughly two and a half Earth years.

Had our traveller arrived directly from twentieth-century Earth, calling that a month might have felt perverse.

But Mars and Ceres have already taught the relevant distinction.

Month is astronomical. Minth is human.

So ordinary activity continues at ordinary speed. Budgets do not wait two and a half years for the month to change. Schools do not need thirty-year planning cycles because Saturn's orbit happens to be long.

Organisations continue through weeks, minths and mears while the much slower astronomical calendar does its own job in the background.

The Saturnian year represents Saturn.

It is not asked to organise every recurring human activity inside the system.

Local physics remains local

A common Saturnian astronomical calendar does not make Titan and Enceladus physically interchangeable.

Titan has atmospheric weather, local illumination patterns and its own orbit around Saturn. Enceladus has a radically different environment. Artificial habitats may generate their own day-night patterns, gravity and agricultural cycles.

All of those are legitimate operational coordinates.

They simply do not all need to become civil-calendar units.

A Titanian engineer may care about local solar elevation, eclipse windows, Saturn's position in the sky and Titan's position around Saturn. A farmer inside a rotating habitat may care about an entirely manufactured agricultural season.

Specialist systems can represent those things precisely.

Trying to force every meaningful physical cycle into the civil calendar would make the calendar more complicated merely to avoid admitting that nature itself is complicated.

Solarian takes the opposite position:

Keep the civil grammar small. Let specialist systems describe specialist phenomena.

What the traveller actually learns

By the time our traveller reaches Titan, the boundary of the learning problem is fairly clear.

They do have to learn local language and terminology. They need to know local holidays, working customs and institutions. They need to understand that Saturnian months and seasons occupy very different physical scales from Martian ones. They may need to learn local legal rules governing which date appears on contracts, public records or personal documents.

But the underlying temporal grammar is already familiar.

They know how the week behaves. They know what a minth is for. They know what a mear is for. They know why an orbital month may be much longer — or shorter — than a minth.

They know that a local year describes the orbit rather than carrying every social function historically attached to Earth's year. And they know that one event can possess both a local civil date and a common chronological coordinate without either being less legitimate.

Moving worlds still requires learning.

The protocol simply puts a boundary around how much has to be relearned.

That is what useful standards usually do.

Common structure should not mean common culture

There is another side to portability.

Some things should become less portable.

A mature Martian civilisation ought to feel different from a Cererian one. Titan should not become an Earth suburb with Saturn pasted onto the sky.

Permanent settlement means communities accumulating their own history, language, institutions, habits and eventually assumptions that outsiders have to learn. Calendars will become part of that divergence.

A Martian New Year may acquire ceremonies rooted in settlement history. A Cererian community may develop social conventions for its long orbital months that nobody predicted. Certain Titanian mears may acquire cultural significance even though the protocol treats one mear exactly like another structurally.

That is desirable.

Interoperability should preserve translation.

It should not prevent culture.

Solarian therefore standardises the structural layer and deliberately leaves the human-facing layer open. Names can change. Holidays can be invented. Local traditions can become wonderfully incomprehensible to outsiders.

The underlying calendar still remains readable.

That is common structure; local culture in practice.

Leaving planetary systems behind

Eventually our traveller leaves Titan for an artificial habitat.

This time, imagine not the stable R3 world from the earlier chapter but a settlement whose trajectory changes substantially over time: perhaps a mobile industrial habitat, a transport settlement or some other community without a persistent heliocentric orbit that has acquired civic significance.

There may be no useful astronomical year to civilise.

That does not damage the human calendar.

The settlement can continue perfectly well with:

civil day → week → minth → mear

The astronomical layer can simply fall away.

This is not a degraded form of Solarian.

It is the architecture behaving as intended.

The mear belongs to people and operations.

It does not require a planet underneath it.

If that habitat later settles into a stable heliocentric orbit and its inhabitants decide that orbit matters to civic identity, an astronomical year can be adopted. If it does not, there is no reason to invent one merely to complete a diagram.

The protocol stops where the useful structure stops.

A calendar without a planet

That matters because artificial habitats may eventually account for a substantial share of human settlement.

Planets and moons are obvious destinations because nature has already assembled enormous amounts of matter into convenient locations. They are not necessarily ideal human environments.

A sufficiently capable civilisation may eventually find it easier to engineer gravity, radiation protection, atmosphere and climate directly than to adapt permanently to hostile natural surfaces.

If so, the distinction between the human operating calendar and the astronomical calendar becomes even more valuable. The human layer can travel. Its weeks, minths and mears do not have to be redesigned every time a settlement changes trajectory.

That is a fairly demanding test of whether the human cadence is genuinely human rather than simply terrestrial astronomy wearing a different label.

One person, several calendars

Our traveller has now lived in four very different temporal environments.

On Mars, a natural sol became the civil day and two mears fitted inside the local year. On Ceres, the standard human day returned and the year expanded to five mears. In the Saturnian system, thirty-two mears passed during one enormous local orbit. In mobile free space, the astronomical layer disappeared altogether while the human cadence continued.

The same person could reasonably regard all four as normal local calendars rather than temporary conversions from Earth time.

That distinction matters.

A multi-world protocol succeeds not when every calendar page looks identical.

It succeeds when a person understands why the pages differ without having to learn an entirely new theory at every destination.

The machinery should disappear

There is a temptation when designing systems such as Solarian to imagine ordinary people spending their lives thinking about Repeat Factors, reference directions and intercalation rules.

They almost certainly will not.

Most people on Earth cannot recite the complete Gregorian leap-year rule. They do not calculate astronomical epochs before accepting a dinner invitation.

Infrastructure works best when most of its machinery disappears beneath normal use.

A Cererian resident needs to understand that the local year contains five mears. They do not need to derive its long-run leap sequence each morning.

A manager on Titan needs to know where the organisation sits within the current minth and mear. They do not need to solve celestial mechanics before scheduling a review.

Software, institutions and standards carry the detailed machinery.

People carry the mental model.

Solarian only earns its complexity if that mental model remains small.

Recognisable difference

The central claim of this chapter is therefore fairly narrow.

A common civil-time architecture does not require everybody in the Solar System to inhabit the same calendar.

It requires different calendars to remain:

recognisably related

When our traveller moves from Mars to Ceres, the astronomy changes but the grammar survives. When they move from Ceres to Titan, the scale changes enormously but the grammar survives. When they leave stable natural worlds altogether, the astronomical layer can disappear while the human cadence survives.

That is different from imposing one calendar everywhere.

It is also different from allowing every settlement to reinvent time from scratch.

The useful middle ground is a protocol that defines what needs to remain common, permits what genuinely needs to be local, and then gets out of the way.

Future settlers should be free to make their calendars local enough to feel like home.

They should not have to make them so different that nobody else can read them.