Decimal Time¶

A time-of-day representation that fixes a day boundary and subdivides the day through powers of ten, so unit changes become decimal-point shifts rather than mixed-radix conversion.

Version: v1 · 2026-08-30 · History
Domain-specific #: 1631
Origin domain: timekeeping systems
Subdomain: time-of-day units and notation
Aliases: Decimalized time, Decimalised time

Core Idea¶

Decimal time is a system for representing time of day by taking one declared day as the whole and dividing it through powers of ten. In the canonical complete form, the day has ten decimal hours, each hour has one hundred decimal minutes, and each minute has one hundred decimal seconds. One day therefore contains 100,000 decimal seconds. The same instant can be written as a fraction of the day, a decimal-hour value, or a fielded clock value without mixed-radix arithmetic: 0.54321 day = 5.4321 decimal hours = 5 h 43 min 21 s = 54,321 decimal seconds.

The defining move is not “write a conventional timestamp with decimal digits.” Ordinary 13:45:30 uses decimal glyphs but retains a mixed hierarchy: 24 hours per day, 60 minutes per hour, and 60 seconds per minute. A fully decimal system aligns the unit hierarchy with radix-ten positional notation. Moving the radix point changes the unit scale because every transition is a power of ten.

The best-known institutional instance is French Republican decimal time. The National Convention divided the midnight-to-midnight day into ten hours, each hour into one hundred minutes, and each minute into one hundred seconds.^[1] The reform belonged to a larger project of rationalizing weights, measures, money, calendars, and clocks. Scholarly histories track both its coherent design and its failure to displace existing social and mechanical time infrastructure.^[2]^[3]

The abstraction is broader than that episode. Ancient Chinese timekeeping included a hundred-ke division of the day alongside duodecimal systems, although subdivisions and coexistence rules varied and did not always make a complete decimal hierarchy.^[4] Astronomers routinely represent instants as day counts with decimal day fractions, as in Julian dates, but that is a related fractional-day coordinate rather than automatically a ten-hour civil clock.^[5] These variants make the boundary useful: decimal time is a family of time representations with a declared temporal whole and radix-ten subdivision, while fully decimal time reserves the strong case in which all displayed subunits belong to one power-of-ten hierarchy.

Structural Signature¶

The defining roles are:

the reference whole — ordinarily one civil, mean-solar, or otherwise specified day;
the day boundary — midnight, noon, local apparent solar midnight, or another declared origin at which the coordinate resets or the day number changes;
the underlying time scale — the physical or civil convention that determines which instants and day lengths the representation is applied to;
the radix-ten partition rule — one or more divisions by 10^k, with a complete system keeping every displayed tier inside the decimal hierarchy;
the unit ladder — named or unnamed day fractions such as decimal hours, minutes, seconds, centidays, or bare fractional-day places;
the time-of-day coordinate — a number f in [0,1) or an equivalent scaled value giving elapsed fraction since the day boundary;
the notation rule — radix point, digit grouping, field widths, separators, and endpoint convention;
the conversion map — a reversible mapping between the decimal coordinate and the operative conventional or physical time scale;
the clock or computational carrier — dial, watch, printed record, astronomical table, software field, or other medium that displays or operates on the coordinate;
the coordination regime — the community and procedures that decide whether the representation is private, scientific, local civil, or interoperable public time.

Locked signature: fix the temporal whole, boundary, and underlying time scale -> map elapsed time to a day fraction -> subdivide or display that fraction through powers of ten -> permit unit changes by place shifting in the full hierarchy -> decode back to an instant under the same boundary and day-length conventions.

The strict recognition test requires more than a decimal numeral. A claimant must expose the temporal whole, origin, decimal partition, notation, and conversion. To qualify as fully decimal time, every named field from day downward must have a power-of-ten ratio to its neighbor. A hybrid can be described accurately as a decimal fraction of an hour, second, or day without being promoted to a complete decimal clock system.

What It Is Not¶

Decimal time is not ISO 8601 clock notation. ISO 8601 represents time with the 24-hour system, and the familiar fields remain hour, minute, and second; a decimal fraction may extend the smallest unit.^[6] 18:30:00.000 is standardized and uses decimal digits, but its hour/minute/second boundaries remain 24/60/60.

It is not payroll decimal hours. Writing seven conventional hours and thirty minutes as 7.5 h decimalizes the fraction of a conventional hour. The hour is still 1/24 of a day, and clock minutes remain sixtieths. This is a useful partial decimal quantity, not a ten-hour day.

It is not automatically metric time. The SI base unit of time is the second, and SI prefixes give decimal multiples and submultiples of that unit. The BIPM separately records the long-standing minute, hour, and day relations as 60 s, 3600 s, and 86,400 s.^[7] A nanosecond is decimal relative to the second; that fact does not decimalize the civil day.

It is not a decimal Unix timestamp. Printing an integer count of SI seconds since an epoch in base ten uses Decimal notation, but the encoded civil-day structure remains conventional and the count need not reset daily. Epoch, continuous count, radix of storage, and time-of-day unit hierarchy are independent choices.

It is not the French Republican calendar as a whole. The calendar altered years, months, ten-day décades, names, and civic observances. Republican decimal time was its intraday system. A decimal calendar need not use decimal hours, and a decimal clock need not change the calendar date.

Finally, it is not a claim that decimal units are physically truer. The partition is representational and conventional. Its merits concern arithmetic and interface coherence; its costs concern divisibility, habit, interoperability, hardware, language, and institutional change.

Scope of Application¶

The primary scope is horology and civil time-of-day representation. A clock face can display ten hours per day, a record can write decimal hours and minutes, and a schedule can be expressed as fractions of a day. The French reform proves that the role system was implemented in public clocks, watches, legal prescription, and official discourse rather than existing only as a numerical thought experiment.^[1]^[3]

Historical metrology provides independent variants. Yan and Lin describe ancient Chinese coexistence among a decimal time law, a duodecimal law, and a clepsydra law, with the hundred-part day tied to instruments and time-telling machinery.^[4] This is important evidence for recurrence and for mixed-system boundaries: a hundred divisions of the day can be decimal at one level while lower subdivisions or social usage remain nondecimal.

Astronomy and geodesy often use fractional days. The US Naval Observatory defines Julian date as a continuous count of days and fractions of a day from a noon origin and warns that the time scale must be specified in precise work.^[5] That representation shares the fractional-day conversion core, but it is not a civil ten-hour clock and its day number changes at noon.

Software and data systems can use a normalized day fraction internally, especially for interpolation, visualization, or cyclic scheduling. Such use qualifies only when the whole, origin, scale, and conversion rules are explicit. A bare floating-point value between zero and one is not self-identifying.

The scope excludes vague claims that a timer is “decimal” merely because it has decimal digits, milliseconds, a decimal database type, or a base-ten epoch count.

Clarity¶

A complete decimal-time specification answers nine questions:

What counts as one day, and can its physical duration vary?
At what instant does the day coordinate start and reset?
Which time scale or civil convention underlies the coordinate?
How many top-level units divide the day?
How is each unit subdivided?
Is the system fully decimal or only one field/fraction decimalized?
What notation and endpoint convention distinguish the start from the end of a day?
How are rounding and carry handled at the smallest displayed place?
How are dates, time zones, daylight-saving transitions, and leap seconds handled outside the intraday numeral?

The day-length question matters. A model may stipulate 1 day = 86,400 SI seconds, as the BIPM conversion table does for the conventional day.^[7] Civil UTC can include leap-second complications, while historical apparent-solar clocks tie the day to local solar observation. A conversion is not fully specified until its day convention is declared.

The simplest diagnostic is to ask whether changing units is a radix-point shift. In the French hierarchy, 5.4321 decimal hours equals 543.21 decimal minutes and 54,321 decimal seconds. In conventional time, 5.4321 hours cannot be read by shifting the point into ordinary minutes because one hour contains sixty minutes.

Manages Complexity¶

Conventional time arithmetic mixes moduli. Adding durations can require carries at 60 seconds, 60 minutes, and 24 hours; representing a fraction of a day requires division by 86,400. Decimal time reduces the intraday coordinate to positional arithmetic. A single numeral can support comparison, interpolation, percentage-of-day displays, and rescaling across units.

The simplification is strongest when the internal representation and public notation are the same. A normalized value f can drive a dial, schedule, database field, or graph without decomposing through heterogeneous radices. Digit positions have stable power-of-ten meanings, so precision and truncation become visibly aligned with the unit hierarchy.

That compression does not eliminate temporal complexity. Calendars, zones, daylight-saving folds and gaps, relativistic or astronomical time scales, leap seconds, clock synchronization, and uncertainty remain separate problems. Decimal time simplifies the coordinate chosen for one day; it does not solve timekeeping as a whole.

Abstract Reasoning¶

Let T be the duration assigned to one reference day, t0 its boundary, and t an instant within the day. Define the normalized elapsed fraction

\[ f=\frac{t-t_0}{T}, \qquad 0\le f<1. \]

For the French-style system,

\[ h_d=10f,\qquad m_d=100h_d,\qquad s_d=100m_d=100000f, \]

where the equations on the right name total decimal hours, minutes, or seconds, not field remainders. The fielded representation is obtained by carries:

\[ H=\lfloor10f\rfloor, \]

\[ M=\left\lfloor100(10f-H)\right\rfloor, \]

\[ S=100\left(100(10f-H)-M\right). \]

Assuming the conventional 86,400-second day, one decimal hour is 8,640 s = 2 h 24 min, one decimal minute is 86.4 s, and one decimal second is 0.864 s. Conversely, conventional seconds after the chosen boundary map to 100,000t/86,400 decimal seconds.

At conventional 13:00:00, t=46,800 s and f=13/24=0.541666.... The decimal clock reads approximately 5:41:66.67. At decimal 5:00:00, f=0.5, so the conventional time is noon. These calculations depend on a fixed 86,400-second day and midnight boundary; changing either changes the conversion.

The endpoint is a convention. f=1 is identical as an instant to f=0 on the next labeled day. A display may allow 10:00:00 to name the just-completed day's endpoint, or normalize it immediately to next-day 0:00:00, but it must not treat both as different instants.

Knowledge Transfer¶

The full role system transfers literally across decimal dials, written Republican hours, hundred-part day instruments, fractional-day coordinates, and normalized software clocks. Each case has a temporal whole, an origin, a radix-ten partition, a numeral, and a decoding rule. What differs is whether the hierarchy is complete, which time scale underlies it, and whether the coordinate resets daily or is joined to a continuous day count.

The arithmetic transfers directly to interface and data design. Normalize elapsed time, choose decimal field widths, define precision, implement carries, and test round-trip conversion at midnight, noon, the day endpoint, and rounding boundaries. Historical adoption evidence transfers a second lesson: computational regularity does not by itself overcome network effects, installed clocks, linguistic habit, scheduling customs, or incompatibility with neighboring systems.^[2]^[3]

Outside timekeeping, base-ten currency, metric length units, and percentage scales are analogues. Their portable residue belongs to Decimal, Representation, and Standardization. Calling them decimal time would erase the day anchor and time-of-day semantics.

Examples¶

French Republican clock. The legal design divides midnight-to-midnight into ten hours, each into one hundred minutes, each minute into one hundred seconds.^[1] The day fraction 0.375 is 3.75 decimal hours, 375 decimal minutes, or 37,500 decimal seconds; a fielded display is 3:75:00.

Conventional-to-decimal conversion. 18:00 conventional time is three quarters through an 86,400-second day. Thus f=0.75, giving 7.5 decimal hours and the fielded decimal time 7:50:00.

Fractional Julian date. Julian date appends a decimal fraction to a continuous day number and uses a noon boundary; 0h UT corresponds to fractional part 0.5.^[5] This preserves the normalized-day relation, but it is not a ten-hour civil-clock hierarchy. It is a related partial decimal-time coordinate.

Hundred-ke day. Ancient Chinese time law divided the day into one hundred marked parts and coexisted with duodecimal and instrument-specific systems.^[4] It illustrates top-level decimal division without licensing a claim that every historical subunit was always decimal.

Non-example—decimal payroll hours. A work interval from 09:00 to 16:30 is 7.5 conventional hours. This simplifies duration accounting, but 09:00 and 16:30 remain 24/60 clock readings. No decimal day or complete time-of-day hierarchy has been adopted.

Non-example—epoch seconds printed in base ten. 1720000000 may be a Unix-style second count. Its glyph radix does not specify its epoch, time scale, civil conversion, or intraday partition, so it is not decimal time merely because the integer is decimal.

Structural Tensions¶

Arithmetic coherence versus coordination cost. Base-ten fields simplify conversion, but time has unusually strong network effects: clocks, timetables, speech, law, work routines, astronomy, and international exchange must agree. The French failure shows that local elegance can lose to transition cost and interoperability.^[2]

Decimal purity versus partial adoption. Decimal fractions of seconds, hours, and days are common precisely because they can coexist with 24/60/60. Hybrids capture some computational value but sacrifice the one-numeral hierarchy that defines the full design.

Radix convenience versus divisibility. Ten divides cleanly by two and five; sixty divides cleanly by two, three, four, five, six, ten, twelve, fifteen, twenty, and thirty. Decimal time favors positional arithmetic while conventional subunits favor many common fractions.

Uniform day versus astronomical and civil reality. A fixed 86,400-second day makes conversion simple; apparent solar days vary, UTC can carry leap-second issues, and local civil time has zone transitions. The representation must state which complexity it abstracts away.

Display simplicity versus semantic metadata. A value such as 0.5 is compact but cannot reveal whether the origin is midnight or noon, whether the scale is UT1, UTC, TT, or local time, or which date it belongs to. Metadata remains part of correctness.

Endpoint clarity versus convenient notation. 10:00:00 may be intuitive as the end of a decimal day, yet it coincides with next-day zero. Systems must choose normalization rules that prevent double labeling and sorting errors.

Structural–Framed Character¶

Decimal Time is a structural–framed abstraction. Its normalized fraction, powers-of-ten hierarchy, conversion formulas, field carries, and round-trip tests are formal and falsifiable. The core can be implemented in a clock or program without adopting the ideology of any historical reform.

Its frame is nevertheless substantial. A “day” needs a boundary, locality, underlying time scale, and legal or scientific convention. Unit names and public meanings are institutional; clocks coordinate people only when communities share them. The French case also attached decimal time to revolutionary rationalization, while other cultures and technical communities embedded decimal divisions in different practices. The node should explain those frames without defining decimal time by one political project.

Structural Core vs. Domain Accent¶

The structural core is whole interval + origin + normalized fraction + radix-ten subdivision + reversible representation. Decimal supplies power-of-ten positional structure; Representation supplies target, medium, mapping, interpretation, and operations; Standardization explains the adoption problem.

The domain accent supplies the day, time-of-day origin, clock fields, temporal units, civil or astronomical time scale, date rollover, clock or table carrier, leap and zone boundary conditions, and scheduling interoperability. Those commitments are not entailed by Decimal or Representation alone. A decimal numeral need not denote time; a time representation need not be decimal; standardization can converge on any radix. The conjunction becomes autonomous because it licenses a specific conversion algebra, interface, failure analysis, and institutional migration problem.

Decimal Time strictly specializes live Representation. It maps instants or elapsed fractions within a declared day onto a radix-ten numeral or clock medium under a decoding convention, with operations on the numeral corresponding to rescaling and comparison of time. Representation is the minimal taxonomic parent.

Time is the target dimension, not the parent kind: a notation system is not a subtype of time itself. Workspace-accepted Decimal supplies the numeral system and power-of-ten place values, but Decimal Time is not a numeral system in general and can use fielded clock notation. Measurement becomes relevant when an instrument observes or realizes time, yet a written conversion scheme can exist without performing a new measurement. Standardization explains public adoption and interoperability but is a process acting on the system, not its genus. Ratio and Scale explain day fractions and unit relations without defining the intraday representation.

Relationships to Other Abstractions¶

Current abstraction Decimal Time Domain-specific

Parents (1) — more general patterns this builds on

Decimal Time is a kind of Representation Prime

Decimal Time strictly specializes live Representation.

Hierarchy path (1) — routes to 1 parentless root

Decimal Time → Representation → Abstraction

Neighborhood in Abstraction Space¶

Decimal Time sits in a sparse region of the domain-specific corpus (98^th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (1565 abstractions)

Nearest neighbors

Superpartient Ratio — 0.76
Decimal — 0.75
Haversine Formula — 0.75
Distributive Case — 0.74
Wiechel Projection — 0.74

Computed from structural-signature embeddings · 2026-09-08

Not to Be Confused With¶

French Republican decimal time: the canonical historical implementation, not the entire abstraction.
French Republican calendar: a date-and-civic calendar containing an intraday reform as one component.
Decimal calendar: decimal or regularized divisions of weeks, months, or years, which need not decimalize the day.
Metric time: use of the SI second and decimal prefixes; it does not by itself create a decimal civil day.
Decimal hour: a conventional hour expressed with a decimal fraction, often for payroll or duration calculation.
Fractional day / Julian date: a decimal day coordinate, commonly joined to a continuous day count and a specified astronomical time scale; related but not automatically a ten-hour clock.
Internet Time / beat time: a particular branded or proposed thousand-part-day system; one decimal-time design, not an alias for all decimal time.
Unix time: a count of seconds from an epoch, independent of the glyph radix used to print it.
ISO 8601 time: standardized 24-hour clock notation with conventional hour, minute, and second fields.
Binary or hexadecimal time: alternative radix-based time representations whose unit partitions are not powers of ten.

References¶

[1] Assemblée nationale. “24 novembre 1793 — Convention nationale et calendrier républicain.” Official historical account of the Convention's decimal calendar and ten-hour, hundred-minute, hundred-second day. registry ↩a ↩b ↩c

[2] Vera, H. (2009). “Decimal Time: Misadventures of a Revolutionary Idea, 1793–2008.” KronoScope, 9(1–2), 29–48. Traces decimal time as a rationalizing metrological project, its implementations, later proposals, and failure to achieve broad adoption. registry ↩a ↩b ↩c

[3] Turner, A. (2022). “Decimal Time.” In A. Turner, J. Betts, & J. Nye (eds.), A General History of Horology, pp. 341–346. Oxford University Press. Authoritative horological history of proposals, French implementation, instruments, later reform efforts, and scientific decimal subdivisions. registry ↩a ↩b ↩c

[4] Yan, H.-S., & Lin, T.-Y. (2002). “A study on ancient Chinese time laws and the time-telling system of Su Song's clock tower.” Mechanism and Machine Theory, 37(1), 15–33. Documents coexistence and instrumentation of decimal, duodecimal, and clepsydra time laws. registry ↩a ↩b ↩c

[5] United States Naval Observatory. “Julian Date Converter” and Astronomical Almanac glossary, checked 2026-08-28. Defines Julian date as a continuous count of days and fractions from a noon origin and requires an underlying time scale in precise work. registry ↩a ↩b ↩c

[6] International Organization for Standardization. ISO 8601-1:2019, Date and time — Representations for information interchange — Part 1: Basic rules, confirmed 2024. Specifies character representations based on the 24-hour clock, providing the principal standard boundary. registry ↩

[7] Bureau International des Poids and Measures. (2026). The International System of Units (SI Brochure), 9^th ed., version 4.01. Defines the SI second and lists minute, hour, and day conversions as 60 s, 3600 s, and 86,400 s. registry ↩a ↩b