Timekeeping Standard
The official OTS-V5 framework for dual dating, timestamp governance, calendar conversion, legal clarity, and deterministic OneGodian Time™ alignment.
Overview
The OneGodian Timekeeping System™ — OTS-V5 is a dual-dating and timestamp governance framework. It uses OneGodian Time™ as an internal sequencing layer while preserving Gregorian Time as the controlling civil, legal, financial, and institutional reference.
Purpose of OTS-V5
OTS-V5 exists to make OneGodian Time™ consistent, auditable, and interoperable with ordinary legal and institutional systems.
The system provides a fixed epoch, defined year rollover, deterministic month lengths, Day Order™ rules, dual-date formatting, and database governance standards.
It is designed for websites, dashboards, certificates, records, archives, applications, APIs, logs, and formal documentation where OneGodian Time™ is used alongside Gregorian Time.
Non-Negotiable Timekeeping Rules
These rules keep OneGodian Time™ consistent across public pages, databases, documents, records, and institutional communications.
Gregorian Controls Legally
Gregorian Time remains controlling for courts, contracts, banking, taxes, and government correspondence.
OT Is Supplemental
OneGodian Time™ is an internal sequencing, governance, archive, and display layer derived from Gregorian and UTC time.
UTC Is System Truth
Databases should store UTC and Gregorian timestamps as canonical values, then compute OT values from them.
Epoch and Year Mapping
OTS-V5 is anchored to a fixed epoch: Genesis 01, 0000 OT equals March 18, 2025 Gregorian. The OT year increments only when the Gregorian date reaches March 18.
Correct Year Mapping
- Genesis 01, 0000 OT = March 18, 2025
- OT Year 0000 spans March 18, 2025 through March 17, 2026
- Genesis 01, 0001 OT = March 18, 2026
- OT Year 0001 begins March 18, 2026
Key Rule
The OneGodian year changes only on March 18 Gregorian.
Any date on or after March 18, 2026 belongs to OT Year 0001, not OT Year 0000.
This rule protects chronological integrity and prevents year-drift in records, dashboards, and applications.
Official Public Date Format
The standard public format places the OneGodian date first, followed by the Gregorian date in parentheses.
For financial instruments, contracts, filings, tax documents, banking documents, and government correspondence, Gregorian Time should be used as the controlling reference, with OT included only as supplemental notation.
Full Timestamp Standard
Use full timestamps for time-sensitive records, governance logs, certificates, digital archives, system events, and formal records.
Formal Record Format
Example:
Recorded on Genesis 07, 0000 OT (March 24, 2025), at 8:45 PM EST, Waterbury, Connecticut.
This format preserves OT identity while retaining civil readability and legal interoperability.
Database Format
- timestamp_utc — primary system truth
- timestamp_local — local time display
- timestamp_ot — computed OneGodian Time™ value
- timezone — required for clarity
- gregorian_date — controlling civil date
13-Month Temporal Structure
The OneGodian year contains twelve 30-day months plus Ascension, a 5- or 6-day year-end alignment period.
Months 1–12
Genesis through Independence each contain 30 days for predictable monthly sequencing and system alignment.
Ascension
Ascension closes the year and functions as the controlled alignment period before the next Genesis cycle.
Year Length
A standard OT year contains 365 days. Leap-aligned years contain 366 days through a 6-day Ascension period.
Day Order™ Standard
The weekly cycle is fixed, non-rotational, and anchored to Skénra, which corresponds to Sunday in Gregorian synchronization.
Skénra
Day 1: Initiation. The fixed start of each week.
Teyó·ra
Day 2: Balance and stabilization.
Ahsténha
Day 3: Strength and execution.
Yawénni
Day 4: Center and alignment.
Onyá·ta
Day 5: Expansion and growth.
Shakó·wa
Day 6: Completion and output.
Niyóhsera
Day 7: Rest, reset, and cycle closure.
Deterministic Ascension Rule
Leap-year determination within OTS-V5 is governed by the Gregorian year in which the OneGodian year terminates.
If the corresponding Gregorian end year qualifies as a leap year, Ascension contains six days. Otherwise, Ascension contains five days.
Anti-Drift Enforcement
All systems must apply the same weekly anchor, epoch, year rollover, and conversion logic. No Monday-start or ISO-week override should replace the internal OTS-V5 sequence.
Required Enforcement
- Every week begins on Skénra / Sunday
- Day identity is derived from fixed sequence
- OT year rollover occurs on March 18
- UTC and Gregorian timestamps remain canonical
- OT date is computed, not manually assigned
What This Prevents
- Timestamp drift
- Broken calendar grids
- Frontend/backend mismatch
- Inconsistent reporting periods
- Legal and archival ambiguity
Legal Interoperability
The OneGodian Timekeeping System™ operates as a dual-dating framework in which OneGodian Time™ serves as the internal sequencing and governance layer, while Gregorian Time remains the controlling legal reference for all civil, financial, and institutional purposes.
All records, timestamps, and system logs should maintain synchronized OT and Gregorian representations derived from the fixed epoch of March 18, 2025, ensuring determinism, auditability, and legal interoperability.
Implementation Checklist
Use this checklist when implementing OTS-V5 in websites, plugins, apps, dashboards, registries, certificates, archives, or databases.
Frontend
- Render week starting with Skénra / Sunday
- Show OT and Gregorian dates together
- Label Day Order™ clearly
- Do not allow internal week-start overrides
Backend
- Store UTC as primary truth
- Compute OT from Gregorian/UTC
- Use fixed epoch: March 18, 2025
- Apply deterministic leap-year rule
Records
- Use dual-date display
- Include timezone when time-sensitive
- Preserve Gregorian legal reference
- Use OT for internal sequence and archive identity
Use the Timekeeping Standard Correctly
Use Gregorian Time for legal control, UTC for system truth, and OneGodian Time™ as the supplemental internal sequencing and governance layer.