Navigating the Stellar Ocean

01 / Foundation

We do not begin from nothing.

A stellar ocean is a useful image: planets and moons as destinations, orbital regions as places to work, and spacecraft as connections between them. It is not a physical description of space as a fluid. Gravity and motion still determine which paths are possible. ^[10]

The scientific foundations for a wider map already exist. The Barycentric Celestial Reference System (BCRS) defines a relativistic solar-system coordinate system centered on the barycenter, or center of mass. The International Celestial Reference System (ICRS) supplies its standard spatial orientation. Origin and orientation are separate choices. ^[1]

NASA’s Horizons system provides ephemerides: calculated descriptions of where objects are and how they move over time. SPICE connects trajectories, reference frames, and time representations. These are substantial pieces of existing navigation infrastructure, not ingredients that USST would need to invent. ^[2][3][17]

USST would organize these foundations into a readable, explicitly versioned framework. Its proposed contribution is the connection between a scientific record and the local maps, clocks, and calendars through which people use it.

Conventions can be agreed upon. Measurements must still be tested. On Earth, laboratories contribute clock data to the BIPM’s international timekeeping work; UTC is related to atomic time and, under the existing leap-second arrangement, kept in approximate agreement with Earth-rotation time. Earth’s orientation is measured separately through quantities published by the IERS. Neither process is a vote that moves a physical meridian or changes a planet’s rotation. ^[4][5]

02 / The map

Choose the reference. Measure the world.

The Sun is not fixed at the solar system’s center of mass. It, too, moves in response to the other bodies. A barycentric map and a map centered on the Sun are therefore related views, not identical ones. ^[6]

For everyday display, a flatter map may be easier to read than a three-dimensional coordinate list. I propose a System Reference Axis perpendicular to a declared reference plane, with a separately declared zero-longitude direction within that plane.

An axis alone is insufficient: it identifies a pole but does not say where longitude begins. Nor should the display imply that every orbit lies in one plane. The underlying coordinates would remain in the scientific reference system, with an explicit transformation into the chosen view.

The key requirement is continuity. Updating an ephemeris should not silently rotate yesterday’s map. A changed convention needs a new version and a documented transformation. Existing frame-handling software already demonstrates how explicit frame definitions and transformations can support different views of the same state. ^[17]

03 / The clock

A common timestamp is not an absolute “now.”

The base unit remains the SI second, defined through a specified caesium-133 transition frequency. A planetary rotation need not determine the unit with which time is measured. ^[7]

A possible first USST profile would use elapsed Barycentric Coordinate Time (TCB) from an explicitly selected epoch:

For example, the proposed origin could be the instant labeled JD_TCB = 2451545.0. That is a choice of label, not a newly discovered event. The same Julian-date number in TT, TDB, or UTC does not identify the same instant automatically.

Barycentric Dynamical Time (TDB) has a defined linear relationship with TCB. It is not an alternative spelling for it. A system using TDB-compatible ephemeris quantities must apply consistent time and spatial scaling rather than simply relabeling its numbers. ^[8][9]

A physical clock, meanwhile, measures its own proper time. Relating its reading to a coordinate time requires its trajectory and gravitational environment. “Synchronized” would mean that these relationships are known to a stated uncertainty—not that every uncorrected clock accumulates identical readings. ^[9]

A shared reference connects local clocks.
It does not erase their differences.

There is no need to install a master clock at the barycenter. There is also no instantaneous broadcast of system time: transmission and reception are different events. Light-travel corrections are already part of astronomical calculations, and must be distinguished from simultaneous-coordinate positions. ^[2]

04 / Orbital tempo

An orbit has a period. A clock has a rate.

Distance from the Sun gives a useful first picture of orbital motion. In an ideal circular orbit around a dominant central mass, the reference speed and period follow:

Here μ_☉ is the Sun’s gravitational mass parameter. The period–distance relationship is the circular-orbit form of Kepler’s third law. ^[10][11]

I propose calling this the orbital-tempo layer: a map of ideal reference speeds and periods across the stellar ocean. It could help someone understand the setting of an orbital station without pretending that distance alone determines its trajectory.

Real paths need more information. In a two-body elliptical orbit, speed also depends on the semimajor axis a:

A full state therefore needs position and velocity—or equivalent orbital elements—at a specified time. Multi-body perturbations and other effects add further requirements. ^[2][10]

None of these orbital periods is a clock-rate correction. Nor does a region of space acquire a compulsory civil time zone just because its ideal orbit has a particular duration. Navigation, clock conversion, and daily scheduling remain separate layers.

05 / Local worlds

Many calendars can describe the same event.

A common coordinate time does not abolish a Martian year or an Earth day. It makes translation between local expressions possible. For a sense of scale, the planets have the following approximate sidereal orbital periods. These are rounded reference values, not a live ephemeris. ^[12]

A Julian year is 365.25 days of 86,400 seconds. Earth’s sidereal orbital period is close to, but not exactly, one Julian year. ^[11][12]

A calendar needs a declared beginning and rules for counting cycles, not just a year’s approximate length. Lunar and satellite cycles can remain useful local choices. They simply need not define the common system-wide timestamp.

Planetarydians: a meridian tied to its world

I propose planetarydian as a name for a planet-specific meridian-and-time reference. It would identify the body, its rotational model, the meridian in use, and the chosen definition of rotational or solar phase.

This has an established basis. Planetary orientation models specify pole direction and a prime-meridian angle, conventionally called W, as functions of time. A model may include periodic corrections as well as a mean rotation rate. ^[13]

A sidereal rotation is measured relative to an inertial reference. A solar day follows the Sun’s return to a local meridian. The two must be distinguished. Nor can a planet’s spin be calculated from mass and distance from the Sun alone: axial rotation needs its own model. ^[3][12][13]

A planetarydian would expose those choices in a readable label. It would not disguise a complicated world as a uniform mechanical dial.

06 / Solar cycles

The Sun does not supply just one “day.”

The Sun is not a rigid body. Different regions of its plasma rotate at different rates. Any reference “day” must therefore say what is rotating: a region of plasma, a tracked feature, or an adopted coordinate grid. ^[14]

Solartation: the rotation of a declared grid

Solartation is proposed here as one rotation of a specified solar reference grid. For example, NAIF’s published pck00011.tpc uses a solar prime-meridian rate of 14.18440 degrees per ephemeris day. That gives:

This is a conventional sidereal grid rotation in that model’s TDB-based timing convention. It is neither the common rotation rate of all solar layers nor the apparent repeat interval seen from a moving Earth. ^[13][15]

Solorbitron: a trajectory, not yet a year

The Sun’s motion relative to the barycenter reflects the changing configuration of the other bodies. It does not supply one simple, fixed “solar year.” ^[6]

I therefore propose solorbitron as a name for a descriptor or study of that trajectory, rather than assigning it a universal period. A more specific convention might count crossings of a declared half-plane in a declared direction. Such a definition would need an ephemeris, geometry, and rules for irregular or absent crossings.

The name opens a subject for study. It does not require us to invent regularity where the motion does not provide it.

07 / Designed calendars

A System State Day would be a convention.

A synthetic System State Day (SSD) could be defined by averaging adopted rotation periods. For a specified body set, one candidate is a mass-weighted arithmetic mean:

The asterisks mark chosen reference values. Positive period magnitudes, time-scale conversions, treatment of differential rotation, and the dataset version would all have to be specified before adoption.

This would be mathematically defined, but not a collective physical rotation. Averaging frequencies instead of periods gives a different result. A quantity based on angular momentum needs moments of inertia and spin directions, not masses alone.

Mass weighting also gives the Sun overwhelming influence because it holds about 99.8% of the solar system’s mass. ^[14] A fixed-duration SSD would need its adopted inputs frozen and versioned; otherwise revisions could change the unit beneath existing timestamps.

A year on the Galactic scale

The Sun’s journey around the Milky Way gives a still larger sense of orientation; NASA gives roughly 230 million years for a trip around the Galaxy. ^[14] A proposed System Year could display phase within a specified Galactic-orbit model, but it would not be an exact metrological tick. Its model, epoch, phase definition, and uncertainty would need to remain attached.

08 / Solardians

Let light give distance an intuitive scale.

A solardian is proposed here as part of a solar-centered map notation combining radial distance with declared angular coordinates. Light-travel intervals provide a useful vocabulary for its distance component.

The vacuum speed of light is exactly 299,792,458 metres per second. A light-second therefore defines a length; it does not turn distance into a new kind of clock. ^[16]

A light-millisecond is nearly 300 kilometres: useful for a coarse map, but not by itself a close-navigation grid. Finer subdivisions can be defined without pretending the measurements have become more accurate.

A grid increment is a convention, not a physical quantum of spacetime. Extra decimal places do not supply the evidence needed to justify them.

A radius identifies distance. A meridian fixes a directional reference. A timestamp identifies a time coordinate. Together they can describe an event; none can substitute for the others.

09 / Shared records

Every number should carry its meaning.

A useful USST record would do more than display a new-looking date. It would preserve the information another observer or program needs to interpret and reproduce it.

Convention

Profile version, epoch, and the definitions behind the label.

Event time

Numerical value, time scale, uncertainty, and whether it marks emission, reception, or another specified event.

Spatial state

Origin, axes, position, velocity, units, and ephemeris or trajectory source.

Local reading

Body or station, rotation model, calendar rules, and any available proper-clock conversion.

Presentation

Map projection, solardian resolution, and optional orbital or calendar phases.

This is a proposal for information requirements, not a finished interchange standard. The test is traceability: can another implementation discover what a value means, transform it, and state how certain the result is?

Physical realizations would still require observations, clock calibration, trajectory estimates, and uncertainty control. A widely shared convention cannot make inaccurate measurements correct.

10 / The first implementation

Build the atlas before declaring the clock.

The first implementation should be a System Atlas: one event viewed through a barycentric map, a solar-centered map, a local rotational frame, and a local calendar. A clock conversion would appear only where the necessary physical model and data are available.

The atlas would use declared astronomical data rather than inventing positions. SPICE already provides reference-frame transformations and time-conversion infrastructure; the proposed atlas would add an accessible, unified presentation. ^[3][17]

Its checks should be concrete. A coordinate round trip should recover the starting value within a declared tolerance. Two implementations should agree within their stated uncertainties. A different calendar should change the label, not the underlying event. Missing data should produce a limitation, not a fabricated answer.

The examples embedded in this article illustrate only a few relationships. They are not that atlas, a live USST service, or operational navigation software.

Unification does not require identical local experience.
It requires reliable translation.

The stellar ocean remains an image. Coordinates, clock models, and conversion rules would be the working infrastructure beneath it. Different worlds can retain different days. Different communities can retain different calendars. The shared framework would make their relationships explicit.

That is the first step proposed here: not a new law of nature, but a way to connect established knowledge so that a wider environment becomes easier to imagine, inspect, and use.

Lucid Founder calling Earth.
Copy.