By Daniel Brannon
Everyone feels it, even if they don’t have the words for it.
The clock we trust to structure our days was designed for a world that no longer exists.
Twice a year, millions of people change their clocks not because Earth has changed, but because policy has. Time zones zig‑zag across borders in shapes that make no physical sense. The same instant has a different name in every country — and sometimes a different date. Every meeting across an ocean begins with arithmetic, and every spring the arithmetic breaks for three weeks because Europe and North America change their clocks on different Sundays.
Civil time is a patchwork of historical accidents, political compromises, and economic conveniences. It was built for railroads, legislatures, and regional commerce — not for a species that talks to itself across every longitude, all day, every day. It works well enough to keep each region running. It was never meant to keep a planet in step.
The strange part is that the solution already exists.
UTC is one time for the whole world. Every satellite, server, airline, and network already runs on it. It has no borders, no seasons, and no politics. But UTC was built for machines. It is a number with no picture. 14:00 UTC tells a person nothing about whether it is morning or night where they stand, where the Sun is, or how much daylight remains. So we keep it hidden behind our regional clocks and go on doing the arithmetic.
Umi‑Time does not replace UTC. It is UTC — the same instant, the same second, counted as a 360‑unit turn of the day instead of 24 hours — and it adds the one thing UTC never had: a picture of the day.
A dial that turns with your longitude.
A ring that shows sunrise, sunset, and twilight for wherever you are.
One number everyone on Earth shares, made locally meaningful by the sky.
UTC is a coordinate system without a map.
Umi‑Time is the map.
Every clock humanity has built reflects the world its builders believed they lived in. To understand why we need a new way to look at time, it helps to see how each era solved its own problem — and handed the next era a new one.
Before civilization invented clocks, humanity lived inside the rhythm of the Sun. Time was not measured — it was felt. Morning was the return of light. Noon was the moment the Sun stood highest. Evening was the lengthening of shadows.
The first clocks were not machines. They were shadows cast on stone, water flowing through bowls, light shifting across the ground. A sundial did not tell time; it revealed it — a direct expression of Earth’s rotation beneath the Sun.
Natural time was honest and local. It needed no conventions because the Sun itself was the reference. But it could not coordinate distant cities. Every place kept its own noon, and nobody needed it to be otherwise.
Mechanical clocks captured the rhythm of sunlight in gears and escapements. Time could now be held, repeated, and shared. Tower clocks struck the hours for whole towns; markets opened by the bell.
Yet these machines still pointed back to the sky. Noon was set when the Sun reached its highest point. Mechanical clocks did not replace natural time — they imitated it. Every town kept its own time, set by its own horizon. Mechanical time was a triumph of engineering, but not yet a system.
Railroads and telegraphs made distance disappear faster than the Sun could cross the sky. For the first time, distant cities needed to agree on what “now” meant — practically, urgently, with consequences measured in collisions and missed connections. Local solar time, drifting a minute for every fifteen miles of track, could not keep up.
Standard time solved this. The world was divided into zones, each adopting a shared offset from a chosen meridian. Noon stopped being the Sun’s highest point and became a convention defined by borders.
Industrial time was a triumph of coordination. It also severed the link between the clock and the sky, and it embedded politics into the hour. It solved the problems of its era and created the fragmentation we still live with.
The twentieth century measured time by the vibration of atoms — a rhythm so precise it made the Sun look primitive. Cesium became the new Sun. The second became a physical constant rather than a planetary experience.
From this foundation came UTC: a single, stable, astonishingly accurate global reference. It unified machines across continents. It made satellites, navigation, telecommunications, and the digital world possible. Every timestamp in every database on Earth ultimately rests on it.
But UTC was designed to be read by machines. It does not show the position of the Sun. It does not show the geometry of daylight. It is perfect, and it is faceless — which is exactly why we keep it in the back room and show people regional clocks instead.
Each era solved the problem in front of it and left a new one behind:
The world has become planetary.
Time, as people experience it, has not.
Before asking what comes next, it is worth being honest about what the current arrangement costs — because most of us have stopped noticing.
Civil time is so familiar that its failures feel like weather: irritating, unavoidable, nobody’s fault. They are not weather. They are design decisions made for the nineteenth century, and we pay for them every day.
Twice a year, more than a billion people are ordered to move their clocks by an hour. Not because Earth changed — because a legislature once decided it should be so.
The spring shift takes an hour of sleep from everyone at once. Studies have linked the Monday after it to measurable increases in heart attacks, strokes, workplace injuries, and fatal traffic accidents. Children’s sleep is disrupted for a week. Shift workers are paid for a seven‑hour night in March and a nine‑hour one in November, and payroll systems have special cases for both.
Then comes the mismatch. Europe changes on the last Sunday of March; North America on the second Sunday. For two or three weeks every spring, and one every autumn, the offset between London and New York is not what it was, and every recurring meeting that spans the Atlantic is wrong for one side. People show up an hour early to an empty call, or an hour late to an angry one. It happens every year. Everyone knows it will happen. Nobody can stop it, because stopping it requires two continents to agree on a Sunday.
And the arrangement cannot even be removed. The European Parliament voted in 2019 to abolish the clock change; it has been stalled in the Council ever since. The United States Senate passed permanent daylight time unanimously in 2022; the House never took it up. Mexico abolished daylight saving in 2022, so the offset between Mexico City and its northern trading partners now changes twice a year instead of staying put. A reform everyone wants has been stuck for years, because civil time is a coordination problem and coordination is exactly what civil time is bad at.
At this moment the same instant is being called by roughly thirty‑eight different names, depending on where you are standing.
Most differ by whole hours. Some differ by half an hour: India, Iran, Afghanistan, much of Australia. Nepal is offset by five hours and forty‑five minutes. New Zealand’s Chatham Islands sit at twelve hours forty‑five. Lord Howe Island observes a daylight‑saving shift of thirty minutes, the only place on Earth that does.
The zones themselves have little to do with the Sun. Spain lies west of Greenwich but has kept Central European Time since 1940, so Madrid’s solar noon in summer arrives after two in the afternoon by the clock. China runs on a single zone across five hours of longitude; in western Xinjiang the Sun is highest around three in the afternoon, and people quietly keep an unofficial local time two hours behind the official one. The zone boundaries wander around provinces, counties, and reservations in shapes that encode a century of local politics and nothing else.
The date is not safe either. In December 2011 Samoa moved itself across the International Date Line to align its week with Australia, and Friday the 30th simply did not occur. Kiribati did something similar in 1995. These were sensible decisions for those countries. They are also a reminder that in civil time, even what day it is is a matter of policy.
Because civil time is law, it changes the way laws change: suddenly, unevenly, and with whatever notice the government feels like giving.
In 2016 Egypt reinstated daylight saving and then cancelled it again, three days before the clocks were due to change. In the same year Turkey announced it would simply stay on summer time forever. In 2018 Morocco gave the country two days’ warning that the autumn clock change would not happen. Chile has rewritten its rules repeatedly, including a year on permanent summer time followed by a reversal. Kazakhstan merged its two zones into one in 2024. Russia has moved between permanent summer time, permanent winter time, and zone redrawings within a single decade.
Each change is defensible on its own terms. Collectively they mean that no one — not a person, not a program — can know what time it will be in a given city six months from now without checking whether a parliament has met.
Every piece of software that shows a time to a human carries the weight of all of the above.
It carries a database of every zone, every boundary, every historical rule, and every scheduled change — the IANA time zone database, updated several times a year, forever, because the rules never stop changing. When a country changes its mind on short notice, every device in the world needs a patch before the date arrives, and many do not get one. When the United States extended daylight saving in 2007, organizations spent months updating mail servers and calendars so that meetings would not silently shift by an hour. Some shifted anyway.
It carries the hour that happens twice. Every autumn, 01:30 occurs, and then an hour later 01:30 occurs again. Logs written in local time cannot be ordered during that hour. Incident timelines reconstructed across teams in different zones routinely disagree about whether the alert fired before or after the deploy, not because anyone is wrong, but because “01:30” is not a time — it is two times, and a timestamp without a zone is a sentence without a verb.
It carries the recurring meeting that is correct on one continent and wrong on the other for three weeks a year, the flight that lands “before” it took off, the stock exchange whose opening bell drifts an hour relative to its overseas counterparties twice a year, the contract whose deadline is “midnight” in a place the signatories have never been.
None of this is the engineer’s fault. It is the system working as designed. The design is the problem.
You do not need to write software to pay.
You pay when you call your parents abroad and do the subtraction in your head, and get it wrong because they changed their clocks last week and you have not yet. You pay when a conference says the deadline is “23:59 AoE” — Anywhere on Earth, UTC−12 — a convention that exists only because academics gave up trying to name a time zone everyone could agree on. You pay when you land after a long flight and your watch, your phone, and your body disagree about what hour it is, and the only honest one is your body.
You pay when a broadcast says the match starts at eight and you do not know whose eight. You pay when the online store says the sale ends at midnight and you have to guess which midnight. You pay every time you type what time is it in into a search engine — one of the most common questions people ask the internet, asked by people who simply want to know whether it is reasonable to call someone.
Each of these is small. Together they are a constant, low‑grade friction on every interaction that crosses a border — and more of our interactions cross borders every year.
It is tempting to think civil time just needs tidying: abolish daylight saving, round the odd offsets, redraw a few boundaries. Every one of those fixes has been proposed. Most have been tried somewhere. None has stuck globally, and none can, for the same reason: civil time is a set of independent local decisions, and there is no mechanism by which independent local decisions converge.
Each region optimizes for itself. Each fix is another patch. The patches accumulate, the database grows, and the system continues to function only through constant human maintenance. It is a system that works despite itself.
The clock we inherited was designed for a world connected by railways, telegraphs, and telephone lines. Those systems needed to coordinate regions, nations, and continents. Time zones solved that problem extraordinarily well.
The systems that connect people today operate at a different scale. The Internet, satellites, mobile networks, cloud services, and global communications routinely connect people on opposite sides of the planet. Millions of people now spend part of every day coordinating across multiple time zones.
Civil time did not become worse. The world simply outgrew the problem civil time was designed to solve.
So the honest conclusion is not that civil time needs reform. It is that civil time is the wrong tool for the one job it was never designed to do: letting people on different parts of the planet agree about when.
For that job, a different tool already exists.
Let’s be clear about what UTC is. It is the solved problem.
It is one time for the whole world, maintained by the finest clocks humanity has ever built. It has no borders, no seasons, no daylight saving. Every connected system already speaks it. Nothing in the previous section happens to UTC: it did not change in March, it has one name for every instant, no parliament can move it on three days’ notice, and 01:30 happens once. Any proposal that asks the world to abandon UTC is asking the world to re‑solve a problem it has already solved.
Umi‑Time does not ask that. Umi‑Time keeps UTC exactly as it is.
What UTC left out is unambiguous human-friendly presentation. The format hh:mm:ss was inherited from local civil clocks, and it carries their connotations. 07:00 says morning to everyone who reads it — which is a lie for most of the planet when the 07:00 is UTC. Shown in that format, universal time looks like someone else’s local time. People translate it back to their own zone and the universality evaporates.
For most of UTC’s history, this limitation hardly mattered. Universal time was primarily the domain of specialists: pilots, navigators, astronomers, military operations, and telecommunications networks. Ordinary people lived almost entirely within local clocks and rarely needed anything else.
That world has changed.
Today, millions of people routinely coordinate across continents. Distributed teams collaborate across oceans. Open-source projects, online communities, multiplayer games, global businesses, international families, and worldwide events all depend on people agreeing on the same moment from different places.
The need for a shared global time reference is no longer confined to specialists. What was once a niche requirement has become an ordinary part of life for an ever-growing share of humanity.
UTC already solved the coordination problem. What it never solved was how to make that shared reference feel natural to the people who increasingly need it.
UTC’s only flaw as a human clock is that it was never given a way to be human without being misinterpreted as local. That is the gap Umi‑Time fills — and it fills it without touching the underlying time. Umi‑Time separates a shared universal time value from the local and solar context used to interpret it.
The next step is not a new time scale. We have one, and it is excellent. The next step is to let people see it, in a locally meaningful light.
Umi‑Time counts the UTC day as 360 umi (ᵘ) instead of 24 hours. One umi is four minutes. One umi‑second is one SI second, the same second UTC uses; there are 240 of them in an umi.
That is the whole definition. 00:00:00 UTC is 0ᵘ. 12:00:00 UTC is 180ᵘ. 15:40:38 UTC is 235ᵘ 38ˢ, written 235:038. The conversion is exact in both directions, down to whatever fraction of a second your clock resolves.
Because it is UTC, the umi value is identical everywhere on Earth. There is nothing to convert. A meeting at 105ᵘ is at 105ᵘ in Lisbon, Delhi, and Honolulu. A log entry at 2026-08-24U235:038 means the same instant to every system that reads it. No offsets, no DST rules, no tzdata lookups to agree on what happened when.
The number, on its own, deliberately tells you nothing about where you are in the day. That is not a defect; it is the point. The number is universal. Local meaning comes from your relationship to the Earth beneath you, not from the number itself.
Umi‑Time separates four concerns that conventional timekeeping often mixes together.
Layer 0: Universal Time. UTC provides the underlying universal time reference. It is the same everywhere and serves as the foundation upon which everything else is built.
Layer 1: Umi‑Time Representation. UTC is represented as a continuous 360‑umi cycle. This creates a single universal value shared by everyone on Earth.
Layer 2: Local Interpretation. Longitude relates that universal value to an observer’s local day, producing concepts such as Umi‑Time noon, Umi‑Time midnight, Umi‑Day, and Umi‑Date.
Layer 3: Solar Context. Sunrise, sunset, twilight, and other solar phenomena are computed from location and date and layered on top of the time value and its local interpretation.
The layers build on one another without modifying one another. UTC remains UTC. The Umi‑Time value remains universal. Local interpretation remains geographic. Solar context remains astronomical.
This separation is the central idea behind Umi‑Time. A single universal value can be shared globally while remaining meaningful locally.
The reference analog implementation of Umi‑Time uses a circular dial with 0ᵘ at the bottom and the umi increasing clockwise, one full turn per day. A single hand sweeps once around in 24 hours.
The dial is then rotated by your longitude — clockwise for east, counterclockwise for west, one degree of rotation per degree of longitude. After that rotation, the umi value at the bottom of the dial is Umi‑Time midnight for your location, and the value at the top is Umi‑Time noon. Morning is the left half; afternoon and evening the right.
Nothing about the number changed. The hand still points at 105ᵘ. But in Lisbon the dial has turned so that 105ᵘ sits in the morning quadrant; in Delhi it sits near the top; in Honolulu it sits low on the evening side. Three people look at the same value and each sees, immediately and without arithmetic, where it falls in their day.
That is the entire trick: universal number, local interpretation. Civil time puts the local meaning into the digits and forces everyone to translate. Umi‑Time keeps the value shared and lets each observer derive local meaning from their relationship to the Earth beneath them.
In the reference analog implementation, a fixed solar ring surrounds the dial and carries the sky.
Computed from your latitude, longitude, and the date, the ring marks sunrise and sunset, and shades the bands of twilight between them — civil, nautical, astronomical, and the photographer’s golden and blue hours. Physical solar noon drifts a few minutes either side of the top over the course of the year, exactly as it does in the real sky.
The solar ring is one way to represent the solar context defined by Umi‑Time. The umi value itself does not know or care about the Sun; it is UTC expressed as a universal coordinate. Solar context is computed separately and layered on top. The ring lets you see, at a glance, that 105ᵘ in Honolulu is after sunset, that there are forty umi of daylight left in Lisbon, or that the Milky Way will be visible in the Atacama once the hand crosses the astronomical‑twilight boundary.
For a traveler, set the dial to the destination and you can see its day before you arrive. For a distributed team, place several dials side by side and the overlap of daylight becomes visible without a single conversion.
The same solar context can be presented in other ways. A digital display might show daylight remaining, the current twilight phase, or upcoming sunrise and sunset events. The solar ring remains the reference analog implementation because it makes the relationship between universal time and local solar conditions immediately visible.
Not every implementation is visual. A phone lock screen, a status bar, a calendar entry, a command-line tool, the corner of a monitor — most places people encounter time are textual or digital. Umi‑Time therefore provides a digital form that preserves the same principles as the analog representation: a universal time value accompanied by optional local context.
The universal component is the umi value itself: 105ᵘ. That value is identical everywhere on Earth.
Local context can then be added in several ways. The most practical is the day phase: the phase symbol Φ and a number from 0 to 23, indicating which twenty‑fourth of the local Umi‑Day the value falls within, counted from Umi‑Time midnight. Each phase spans fifteen umi — one hour — making the phase familiar and immediately understandable. Φ0 is the hour after midnight, Φ6 is around dawn, Φ12 is the hour after noon, Φ18 is early evening, and Φ23 is the final hour before midnight.
A display showing 105ᵘ Φ9 therefore conveys two pieces of information: the universal time value, shared by everyone everywhere, and the observer’s local position within the day. Spoken, it is simply “105, phase 9.”
Three people looking at the same moment might see:
Lisbon 105ᵘ Φ6 early morning
Delhi 105ᵘ Φ12 just past noon
Honolulu 105ᵘ Φ20 evening
Same number. Different phase. No conversion is required; the phase is derived from the reader’s own longitude rather than negotiated with anyone else.
The phase never changes the umi value. It is a reading aid that provides local context while preserving the universal time value itself. The specification also defines other forms of local context, including segment-based and longitude-based representations, but the day phase is likely to be the most intuitive because it maps directly onto the familiar human sense of hours within a day.
Where the Φ glyph is unavailable, a plain P may be used (105ᵘ P9). This form is also used by the specification’s strict machine-readable timestamp format. The timestamp serves systems; the phase serves people.
If Umi‑Time is simply a different representation of UTC, why use 360 umi instead of hours, minutes, and seconds? Because 360 is not an arbitrary choice. It is the number that makes geography, rotation, and time align naturally.
Earth turns 360° in a day, so the mean Sun crosses one degree of longitude every four minutes — exactly one umi. That single fact collapses all the geometry:
There is a human reason as well. 14:00 lies to most of the planet; it asserts an afternoon it does not possess. 210ᵘ asserts nothing. It carries no inherited local meaning, allowing local context to be added independently. And 210ᵘ can only ever be Umi‑Time, which means it can only ever be UTC. No reader will mistake it for someone’s local clock.
Finally, 360 is a generous number. It divides evenly into halves, thirds, quarters, sixths, eighths, twelfths, twenty‑fourths, and more. The day splits into 24 phases of 15ᵘ, or 8 segments of 45ᵘ, or 6 of 60ᵘ, always on whole units. Fifteen umi is an hour. Ninety umi is a quarter‑day. The old fractions still work; they just stop needing the colon.
This is the same relationship navigators have exploited since the first marine chronometer: time is longitude. Umi‑Time simply chooses the unit in which that relationship becomes literal.
Everything above follows from a small number of commitments.
Universal first. The time value is shared by everyone and owned by no one. It is UTC, and it stays UTC. Nothing local is ever written into the number.
Layered by design. Universal time, local interpretation, and solar context are distinct concerns. Umi‑Time keeps them separate so that each can be understood, computed, and presented independently without modifying the others. The time value remains universal. Local interpretation remains geographic. Solar context remains astronomical.
Local second — and always visible. Local meaning is essential, but it belongs in interpretation rather than in the time value itself. Two people in the same place share both a Umi‑Time value and its local meaning. Two people on opposite sides of the Earth share the same Umi‑Time value while interpreting it within different local days. Neither needs to convert anything.
No politics in time. Local interpretation is derived from longitude, a physical quantity. Time zones, daylight saving rules, and legislation have no role in determining the Umi‑Time value or its local interpretation. Communities may still agree that work begins at a particular umi or phase, but those are social conventions. Umi‑Time does not attempt to eliminate conventions; it eliminates legislated offsets.
Compatible by construction. Any system that stores UTC already stores Umi‑Time. Adoption requires no new infrastructure, no new epoch, no migration. Only the representation changes.
Honest about the Sun. Umi‑Time noon is a longitude‑based reference, not physical solar noon. The two differ by the equation of time and related solar effects. Umi‑Time preserves that distinction rather than hiding it. Solar context describes the sky; it does not define the time.
Simple enough to explain in a sentence. It’s UTC counted in 360ths, with longitude‑based local interpretation and optional solar context. If a system cannot be explained that briefly, it will not be adopted voluntarily — and Umi‑Time can only be adopted voluntarily.
A software team has members in Lisbon, Delhi, and Honolulu. Today their standing meeting is “09:00 Lisbon,” which is 13:30 in Delhi and 22:00 in Honolulu — except for the three weeks in March and the week in October when Europe and the United States are out of step on daylight saving and someone shows up an hour wrong.
In Umi‑Time the meeting is at 120ᵘ. That is the whole invitation. Each member’s dial shows where 120ᵘ falls in their own day: mid‑morning in Lisbon, just after noon in Delhi, late evening in Honolulu — the ring in Honolulu already dark. Nobody converts. Nothing changes in March. If the team wants a fairer slot, they lay the three dials side by side and look for the umi where all three rings are lit.
A landscape photographer is scouting a shoot in the Dolomites for early June. She needs to know when golden hour starts, when the blue hour fades to civil twilight, and when the sky is dark enough for stars.
She sets the dial to the location and the date. The ring draws it for her: golden hour beginning at 274ᵘ, sunset at 285ᵘ, civil twilight ending at 295ᵘ, astronomical darkness from 325ᵘ. These are the same numbers her camera’s UTC clock and her GPS track will record, so every frame’s timestamp lines up with the sky it was shot under, without the usual “which time zone was the camera set to” puzzle.
When she moves on to Iceland in July, the ring shows no astronomical twilight at all — the sun never gets low enough — and she plans accordingly, before the flight rather than after.
Aviation gave up on local time decades ago. Flight plans, weather, clearances, and logs are all in UTC, which pilots call Zulu. A pilot departing Frankfurt for Tokyo files an off‑block time of 2200Z and an ETA of 0930Z.
In Umi‑Time those are 330ᵘ and 142ᵘ — the same instants, no conversion — but now the pilot can glance at a dial rotated to Tokyo’s longitude and see that 142ᵘ falls in early evening there, with the ring showing sunset less than half an hour after arrival. The planning value of Zulu is preserved; the human context Zulu never provided is added.
tzdata AgainA developer is building a dashboard for a global incident‑response team. Internally everything is UTC, as it should be. The problem is the display: every user wants “their” time, which means time‑zone databases, DST rule updates, and the inevitable bug where two engineers disagree about whether an alert fired before or after a deploy.
With Umi‑Time, the timestamp 2026-08-24U235:038.25 is displayed as‑is to everyone. It sorts, compares, and diffs as plain UTC because it is plain UTC. The dial widget beside it takes the user’s coordinates — not a time zone — and rotates. If the team needs civil time for a specific jurisdiction, that remains available as an auxiliary indicator; it is just no longer the thing everyone has to agree on first.
| Dimension | Civil Time | UTC | Umi‑Time |
|---|---|---|---|
| What it is | Legal local time: UTC plus a political offset, sometimes with a seasonal shift | The world’s reference time, kept by atomic clocks | UTC represented as a continuous 360‑umi day, with optional local interpretation and solar context |
| Same value everywhere | No — ~38 offsets in use | Yes | Yes — identical to UTC by construction |
| Conversion needed to coordinate across regions | Yes — offsets and DST rules on both sides | No | No |
| Daylight Saving Time | Yes, in many regions | No | No |
| Leap seconds | Inherited from UTC | Yes, until their scheduled end (by 2035) | Inherited from UTC |
| The number alone tells you the local phase of day | Yes — 07:00 is morning wherever you are |
No | No — local interpretation is provided separately |
| Provides local day context | Built into the displayed time value | Not directly | Yes — through longitude‑based local interpretation |
| Represents solar context | Not directly | No | Optionally — through computed solar context such as sunrise, sunset, and twilight |
| Alignment with physical solar noon | Off by the zone offset and DST — up to ~2 h | Only at 0° longitude | Within the equation of time (±16 min) at every longitude |
| Legal or infrastructure change to adopt | — | — | None — any system that stores UTC already stores Umi‑Time |
| Familiarity today | Universal | High among engineers, pilots, scientists | None — must be learned |
| Built for | Regional daily life | Machines and global synchronization | Universal coordination with locally meaningful interpretation |
Civil time’s great strength is that its digits carry local meaning: 07:00 is morning wherever you are. Its great weakness is that this meaning is regional, so the same instant acquires dozens of different names, and those names can change with legislation and season. Civil time coordinates a region well and a planet poorly.
Umi‑Time inverts the trade. The time value is universal, while local meaning is derived separately from the observer’s longitude. Coordination across regions becomes trivial because everyone shares the same value, while local context remains immediately available through local interpretation. For someone whose life rarely crosses time zones, civil time remains perfectly adequate. For someone coordinating across regions, the inversion quickly becomes useful.
Civil time places local meaning directly into the displayed number. Umi‑Time keeps the number shared and places local meaning in a separate layer. One approach optimizes for local familiarity; the other optimizes for universal consistency.
Neither approach eliminates the need for local context. The difference is where that context lives. Civil time bakes it into the timestamp itself. Umi‑Time derives it from geography while preserving a single universal value for everyone.
Umi‑Time and UTC are not alternatives. Umi‑Time is UTC. The comparison is between two ways of representing the same quantity.
hh:mm:ss is the familiar representation, and that familiarity becomes a liability when the time is universal. It looks like local civil time, so people instinctively interpret it as local civil time and begin converting it. The umi representation avoids that problem. A value such as 210ᵘ has no inherited association with a particular hour of the day, so it remains unmistakably universal.
Additional local meaning can then be provided separately. A day‑phase indicator, longitude context, local interpretation, or other presentation layer can tell a reader where that shared value falls within their day without changing the value itself. The universal time stays universal; the local meaning remains local.
UTC tells systems exactly when something happened. Umi‑Time aims to let people share that same universal moment without immediately translating it into dozens of regional representations.
Machines should continue speaking UTC in whatever format is most useful to them. Umi‑Time exists for the moment a person looks at the screen.
A manifesto that lists only benefits is advertising.
Here is what Umi‑Time asks of you, and what it does not fix.
235:198 means nothing to anyone alive today.
It takes time before “about 235” feels as natural as “about quarter to four.” Although Umi‑Time retains familiar relationships within the day, the numbering system itself must be learned. There is no traditional hour-sized unit between the umi (four minutes) and the day. Day phases provide a useful bridge, but even they require some acclimation.
07:00 is morning anywhere on Earth.
105ᵘ is morning in Lisbon, lunchtime in Delhi, and late evening in Honolulu.
Umi‑Time deliberately trades built‑in local meaning for a shared global value. Local context is provided separately through longitude‑based interpretation, day phases, or other contextual indicators. The universal value remains the same for everyone; understanding where it falls within the local day requires that additional context.
“School starts at 9” is a social agreement, not a time‑zone artifact.
In Umi‑Time that agreement still has to be made, and it will be made differently in every city. What disappears is the legislated offset and the DST switch, not the human habit of agreeing when the day begins, when businesses open, or when people gather.
Umi‑Time inherits the UTC calendar date, which rolls over at 0ᵘ. For some people that occurs near the beginning of the local day; for others it occurs in the middle of daily activities.
The specification provides a local Umi‑Date for situations where the calendar should follow the observer’s day, but that introduces an additional concept that must be understood.
Umi‑Time noon is a longitude‑based reference. Physical solar noon varies throughout the year because of the equation of time and related astronomical effects.
Umi‑Time preserves this distinction rather than hiding it. Solar context can describe where the Sun actually is; the time value itself remains independent of solar conditions.
235198 is syntactically similar to many existing time formats.
The U prefix and forms such as 235:198 exist to eliminate ambiguity, but the potential for confusion is real and the habit of using unambiguous forms must be learned.
This is the largest cost and the one no specification can remove.
A shared clock is only valuable when it is shared. Early adopters bear the full cost of explaining and translating the system until enough other people begin using it.
It does not measure Earth’s rotation; it represents UTC.
It is not more precise than UTC; it is UTC.
It does not eliminate geography; it separates universal time from local interpretation.
It will not abolish time zones by itself. It offers an alternative way to coordinate across regions, starting with the situations where time zones create the most friction.
If, knowing all of this, one shared number with locally meaningful interpretation still sounds better than dozens of regional numbers describing the same moment, read on.
Umi‑Time does not require the replacement of anything. UTC stays exactly as it is — Umi‑Time is UTC, and that never changes. Civil time keeps running local life for as long as people want it to. Umi‑Time arrives as a third view of the same instant, the one you reach for when the conversation crosses a border, and it can be adopted by one person, one team, or one industry without waiting for anyone else.
That is the design, and it is the only design that can work: any proposal that requires existing systems to change first will never be tried.
But coexistence is a starting condition, not a goal. Two clocks for the same moment is friction — one more translation, one more chance to be an hour wrong. If the world finds enough value in a shared clock, there is no reason in principle that civil time must persist beside it forever. Umi‑Time can carry local life as well as global coordination: the dial already shows morning, noon, and night for wherever you stand, and the conventions that civil time encodes — when work begins, when shops close — can be expressed in umi as easily as in hours.
That replacement would take decades at a minimum, would happen region by region, and would happen only because people chose it. It may never happen at all. But it should not be ruled out, and the period of running two clocks should be as short as the world is willing to make it.
Because Umi‑Time is UTC, integration is a display problem, and display problems are cheap.
A clock face, a dashboard widget, a column in a log viewer, an extra field in an API response — each can show Umi‑Time next to the formats already there, derived from the same stored timestamp. A scheduling tool can offer a Umi‑Time view without changing its model. A map can render the terminator from the umi value directly. None of this requires new standards bodies, new hardware, or new epochs.
The reference implementation, the clock and world‑map demos, and the embeddable web component exist for exactly this reason: so that adding Umi‑Time to something is an afternoon’s work, not a project.
Voluntary standards win by being useful somewhere specific before they are useful everywhere. Umi‑Time’s natural first homes are the places where people already live in UTC and already feel the lack of a picture:
Each of these communities can adopt Umi‑Time alone, without waiting for anyone else, and gain something on day one.
If it spreads, it will spread the way the 24‑hour clock did in the places where it spread: first as something seen on a screen, then as something used in a particular context, then as something expected.
Familiarity comes from exposure — a dial on a watch, a map that turns, a timestamp with an unfamiliar suffix that turns out to be unambiguous. Fluency comes from use — the first time a team realizes the March meeting didn’t break, the first time a photographer plans a shoot from the ring. Expectation comes last, and only if the first two are earned.
None of these stages requires anyone to be forced. That is the only kind of adoption a time representation can have.
Every system humanity builds reflects the world it believes it inhabits. Civil time was built for a world divided by borders. UTC was built for a world connected by machines. Umi‑Time is built for the world we have now: one where the machines are already connected and the people are still doing arithmetic.
The near horizon is a world where, when two people in different countries talk about when, they reach for a number they both already share — and each can immediately see what that number means under their own sky. Civil time is still there; it is simply no longer the thing everyone has to agree on first.
The far horizon is a world that no longer needs two clocks. Not because anyone was made to give one up, but because one of them stopped earning its place. That is a long way off, and it may not come. But it is the direction.
Noon becomes a planetary moment, sweeping westward at one degree of longitude per umi, visible on a map. Midnight follows it. Sunrise and sunset stop being local secrets and become positions on a ring anyone can read for anywhere. The day is understood as what it physically is: one rotation, experienced differently at every longitude, described by one number.
The near horizon is modest and achievable. It asks nothing of governments. It asks nothing of infrastructure. It asks only that people find it useful enough to look at. The far horizon is reached, if at all, by the same route.
You have done the arithmetic. You have shown up an hour wrong in March. You have asked “which time zone was that in?” about a timestamp that should have answered the question itself.
Umi‑Time is not a demand that you stop. It is an invitation to try something simpler where it helps.
Begin by noticing. Notice that your phone already knows UTC and hides it from you. Notice how much of the friction in your week is translation between clocks that describe the same instant. Notice the Sun, and how little your clock has to say about it.
Use it where it clarifies. Put a dial on your screen. Give a cross‑border meeting a umi value and see whether anyone needs to convert. Plan one shoot, one flight, one deployment window with the ring instead of a table of offsets.
Share it where it resonates. The reference implementation is open. The specification is open. The components are built to be dropped into whatever you already have. If it helps you, it will help someone else, and the only way a shared clock becomes shared is one person at a time.
A connected world deserves one clock it can hold in common — universal in value, local in meaning.
The number already exists. The map is ready.
The day is already turning.