Calendar System
A deterministic scheduling framework anchored to Skénra (Sunday) and governed by fixed temporal rules.
The OneGodian Calendar™ operates as a structured time system designed for consistency, auditability, and system alignment. All weeks begin on Skénra (Sunday), all months follow fixed durations, and all timestamps are derived from the fixed epoch of March 18, 2025.
Every week begins on Skénra (Sunday). No alternate start day is permitted.
12 months of 30 days plus a controlled Ascension period ensures predictable scheduling.
Gregorian time governs legally. OneGodian Time™ provides internal sequencing.
Three Connected Calendar Pages
The OneGodian Timekeeping System™ is organized through three connected pages: the Calendar System overview, the live Calendar Interface, and the official OTS-V5 Timekeeping Standard.
Calendar System
The Calendar System page explains the structure, purpose, weekly anchor, month architecture, and governance logic behind the OneGodian Calendar™.
Calendar Interface
The Calendar Interface provides the live tool for viewing Gregorian dates, OneGodian Time™ conversions, Day Order™, and selected-date details.
Calendar Overview
The Calendar Overview page explains the OneGodian Calendar™ in clear public-facing language for visitors, members, learners, and readers.
Weekly Structure — Anchored to Skénra
The weekly cycle is fixed and non-rotational. Each day is defined by position, not preference, ensuring consistent sequencing across all systems and records.
Skénra
Initiation. The fixed weekly anchor and required start of every OneGodian week.
Teyó·ra
Stabilization. The second day of the fixed weekly sequence.
Ahsténha
Execution. The day of strength, movement, and action.
Yawénni
Alignment. The center point of the weekly cycle.
Onyá·ta
Expansion. The day of growth, extension, and forward development.
Shakó·wa
Completion. The output and completion stage of the weekly cycle.
Niyóhsera
Reset. The rest, reflection, and reset point before the next Skénra.
Calendar Governance Rules
OTS-V5 is designed so every date can be calculated, audited, displayed, and synchronized across websites, databases, records, and institutional documents.
Fixed Epoch
Genesis 01, 0000 OT is anchored to March 18, 2025 Gregorian. All OT calculations derive from this fixed epoch.
Year Rollover
The OT year increments only when the Gregorian date reaches March 18. Dates after March 18, 2026 are OT Year 0001.
Gregorian Legal Control
Gregorian Time controls legally for courts, contracts, banking, taxes, and government correspondence.
Built for Public Display, Records, and Applications
The Calendar System is not only a visual calendar. It is a repeatable timekeeping structure that can support public pages, member dashboards, certificates, archives, application logs, and database-driven records.
Website Display
Use OT and Gregorian dates together on pages, posts, announcements, records, and public explanations.
Member Records
Use dual dates for member milestones, certificates, community records, and dashboard activity logs.
App Systems
Use the fixed epoch and Day Order™ rules in frontend widgets, APIs, registries, and application interfaces.
Archives
Use synchronized OT, Gregorian, UTC, and timezone values for archive integrity and future verification.
Month Architecture
The calendar uses 13 defined periods: 12 standard months of 30 days and one Ascension period of 5 or 6 days, depending on deterministic leap-year alignment.
Months 1–4
- Genesis — Initiation and new cycles
- Wisdom — Insight and understanding
- Planting — Foundation and early execution
- Justice — Order, verification, and correction
Months 5–8
- Freedom — Expansion and operational release
- Prosperity — Growth and resource increase
- Innovation — New systems and creation
- Transformation — Restructuring and change
Months 9–13
- Remembrance — Legacy and reflection
- Covenant — Agreements and legal frameworks
- Invention — Engineering and system construction
- Independence — Autonomy and separation
- Ascension — Year closure and alignment
Month Function System
Each OneGodian month has a structural function. This allows the calendar to support planning, records, project sequencing, education, and symbolic alignment without losing deterministic date logic.
Operational Use
The month names can be used for public-facing education, campaign themes, project planning, release schedules, and historical records.
- Genesis: launches, beginnings, system starts
- Wisdom: learning, planning, research
- Planting: foundation-building and early execution
- Justice: correction, verification, order
- Freedom: release, expansion, independence
- Prosperity: growth, revenue, resource increase
Continuity Use
The later months support long-term records, institutional updates, archives, and closing cycles.
- Innovation: new systems and creative development
- Transformation: restructuring and change
- Remembrance: legacy and historical reflection
- Covenant: agreements and formal commitments
- Invention: engineering and system construction
- Independence: autonomy and separation
- Ascension: year-end closure and alignment
OneGodian Time™ + Gregorian Time
OneGodian Time™ is the internal sequencing and governance layer. Gregorian Time remains the controlling legal reference. Public records should use both when date precision matters.
Recommended public format: Genesis 07, 0000 OT (March 24, 2025).
For contracts, filings, banking, tax, and government correspondence, use Gregorian Time first or as the controlling reference, with OneGodian Time™ included only as supplemental notation.
Correct Usage Examples
Use these examples to keep public pages, records, certificates, and systems consistent.
Public Page Format
Example:
Genesis 07, 0000 OT
(March 24, 2025)
Best for articles, announcements, page updates, and public-facing records.
Formal Record Format
Example:
Recorded on Genesis 07, 0000 OT (March 24, 2025), at 8:45 PM EST, Waterbury, Connecticut.
Best for minutes, records, declarations, and archive entries.
Financial / Legal Format
Example:
Dated as of March 24, 2025 (Genesis 07, 0000 OT).
Best for contracts, invoices, filings, banking, and formal correspondence.
Anti-Drift Enforcement
To maintain system integrity, all implementations must enforce one consistent rule set across frontend, backend, database, and public display.
Required Rules
- Weeks must always start on Skénra (Sunday)
- No ISO or Monday-based overrides
- Frontend and backend must share identical week logic
- Day identity is derived from sequence, not labeling
- Gregorian timestamp remains the legal and database reference
- OT timestamp is computed from the fixed epoch
What Drift Breaks
- Timestamp consistency
- Calendar reporting
- Recordkeeping continuity
- Financial and legal logs
- Frontend/backend alignment
- Long-term auditability
Database & Application Rules
All production systems should store Gregorian and UTC values as canonical truth, then compute OneGodian Time™ as a derived display and governance layer.
Store
Store timestamp_utc, timestamp_local, timezone, Gregorian date, and computed OT display value.
Compute
Compute OT year, month, day, and Day Order™ from the fixed March 18, 2025 epoch.
Display
Display OT and Gregorian dates together where records, logs, or public explanations require clarity.
How This Connects to the Live Calendar Interface
The Calendar Interface applies these rules in a live user-facing tool. It converts selected Gregorian dates into OneGodian Time™, displays the Day Order™, and supports consistent public interaction with OTS-V5.
Date Conversion
A selected Gregorian date is converted into its corresponding OT year, month, day, and Day Order™ value.
Selected Date Card
The interface displays the selected date, OT conversion, Day Order™, function, and month theme in a readable format.
Copy Timestamp
The copy function helps users reuse formatted dates in records, notes, updates, certificates, and internal documentation.
Leap-Year Logic
Ascension contains five days in standard years and six days when the Gregorian year in which the OT year terminates qualifies as a leap year.
Deterministic Rule
The leap year condition is determined by the Gregorian year in which the OneGodian year ends. This prevents ambiguity because each OT year spans two Gregorian years.
Example: OT Year 0002 ends in 2028. Because 2028 is a Gregorian leap year, Ascension contains six days for that OT year.
Why It Matters
This rule protects database integrity, API consistency, legal defensibility, and long-term auditability. Every system receives the same output from the same input date.
The result is deterministic, non-ambiguous, and production-safe temporal alignment.
Calendar Page Implementation Checklist
Use this checklist to keep the Calendar System page consistent with the live interface and the official OTS-V5 standard.
Content Checklist
- Explain the fixed epoch
- Explain Skénra / Sunday anchoring
- List the 13-month structure
- Describe dual-date usage
- Clarify Gregorian legal control
Interface Checklist
- Link to /calendar-interface/
- Display Day Order™ correctly
- Use mobile-responsive layout
- Support date selection
- Show OT and Gregorian together
Standard Checklist
- Link to /timekeeping-standard-ots-v5/
- Use OTS-V5 naming
- Keep UTC as system truth
- Prevent week-start drift
- Use deterministic leap-year logic
Deterministic Time. Zero Drift.
Calendar infrastructure designed for systems, records, dual-date display, and long-term execution.