IST, Local Civil Time, and Operational Time — the three-layer temporal system of the Imperium
This document establishes the official framework by which time is defined, recorded, and coordinated across the territories of the Awen Concordia Imperium.
It addresses the necessity of unified temporal reference while acknowledging the practical requirements of local environments, human perception, and cultural continuity.
The Imperium does not impose a single lived rhythm of time. It provides a shared temporal language.
The Imperium recognises three coexisting temporal layers, each serving a distinct and non-interchangeable function. All three are valid. None is sufficient on its own.
| System | Purpose | Scope |
|---|---|---|
| Imperial Standard Time (IST) | Universal reference | Interstellar / Legal |
| Local Civil Time (LCT) | Lived daily rhythm | Within local environment |
| Operational Time (OPT) | Task / mission rhythm | Duration of operation |
Imperial Standard Time serves as the absolute temporal reference for all interstellar coordination. It is a continuous, linear time index — independent of planetary rotation, orbital cycles, or biological rhythms — maintained by synchronised atomic reference arrays across Core systems.
IST is used exclusively for:
IST is not intended for daily civil use. It is the reference, not the experience.
On the IST Epoch
The IST count is continuous, inheriting the accumulated year count of human civilisation. The epoch is not the founding of the Imperium — the Imperium does not own the clock. IST 0001 predates the Imperium by several centuries. The Imperium standardised and enforced the system; it did not create the count.
This means all human history — pre-Imperial colonial records, Earth-bound archives, and post-founding documentation — exists on a single unbroken numerical axis. A document dated IST 2487 requires no conversion, no epoch translation, no disambiguation.
Local Civil Time governs daily life within a specific environment — planetary surfaces, stations, habitats, and long-duration vessels. It is derived from planetary rotation where applicable, or from administratively defined cycle schedules on stations and ships.
LCT may vary significantly between locations and is not standardised across the Imperium. Cycle length, interval count, and cultural observances are all permitted to differ.
Usage domains: work schedules, education, civic services, social coordination.
Examples: “Markets open mid-cycle.” — “School begins two intervals after wake.”
Local Civil Time is valid only within its environment and must never be used for interstellar coordination or legal reference beyond its jurisdiction.
Operational Time governs task-bound, mission-specific, and system-critical activities. OPT is purpose-defined, context-limited, and often temporary. Operational Time may override Local Civil Time for the duration of an operation but does not replace it permanently.
Typical applications include spaceflight operations, docking windows, emergency response, industrial processes, and military and rescue missions.
Operational Time is anchored to mission start — designated Zero Interval — and expressed in intervals and cycles counted forward from that point. It may compress or extend cycles artificially as operational requirements demand.
Examples: “Docking window: OPT +4 int” — “Extraction phase ends at OPT cycle 3” — “We are running on op-time until recovery.”
Operational Time exists to remove ambiguity under pressure.
To bridge the gap between abstract standard time and lived human experience, the Imperium recognises three operational units. These units are relational and scalable, allowing local adaptation while remaining interoperable.
| Unit | Shorthand | Spoken Forms | Quantity / Role |
|---|---|---|---|
| Passage | psg / P | long, arc, season, year | 360 cycles — planning & historical scale |
| Cycle | cy / C | turn, day, shift, wake | 24 intervals — primary lived rhythm |
| Interval | int / iv | tick, bit, moment | 1/24 of a cycle — task & operational scale |
The Passage
The Passage is the large-scale unit — 360 cycles in length. It replaces the pre-Imperial concept of the year while retaining intuitive human scale. Passages serve planning horizons, life phases, and long-term institutional continuity.
The figure of 360 cycles was selected deliberately: it divides cleanly into halves, thirds, quarters, sixths, and eighths, making administrative scheduling, charter review periods, and contract durations naturally expressible without fractional cycles.
360 cycles is not tied to any planetary orbital period. Its value is mathematical convenience, not astronomical coincidence.
The Cycle
The Cycle is the primary lived rhythm — divided into 24 intervals. It replaces the pre-Imperial concept of the day. On planetary surfaces, a cycle typically aligns with local rotation. On stations and vessels, cycles are administratively defined to support crew health and operational stability.
The division of 24 intervals was retained from pre-Imperial human timekeeping, not for precision, but for cognitive continuity. The Imperium does not erase these inheritances — it renders them interoperable.
The Interval
The Interval is the short, task-scale unit — one twenty-fourth of a cycle. It is used for immediate activities, coordination windows, and operational scheduling. Intervals are context-dependent and not required to align across environments. Their purpose is functional clarity, not universal precision.
A full IST timestamp is expressed as:
IST [Passage].[Cycle].[Interval]
Example: IST 2487.214.09 — Passage 2487, Cycle 214, Interval 9.
For document headers and legal records, cycle-level precision is standard: IST 2487.214. Interval-level precision is reserved for operational logs, navigation records, and incident reports where sub-cycle timing is material.
A single recorded event may carry all three temporal references simultaneously. Each answers a different question and serves a different reader.
Recorded Event: Docking incident, Kepler Station Approach
| Reference | Value | Question Answered |
|---|---|---|
| IST | 2471.088.17 | When did it happen universally? |
| Local Civil Time | Late cycle, pre-rest interval | How did it affect people locally? |
| Operational Time | OPT +17 int | What failed operationally? |
Translation between temporal layers is mandatory for navigation, legal documentation, logistics, and archival recordkeeping. Failure to translate correctly is treated as procedural error, not cultural deviation.
No single unit is sufficient on its own:
Prior to unification, humanity maintained thousands of incompatible time systems based on local rotation, orbit, and cultural tradition. This fragmentation produced logistical inefficiency, legal ambiguity, and coordination failure at scale.
The Imperial framework does not erase these histories. It renders them interoperable. Local systems remain valid within their domains. The IST count simply ensures that any two records, from any two worlds, can be placed on the same axis without negotiation.
“Time is local. Consequence is not.”