{ "schema_version": 1, "last_updated": "2026-05-15", "status_definitions": { "implemented": "Real implementation exists in the app and returns structured output.", "planned": "Tracked in the roadmap/backlog, but not yet present in the app. Human-readable surfaces may show some planned entries as deferred on purpose when the notes make that explicit.", "research_required": "Tracked, but blocked on observational, scholarly, provider, or source-reconciliation work rather than simple sequencing.", "not_standalone": "Tracked as an overlay, naming layer, meta-unit, or edge case rather than as an independent calendar." }, "kind_definitions": { "calendar": "Independent calendar projection system.", "time_scale": "Time scale or clock/time-of-day system.", "serial": "Continuous or encoded serial/numeric time representation.", "era": "Year-era layer that rides on a base calendar.", "overlay": "Observance, ritual, fiscal, or other layer projected on a base calendar.", "cycle": "Cycle system that may or may not be a full date calendar.", "naming_layer": "Month/season/vocabulary layer over a base date structure.", "observational_framework": "System family that needs observational or scholarly infrastructure first.", "meta_unit": "Chronological framework, relative dating, or other non-calendar temporal unit." }, "notes": [ "This file is the source of truth for the roadmap-style backlog of systems the project wants to track explicitly.", "Some user-proposed items were intentionally consolidated. For example, Greek parapegmata and parapegma calendars are tracked together, and regnal-year overlay is tracked once as a full overlay family.", "The backlog is broader than the currently implemented system kinds; it also tracks observational frameworks and meta-units so they are not lost." ], "entries": [ { "key": "liturgical_calendars", "display_name": "Liturgical Calendars", "kind": "overlay", "status": "implemented", "track": "orthodox_liturgical", "notes": "Orthodox-first provider-backed v1 exists with world_orthodox and russian_orthodox profiles." }, { "key": "catholic_liturgical_year", "display_name": "Catholic Liturgical Year", "kind": "overlay", "status": "implemented", "track": "catholic_liturgical", "notes": "Implemented as a Roman-rite Catholic overlay with General Roman and jurisdiction-style profiles, using the romcal provider engine for seasons and major moveable observances plus curated major fixed-feast support. This is the closest current analogue to the Orthodox/Ponomar path, though not a one-to-one upstream equivalent." }, { "key": "ecclesiastical_computus", "display_name": "Ecclesiastical Computus", "kind": "overlay", "status": "implemented", "track": "orthodox_liturgical", "notes": "Gregorian/Julian Pascha comparison base is live; deeper liturgical linkage still planned." }, { "key": "wheel_of_the_year", "display_name": "Wheel of the Year", "kind": "overlay", "status": "implemented", "track": "cultural_overlays", "notes": "Current implementation is fixed-date civil overlay only." }, { "key": "hebrew_civil_religious", "display_name": "Hebrew Civil Year vs. Religious Year", "kind": "overlay", "status": "implemented", "track": "overlay_profile_validators", "notes": "Real convention/profile overlay on top of Hebrew." }, { "key": "jewish_liturgical_calendar", "display_name": "Jewish Liturgical Calendar", "kind": "overlay", "status": "implemented", "track": "jewish_liturgical", "notes": "Implemented as a locality-aware Jewish observance overlay with provider-backed Hebrew date, holidays, Omer, parasha, Daf Yomi, and zmanim support, plus curated daily-reading and study-cycle structure. This is intentionally distinct from the lighter `hebrew_civil_religious` convention overlay." }, { "key": "soviet_calendar", "display_name": "Soviet Calendar", "kind": "overlay", "status": "implemented", "track": "historical_reform_overlays", "notes": "Implemented as a historical overlay over Gregorian civil dating rather than as a replacement calendar. V1 models the pyatidnevka and shestidnevka work-week experiments, the restoration of the seven-day week, the native reform window, and the major Soviet state holidays, while explicitly not inferring worker-specific five-day rest assignments from date alone." }, { "key": "kali_yuga", "display_name": "Kali Yuga Era", "kind": "era", "status": "implemented", "track": "era_validators", "notes": "Implemented as a pinned civil-era layer on Gregorian." }, { "key": "vikram_samvat", "display_name": "Vikram Samvat", "kind": "era", "status": "implemented", "track": "era_validators", "notes": "Current implementation is a civil-era projection, not the full regional/lunisolar family." }, { "key": "macedonian_months", "display_name": "Macedonian Months", "kind": "naming_layer", "status": "implemented", "track": "naming_layer_validators" }, { "key": "sotho_months", "display_name": "Sotho Months", "kind": "naming_layer", "status": "implemented", "track": "naming_layer_validators" }, { "key": "pawukon", "display_name": "Pawukon Calendar", "kind": "cycle", "status": "implemented", "track": "cycle_validators", "notes": "Implemented as a real cycle projection with honest no-parse policy. This already covers the Balinese wewaran family of overlapping week cycles, including one-day through ten-day week structures." }, { "key": "advent_calendar", "display_name": "Advent Calendar", "kind": "cycle", "status": "implemented", "track": "cycle_validators", "notes": "Implemented as a fixed annual 24-day countdown cycle anchored to December 1. It is intentionally separate from the Orthodox-first `liturgical_calendars` overlay: this entry models the modern Advent countdown practice itself, not the broader Christian liturgical season." }, { "key": "tonalpohualli", "display_name": "Tōnalpōhualli", "kind": "cycle", "status": "implemented", "track": "cycle_validators" }, { "key": "xiuhpohualli", "display_name": "Xiuhpōhualli", "kind": "cycle", "status": "implemented", "track": "cycle_validators" }, { "key": "discordian", "display_name": "Discordian Calendar", "kind": "calendar", "status": "implemented", "track": "real_calendar_replacements" }, { "key": "gregorian", "display_name": "Gregorian Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented core civil calendar; included here so the Wikipedia calendar list has an explicit backlog/reference row." }, { "key": "julian", "display_name": "Julian Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented core Julian calendar projection." }, { "key": "hebrew", "display_name": "Hebrew/Jewish Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as the app's Hebrew calendar; the separate `hebrew_civil_religious` entry tracks civil/religious-year overlay semantics." }, { "key": "chinese_lunar", "display_name": "Chinese Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented Chinese lunar/lunisolar calendar surface; historical named Chinese calendars remain tracked separately where they need profile-level reconstruction." }, { "key": "coptic", "display_name": "Coptic Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a Coptic-family calendar projection." }, { "key": "armenian", "display_name": "Armenian Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as an Armenian calendar projection." }, { "key": "islamic", "display_name": "Islamic Calendar / Lunar Hijri Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented generic Islamic calendar path; provider/authority-specific work is tracked separately by `umm_al_qura` and `islamic_regional_moon_sighting`." }, { "key": "indian", "display_name": "Indian National Calendar (Saka)", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as the Indian national/Saka calendar." }, { "key": "burmese", "display_name": "Burmese Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as the app's Burmese calendar projection." }, { "key": "persian", "display_name": "Solar Hijri / Persian Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented public Persian/Solar Hijri surface; `jalali` and `persian_algorithmic` track related Persian-family distinctions." }, { "key": "mayan", "display_name": "Maya Long Count", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as the app's Mayan Long Count surface." }, { "key": "french_republican", "display_name": "French Republican Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a bounded French Republican calendar projection." }, { "key": "byzantine", "display_name": "Byzantine Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a Byzantine Anno Mundi surface over Julian calendar structure." }, { "key": "bahai", "display_name": "Badíʿ / Baháʼí Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as the app's Baháʼí calendar surface." }, { "key": "thai_solar", "display_name": "Thai Solar Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as Thai solar/Buddhist Era civil projection." }, { "key": "ifc", "display_name": "International Fixed Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as the International Fixed Calendar." }, { "key": "pax", "display_name": "Pax Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a leap-week reform calendar." }, { "key": "positivist", "display_name": "Positivist Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a Gregorian-derived reform calendar." }, { "key": "pataphysical", "display_name": "Pataphysical Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as the app's Pataphysical calendar projection." }, { "key": "assyrian", "display_name": "Assyrian Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as the modern Assyrian calendar projection." }, { "key": "dreamspell", "display_name": "Dreamspell Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a Dreamspell/13 Moon style projection." }, { "key": "holocene", "display_name": "Holocene Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as Gregorian structure with Holocene era numbering." }, { "key": "juche", "display_name": "Juche Era Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as Gregorian structure with Juche era numbering." }, { "key": "astronomical", "display_name": "Astronomical Year Numbering", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as the app's astronomical year-numbering surface." }, { "key": "runic", "display_name": "Runic Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a Runic calendar/cycle projection." }, { "key": "hanke_henry", "display_name": "Hanke-Henry Permanent Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a Gregorian-derived leap-week reform calendar." }, { "key": "ethiopian", "display_name": "Ethiopian Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented as an arithmetic Ethiopian calendar projection through the Coptic family offset." }, { "key": "mandaean_calendar", "display_name": "Mandaean Calendar", "kind": "calendar", "status": "implemented", "track": "backlog_only", "notes": "Implemented as a fixed 365-day Mandaean liturgical/cultural solar projection anchored to the published 2019-07-18 Gregorian = 1 Daula 481343 AA correspondence, with Parwanaya exposed honestly and day-boundary limitations documented." }, { "key": "berber", "display_name": "Berber Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in Wave 1 as a modern Amazigh public solar surface with Yennayer on January 14 and a fixed era offset, explicitly not as a survey of every regional Berber reckoning." }, { "key": "egyptian", "display_name": "Egyptian Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in Wave 1 as an Egyptian-family public backbone surface over the Alexandrian/Coptic month structure with Egyptian month labels, not as a full pharaonic or ritual reconstruction." }, { "key": "japanese_many", "display_name": "Japanese Calendar (Many Variants)", "kind": "meta_unit", "status": "not_standalone", "track": "backlog_only", "notes": "Reclassified on purpose as an umbrella/family tracker rather than a plain calendar ticket. The implemented `japanese_traditional` surface plus future reign/era overlays cover the concrete work more honestly than one vague many-variants calendar key." }, { "key": "kurdish", "display_name": "Kurdish Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in Wave 1 as a Kurdish public solar family surface over the current Persian/Jalali arithmetic backbone, with Kurdish era numbering and month labels." }, { "key": "persian_algorithmic", "display_name": "Persian Algorithmic Calendar", "kind": "calendar", "status": "implemented", "track": "backlog_only", "notes": "Implemented as an explicit arithmetic Persian-family public surface over the same convertdate-backed Solar Hijri core already used by the app, so the algorithmic entry is now real and directly comparable." }, { "key": "tripuri", "display_name": "Tripuri Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in the South Asian regional wave as a public Tripuri family surface over the existing Bengali fixed civil approximation, with Tripuri-facing month labels rather than a claim to every Tripuri ritual calendar." }, { "key": "hindu_panchangam", "display_name": "Hindu Traditional Panchangam", "kind": "observational_framework", "status": "implemented", "track": "backlog_only", "notes": "Implemented as a reference-only Panchangam engine contract. Live conversion remains blocked until a locality-aware astronomy/provider layer can compute tithi, nakshatra, yoga, karana, masa, sunrise, and regional conventions.", "sources": [ "docs/old-future/future_ hindu_panchangam.md" ] }, { "key": "jain", "display_name": "Jain Calendar", "kind": "observational_framework", "status": "implemented", "track": "backlog_only", "notes": "Implemented as a reference-only Jain/Panchangam overlay contract tied to Vira Nirvana Samvat, Kartika New Year, and sectarian month-convention requirements. Live conversion awaits the deeper Panchangam engine.", "sources": [ "docs/old-future/future_ jain.md" ] }, { "key": "akan", "display_name": "Akan Calendar", "kind": "observational_framework", "status": "implemented", "track": "phase5_replacements", "notes": "Wave 2 implemented this honestly as a framework-first Akan cycle surface centered on Nnanson, the seven-day week, and Adaduanan timing rather than as a fake normalized month/day converter." }, { "key": "borana", "display_name": "Borana Calendar", "kind": "observational_framework", "status": "implemented", "track": "phase5_replacements", "notes": "Wave 2 implemented this honestly as a lunar-stellar Borana framework with pastoral and locality dependence made explicit rather than as a pinned public month/day converter." }, { "key": "georgian_historical", "display_name": "Georgian Historical Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in the historical-backbone wave as a Georgian historical public surface over Julian civil structure with historical Georgian month labels, not as a full reconstruction of every royal and ecclesiastical Georgian calendrical phase." }, { "key": "hmong", "display_name": "Hmong Calendar", "kind": "observational_framework", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable; live conversion remains blocked pending community/profile-specific source work." }, { "key": "japanese_traditional", "display_name": "Japanese Traditional Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in Wave 4 as a Chinese-family traditional Japanese public surface with wagetsu month names, while broader historical Japanese reform and reign-calendar differentiation remains future work." }, { "key": "melanau", "display_name": "Melanau Calendar", "kind": "observational_framework", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable; live conversion remains blocked pending ethnographic source profiles." }, { "key": "mizo", "display_name": "Mizo Calendar", "kind": "observational_framework", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable; live conversion remains blocked pending ethnographic source profiles." }, { "key": "tirhuta", "display_name": "Tirhuta Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in the South Asian regional wave as a practical April-start Tirhuta/Maithili public surface with regional month labels and Vikram-style year numbering, not as a full Mithila Panchang reconstruction." }, { "key": "tulu", "display_name": "Tulu Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in the South Asian regional wave as a fixed public coastal-Karnataka solar approximation with April New Year and Tulu-facing month labels, not as a full ritual-grade Tulu Panchangam." }, { "key": "xuanming", "display_name": "Xuanming Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in Wave 4 as a historical Chinese-family backbone surface, explicitly not yet a dynasty-specific ephemeris-perfect reconstruction." }, { "key": "igbo", "display_name": "Igbo Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Wave 2 implemented this as a fixed public Nri-oriented surface with 13 x 28-day months plus a year-closing intercalary day and four-day market-cycle labels, while staying honest that historical Igbo communities were not universally synchronized to one absolute-date table." }, { "key": "khmer", "display_name": "Khmer Lunar Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented as a provider-backed Khmer lunar projection using khmerdate; current scope is Gregorian-to-Khmer lunar output with Buddhist year, zodiac year, and stem, not reverse parsing." }, { "key": "meitei", "display_name": "Meitei Calendar", "kind": "observational_framework", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable; live conversion remains blocked pending provider/profile work." }, { "key": "mongolian", "display_name": "Mongolian Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in Wave 4 as a Chinese-family Mongolian public surface so the entry is real and comparable now, while fuller provider-backed almanac differentiation remains future work." }, { "key": "punjabi", "display_name": "Punjabi Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in Wave 1 as a public Punjabi fixed civil surface with April New Year, Punjabi month names, and Vikram-Samvat-style year numbering, not as a full ritual Bikrami or denominational Sikh calendar." }, { "key": "roman", "display_name": "Roman Calendar", "kind": "calendar", "status": "implemented", "track": "backlog_only", "notes": "Implemented in Wave 3 as a Roman imperial/late-classical Julian public surface with AUC year numbering, explicitly not as a full republican pre-Julian reconstruction." }, { "key": "roman_legendary_ten_month_calendar", "display_name": "Roman Legendary 10-Month Calendar", "kind": "observational_framework", "status": "implemented", "track": "historical_reconstructions", "notes": "Implemented as a reference-only antiquarian reconstruction concept. It exposes provenance and blocks live date arithmetic because no secure epoch, continuity model, or native civil-use table exists.", "sources": [ "docs/future_roman_legendary_ten_month_calendar.md" ] }, { "key": "thai_lunar", "display_name": "Thai Lunar Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented as a provider-backed Thai lunar projection using pythaidate's Chulasakarat-era lunisolar model, preserving intercalary month notation such as month 88 and exposing PakDate labels. A separate Thai zodiacal month-naming layer remains tracked independently." }, { "key": "tibetan_notations", "display_name": "Tibetan Calendar Notations", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented as a provider-backed Tibetan projection using caltib, with explicit Phugpa and Tsurphu profiles. Current public scope is Gregorian-to-Tibetan projection with leap-month awareness and notation-oriented labels." }, { "key": "vietnamese", "display_name": "Vietnamese Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in Wave 4 as a provider-backed Vietnamese lunisolar projection using lunar-vn, including Can Chi labels." }, { "key": "sikh_nanakshahi", "display_name": "Sikh Nanakshahi Calendar", "kind": "meta_unit", "status": "not_standalone", "track": "backlog_only", "notes": "Reclassified on purpose as a family/provenance tracker rather than a separate plain-calendar ticket for now. The implemented `nanakshahi` surface covers the concrete current public work until a stricter Sikh/profile split is justified." }, { "key": "nanakshahi", "display_name": "Nanakshahi Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented as a fixed solar Mool/2003-style Nanakshahi projection with March 14 New Year and fixed month starts." }, { "key": "zoroastrian", "display_name": "Zoroastrian Calendar", "kind": "meta_unit", "status": "not_standalone", "track": "backlog_only", "notes": "Reclassified on purpose as an umbrella family tracker rather than a plain calendar ticket. The concrete public work now lives in `zoroastrian_variants` and `fasli`." }, { "key": "zoroastrian_variants", "display_name": "Zoroastrian Calendar Variants", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented with explicit Fasli, Shahanshahi, and Qadimi profiles; Fasli is seasonal while Shahanshahi and Qadimi use pinned drifting arithmetic anchors." }, { "key": "assamese", "display_name": "Assamese Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in Wave 1 as an Assamese public family surface over the already-implemented Bengali fixed civil model, using Assamese month labels rather than claiming a full festival-grade Assamese Panjika." }, { "key": "cappadocian", "display_name": "Cappadocian Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in the historical-backbone wave as a Cappadocian public surface over Julian civil structure with Cappadocian month labels, not as a full Persian-Anatolian reconstruction." }, { "key": "fasli", "display_name": "Fasli Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented as a first-class public surface promoted from the existing seasonal Fasli profile in `zoroastrian_variants`." }, { "key": "icelandic", "display_name": "Icelandic Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in the historical-backbone wave as an old Icelandic public surface over Julian civil structure with traditional month labels, while the more structural misseri system remains separate." }, { "key": "jalali", "display_name": "Jalali Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented as a distinct public Jalali surface over the current arithmetic Persian/Solar Hijri family in the app." }, { "key": "nepal_sambat", "display_name": "Nepal Sambat", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in the South Asian regional wave as a fixed public civil approximation with Nepal Sambat era numbering, Nepal Bhasa month labels, and an explicit November New Year, while deeper lunisolar Newar reconstruction remains future work." }, { "key": "tamil", "display_name": "Tamil Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in the South Asian regional wave as a fixed public Tamil solar approximation with April New Year and Tamil month labels, explicitly not as a full Panchangam or temple-almanac implementation." }, { "key": "bangladeshi_national", "display_name": "Bangladeshi National Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented as the fixed post-2019 Bangladeshi state calendar: first six months 31 days, later months 30, with Falgun extended in Gregorian leap years." }, { "key": "bengali", "display_name": "Bengali Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented as a generic fixed Bengali civil approximation using the older first-five-months-31 reform pattern, intentionally distinct from the post-2019 Bangladeshi national calendar." }, { "key": "astronomical_lunar", "display_name": "Astronomical Lunar Calendar", "kind": "observational_framework", "status": "implemented", "track": "backlog_only", "notes": "Implemented as a reference-only crescent-visibility framework. It intentionally blocks arbitrary conversion until topocentric crescent visibility, sunset, moonset, and Yallop/Odeh-style criteria are available.", "sources": [ "docs/old-future/future_ astronomical_lunar.md" ] }, { "key": "buddhist_many", "display_name": "Buddhist Calendar (Many Variants)", "kind": "meta_unit", "status": "not_standalone", "track": "backlog_only", "notes": "Reclassified on purpose as a family umbrella. 'Buddhist calendar' is too broad for one plain calendar entry and should continue to split into concrete regional families instead." }, { "key": "yele_sambat", "display_name": "Yele Sambat", "kind": "era", "status": "implemented", "track": "backlog_only", "notes": "Implemented as a pinned era-style public surface over Gregorian month/day structure with a January 15 boundary. It is intentionally not a full Kirat lunisolar calendar reconstruction." }, { "key": "aztec", "display_name": "Aztec Calendar", "kind": "cycle", "status": "not_standalone", "track": "backlog_only", "notes": "Reclassified on purpose as an umbrella tracker rather than one more standalone cycle surface. The concrete cycle work now lives in `tonalpohualli`, `trecena_cycle`, `xiuhpohualli`, and the broader Mesoamerican relationship surfaces." }, { "key": "balinese_pawukon", "display_name": "Balinese Pawukon Calendar", "kind": "cycle", "status": "not_standalone", "track": "backlog_only", "notes": "Reclassified on purpose because the concrete public surface is already implemented as `pawukon`. Keeping a second Balinese Pawukon cycle key as planned would just duplicate the same family." }, { "key": "romanian_calendar", "display_name": "Romanian Calendar Naming Layer", "kind": "naming_layer", "status": "implemented", "track": "naming_layers_missing", "notes": "Implemented as a direct Romanian traditional month-name layer over Gregorian date structure." }, { "key": "heliocentric_julian_day", "display_name": "Heliocentric Julian Day", "kind": "serial", "status": "implemented", "track": "backlog_only", "notes": "Implemented as an approximate scalar HJD surface; full heliocentric correction still requires target coordinates and observer location." }, { "key": "sidereal_time", "display_name": "Sidereal Time", "kind": "time_scale", "status": "implemented", "track": "backlog_only", "notes": "Implemented as Greenwich mean/apparent sidereal time. Local sidereal time is deferred because it requires observer longitude/locality input." }, { "key": "binary_clock", "display_name": "Binary Clock", "kind": "time_scale", "status": "implemented", "track": "backlog_only", "notes": "Implemented as UTC-day binary clock notation, not as a physical time scale." }, { "key": "hexadecimal_time", "display_name": "Hexadecimal Time", "kind": "time_scale", "status": "implemented", "track": "backlog_only", "notes": "Implemented as UTC-day hexadecimal clock notation, not as a physical time scale." }, { "key": "octal_time", "display_name": "Octal Time", "kind": "time_scale", "status": "implemented", "track": "alternative_radix_time", "notes": "Implemented as UTC-day octal clock notation inspired by OctaRule-style octal clock ideas; not a physical time scale.", "sources": [ "https://octarule.com/apps/octal-clock", "https://octarule.com/pages/about" ] }, { "key": "thai_six_hour_clock", "display_name": "Thai Six-Hour Clock", "kind": "time_scale", "status": "implemented", "track": "backlog_only", "notes": "Implemented as Thai six-hour clock notation over the UTC civil day; locality/language-specific Thai civil presentation remains future work." }, { "key": "universal_time", "display_name": "Universal Time", "kind": "time_scale", "status": "deferred", "track": "backlog_only", "notes": "Deferred because Universal Time is an umbrella family (UT0, UT1, UT2, UTC-style usage) rather than one unambiguous implementation surface." }, { "key": "tai", "display_name": "TAI (International Atomic Time)", "kind": "time_scale", "status": "implemented", "track": "time_scales_missing", "notes": "Implemented through Astropy's TAI scale." }, { "key": "gps_time", "display_name": "GPS Time", "kind": "time_scale", "status": "implemented", "track": "time_scales_missing", "notes": "Implemented as the continuous GPS clock scale, offset from TAI by 19 seconds." }, { "key": "tcb", "display_name": "TCB (Barycentric Coordinate Time)", "kind": "time_scale", "status": "implemented", "track": "time_scales_missing", "notes": "Implemented through Astropy's TCB scale." }, { "key": "tcg", "display_name": "TCG (Geocentric Coordinate Time)", "kind": "time_scale", "status": "implemented", "track": "time_scales_missing", "notes": "Implemented through Astropy's TCG scale." }, { "key": "ut1", "display_name": "UT1", "kind": "time_scale", "status": "implemented", "track": "time_scales_missing", "notes": "Implemented through Astropy/IERS Earth-rotation data; current/future values may be predictive depending on bundled IERS data." }, { "key": "ut0", "display_name": "UT0", "kind": "time_scale", "status": "deferred", "track": "time_scales_missing", "notes": "Deferred because UT0 is observatory-dependent and requires polar-motion correction plus observer location; the current request model has no observatory/locality fields." }, { "key": "ut2", "display_name": "UT2", "kind": "time_scale", "status": "deferred", "track": "time_scales_missing", "notes": "Deferred because UT2 applies historical seasonal corrections to UT1 and needs an explicit epoch/rule-table policy before exposing a public converter." }, { "key": "local_apparent_solar_time", "display_name": "Local Apparent Solar Time (LAST)", "kind": "time_scale", "status": "deferred", "track": "time_scales_missing", "notes": "Deferred because LAST requires observer longitude and apparent-sun/equation-of-time handling; the current API does not accept locality/longitude." }, { "key": "local_mean_solar_time", "display_name": "Local Mean Solar Time (LMST)", "kind": "time_scale", "status": "deferred", "track": "time_scales_missing", "notes": "Deferred because LMST requires observer longitude/local meridian input; the current API does not accept locality/longitude." }, { "key": "delta_t", "display_name": "ΔT (Delta T)", "kind": "time_scale", "status": "implemented", "track": "ultra_deep_time_scales", "notes": "Implemented as TT minus UT1 in seconds using Astropy/IERS data where available." }, { "key": "dynamical_time", "display_name": "Dynamical Time", "kind": "time_scale", "status": "deferred", "track": "ultra_deep_time_scales", "notes": "Deferred because Dynamical Time is an umbrella/historical family; TT and TDB are already implemented as concrete surfaces, but a separate umbrella key needs policy for which realization to expose." }, { "key": "proper_time", "display_name": "Proper Time", "kind": "time_scale", "status": "deferred", "track": "ultra_deep_time_scales", "notes": "Deferred because proper time depends on a specific observer/worldline and relativistic model; the current app has no trajectory or gravitational potential input." }, { "key": "coordinate_time", "display_name": "Coordinate Time", "kind": "time_scale", "status": "deferred", "track": "ultra_deep_time_scales", "notes": "Deferred because coordinate time is a class of relativistic coordinate systems, not a single scale; concrete TCB and TCG surfaces are implemented." }, { "key": "barycentric_coordinate_dynamical_time", "display_name": "Barycentric Coordinate Dynamical Time", "kind": "time_scale", "status": "deferred", "track": "ultra_deep_time_scales", "notes": "Deferred pending terminology cleanup with existing TDB and newly implemented TCB; exposing this as a separate key now would risk duplicating or confusing barycentric dynamical/coordinate scales." }, { "key": "atomic_time_realizations", "display_name": "Atomic Time Realizations (TAI(k))", "kind": "time_scale", "status": "deferred", "track": "ultra_deep_time_scales", "notes": "Deferred because TAI(k) realizations are laboratory-specific post-processed timescales requiring provider data and station identifiers, not a universal arithmetic conversion." }, { "key": "amiternum_calendar", "display_name": "Amiternum Calendar", "kind": "observational_framework", "status": "implemented", "track": "new_calendars", "notes": "Implemented as a reference-only Roman fasti overlay candidate. It is deliberately not an independent calendar converter; inscription-level data and Roman/Julian normalization remain future work." }, { "key": "gezer_calendar", "display_name": "Gezer Calendar", "kind": "observational_framework", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable; the single-artifact agricultural text is not forced into a daily converter." }, { "key": "thorikos_sacrificial_calendar", "display_name": "Thorikos Sacrificial Calendar", "kind": "overlay", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public source-table surface is registered and selectable; live Attic sacrificial overlay awaits an edition-specific event table." }, { "key": "erchia_sacrificial_calendar", "display_name": "Sacrificial Calendar of Erchia", "kind": "overlay", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public source-table surface is registered and selectable; live Attic sacrificial overlay awaits an edition-specific event table." }, { "key": "hellenic_regional_calendars", "display_name": "Hellenic Regional Calendars", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 3 as a profiled Hellenic historical backbone surface with Attic and autumnal regional profiles, explicitly not a full polis-by-polis lunisolar reconstruction." }, { "key": "alexandrian_calendar", "display_name": "Alexandrian Calendar", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 3 as a late Alexandrian/Coptic-family historical backbone surface using reformed Egyptian month structure and Alexandrian year numbering." }, { "key": "seleucid_calendar_full", "display_name": "Seleucid Calendar (Full Reconstruction)", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 3 as a profiled Seleucid backbone surface with explicit Macedonian/autumnal and Babylonian/spring year-start conventions." }, { "key": "chronography_354_calendar", "display_name": "Chronography of 354 Calendar System", "kind": "overlay", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public source-table surface is registered and selectable; arbitrary daily overlay remains blocked until the late-antique table is modeled." }, { "key": "anglo_saxon_calendar_full", "display_name": "Anglo-Saxon Calendar (Full Reconstruction)", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 3 as an Anglo-Saxon historical backbone surface over Julian civil structure with Bede-attested month labels; fuller lunisolar reconstruction remains future work." }, { "key": "frankish_calendar", "display_name": "Frankish Calendar", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 3 as a Frankish/Carolingian historical backbone surface over Julian civil structure with Carolingian month labels." }, { "key": "old_prussian_calendar", "display_name": "Old Prussian Calendar", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 3 as an Old Prussian historical backbone surface over Julian civil structure, while the more disputed month lexicon remains intentionally deferred." }, { "key": "saxon_calendar_continental", "display_name": "Saxon Calendar (Continental)", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 3 as a continental Saxon historical backbone surface over Julian civil structure with historical Germanic month labels." }, { "key": "umm_al_qura", "display_name": "Umm al-Qura Calendar", "kind": "calendar", "status": "implemented", "track": "new_calendars" }, { "key": "ottoman_rumi", "display_name": "Ottoman Rumi Calendar", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 2 as a historical Ottoman solar calendar with March-year numbering before 1918 and the 1917 Gregorian realignment modeled explicitly." }, { "key": "ottoman_fiscal_maliye", "display_name": "Ottoman Fiscal Calendar (Maliye)", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 2 as a separate Ottoman fiscal/public surface that currently follows the same arithmetic cutover as `ottoman_rumi`, kept distinct for honest historical labeling." }, { "key": "malayalam_calendar", "display_name": "Malayalam Calendar (Kollam Era)", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented as a provider-backed Malayalam/Kollam projection using the kollavarsham library with Surya Siddhanta settings and Kerala reference coordinates; reverse parsing is not yet exposed." }, { "key": "balinese_saka", "display_name": "Balinese Saka Calendar", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 4 as an astronomy-derived Balinese Saka public surface using the internal lunar primitives, explicitly marked as an approximation until a stronger wariga/provider path is added." }, { "key": "javanese_aboge", "display_name": "Javanese Calendar (Aboge System)", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 4 as a provider-backed Javanese Aboge-style public surface using tanggalan, with dina, pasaran, wuku, and mongso labels." }, { "key": "korean_dangi_calendar", "display_name": "Korean Dangi Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented as a solar Dangi-year public calendar surface over Gregorian month/day structure, explicitly distinguished from historical Korean lunisolar reconstruction." }, { "key": "ryukyuan_calendar", "display_name": "Ryukyuan Calendar", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 4 as a Chinese-family Ryukyuan public surface with Okinawan-adaptation month labels, while finer court/island differentiation remains future work." }, { "key": "sukuma_calendar", "display_name": "Sukuma Calendar", "kind": "observational_framework", "status": "implemented", "track": "phase5_replacements", "notes": "Wave 2 implemented this as a documented Sukuma seasonal framework using the published lunar-solar/Jidiku-solstice intake rather than overstating it as a finished normalized public converter." }, { "key": "nyole_calendar", "display_name": "Nyole Calendar", "kind": "observational_framework", "status": "implemented", "track": "phase5_replacements", "notes": "Wave 2 implemented this as a Banyole seasonal/agricultural framework because the current source base supports locality- and consultation-dependent timing more strongly than a pinned public month/day table." }, { "key": "ganda_calendar", "display_name": "Ganda Calendar", "kind": "observational_framework", "status": "implemented", "track": "phase5_replacements", "notes": "Wave 2 implemented this as a Buganda seasonal/public framework because the current source base supports kingdom/agricultural cycle framing more strongly than a normalized traditional month/day converter." }, { "key": "world_season_calendar", "display_name": "World Season Calendar", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 2 as an explicit reform-calendar model with four 31-30-30 seasons, Leapyear Day, and Worldsday." }, { "key": "symmetry454_calendar", "display_name": "Symmetry454 Calendar", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 2 as a reform-calendar model using the published 4-5-4 week structure and 293-year leap-week cycle." }, { "key": "tranquility_calendar", "display_name": "Tranquility Calendar", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 5 as a Moon-Landing-centered reform/proposal calendar based on the Tranquility era model, with 13 equal months plus Armstrong Day and leap-year Aldrin Day. It is intentionally presented as a proposal surface, not a native civil calendar." }, { "key": "galilean_moon_calendars", "display_name": "Galilean Moon Calendars", "kind": "calendar", "status": "implemented", "track": "new_calendars", "notes": "Implemented in Wave 5 as a profiled Darian-derived proposal family for Io, Europa, Ganymede, and Callisto using Earth-year synchronization. It is intentionally a comparative off-world proposal surface, not a native civil calendar or site-specific chronometry model." }, { "key": "umma_calendar", "display_name": "Umma Calendar", "kind": "observational_framework", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a reference-only Ur III local administrative/cultic calendar framework. Arbitrary conversion remains blocked until a source-table profile exists." }, { "key": "pentecontad_calendar", "display_name": "Pentecontad Calendar", "kind": "observational_framework", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a reference-only fifty-day festival/reconstruction framework. It preserves the scholarly caution and does not choose a universal annual anchor or supplement rule." }, { "key": "four_seasons_eight_nodes", "display_name": "Four Seasons and Eight Nodes", "kind": "overlay", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public seasonal overlay is registered and selectable; detailed output should build on the Chinese solar-terms profile." }, { "key": "six_ancient_chinese_calendars", "display_name": "Six Ancient Chinese Calendars", "kind": "observational_framework", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a reference-only ancient Chinese sifen bundle for Huangdi, Yin, Zhou, Lu, Xia, and Zhuanxu traditions. Constants are exposed, but public conversion is deliberately blocked until individual reconstructed profiles have source/epoch/month-ordering decisions." }, { "key": "nisgaa_calendar", "display_name": "Nisga'a Calendar", "kind": "observational_framework", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable; live conversion remains blocked pending locality/source-profile anchoring." }, { "key": "inuit_calendar", "display_name": "Inuit Calendar", "kind": "observational_framework", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable; live conversion remains blocked pending locality and seasonal observation profiles." }, { "key": "haab", "display_name": "Haabʼ", "kind": "cycle", "status": "not_standalone", "track": "wikipedia_list_of_calendars", "notes": "Already appears as a component inside Maya calendar-round style output; track explicitly without duplicating it as a separate full calendar for now." }, { "key": "attic_calendar", "display_name": "Attic Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a standalone public wrapper over the Attic/Athenian profile of `hellenic_regional_calendars`, so it is directly selectable without pretending to be a separate deeper reconstruction." }, { "key": "old_persian_calendar", "display_name": "Old Persian Calendar", "kind": "observational_framework", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a reference-only Achaemenid lunisolar month-name framework. It is intentionally distinct from modern Persian/Solar Hijri and Zoroastrian-family arithmetic." }, { "key": "chinese_taichu_calendar", "display_name": "Taichu Calendar / Grand Inception Calendar", "kind": "observational_framework", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a reference-only Han Taichu profile with structural constants and explicit source/epoch blockers. The old `genesis_calendar_chinese` label is kept only as an alias in catalog metadata." }, { "key": "ptolemaic_calendar", "display_name": "Ptolemaic Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a guarded phase-aware solar reconstruction with assimilated Macedonian/Egyptian and Canopic reform profiles. Early Macedonian lunar dual-dating remains blocked.", "sources": [ "docs/old-future/future_ ptolemaic_calendar.md" ] }, { "key": "qumran_enoch_calendar", "display_name": "Qumran / Enoch 364-Day Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a strict 364-day Qumran/Enoch/Jubilees reconstruction with locked weekdays and explicit leap-week uncertainty. The v1 profile is strict_364_wandering only.", "sources": [ "docs/old-future/future_ qumran_enoch_calendar.md" ] }, { "key": "coligny_calendar", "display_name": "Coligny Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Covered by the implemented `gaulish_calendar_variants` profile surface." }, { "key": "chinese_daming_calendar", "display_name": "Daming Calendar", "kind": "observational_framework", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a reference-only historical Chinese li profile. The 391-year / 4836-month Daming constants are exposed, but official date conversion remains blocked pending source edition, epoch, meridian, new-moon, solar-term, and intercalation work." }, { "key": "korean_lunisolar_calendar", "display_name": "Korean Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a Korean lunisolar comparative public surface over the Chinese-family lunisolar backbone, with Dangi-style year numbering and Korean month labels. It is intentionally not yet a Joseon-almanac-perfect reconstruction." }, { "key": "chinese_wuyin_calendar", "display_name": "Wuyin Yuan Calendar", "kind": "observational_framework", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a reference-only Tang historical Chinese li profile with 676-year / 8361-month constants and an explicit true/mean new-moon phase-boundary blocker." }, { "key": "pyu_calendar", "display_name": "Pyu Calendar", "kind": "observational_framework", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a reference-only Pyu/Siddhantic predecessor framework. It preserves era-shift and archaeological cautions while blocking month/day conversion until a source-checked engine exists.", "sources": [ "docs/old-future/future_ pyu_calendar.md" ] }, { "key": "bulgar_calendar", "display_name": "Bulgar Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a guarded Nominalia-style cyclic reconstruction using the 680 CE Somor anchor and a vernal solar grid. Exact leap and month-boundary rules remain disputed.", "sources": [ "docs/old-future/future_ bulgar_calendar.md" ] }, { "key": "florentine_calendar", "display_name": "Florentine Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a Julian-based Annunciation-style civic year-beginning variant whose year changes on March 25 and runs one year behind standard Julian numbering from January 1 through March 24." }, { "key": "pisan_calendar", "display_name": "Pisan Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a Julian-based Annunciation-style civic year-beginning variant whose year changes on March 25 and runs one year ahead of standard Julian numbering from March 25 through December 31." }, { "key": "chula_sakarat", "display_name": "Chula Sakarat", "kind": "era", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Represented in the implemented Thai lunar provider-backed surface; tracked explicitly because Wikipedia lists it as a calendar/era system." }, { "key": "chinese_shoushi_calendar", "display_name": "Shoushi Calendar / Season-Granting Calendar", "kind": "observational_framework", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a reference-only Yuan Shoushi profile. The page preserves the system's mathematical-astronomical complexity and blocks conversion until a source algorithm, correction tables, court meridian, and validation examples exist. `seasonal_instruction_calendar` is treated as an alias." }, { "key": "six_imperial_chinese_calendars", "display_name": "Six Imperial Chinese Calendars", "kind": "meta_unit", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented only as a blocked reference category. The research found no source-secure definition of the six member calendars, so the app refuses to substitute Datong, Shoushi, Shixian, or a generic Ming calendar." }, { "key": "incan_calendar", "display_name": "Inca Calendar", "kind": "observational_framework", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a reference-only Inca/Cuzco ritual, solar, lunar, and ceque/huaca framework rather than a normalized pan-Andean converter." }, { "key": "muisca_calendar", "display_name": "Muisca Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a Duquesne-model cyclic reconstruction with strong historical-warning labels. It is not presented as a secure native Muisca civil calendar.", "sources": [ "docs/old-future/future_ muisca_calendar.md" ] }, { "key": "chinese_shixian_calendar", "display_name": "Shixian Calendar / Seasonal Constitution Calendar", "kind": "observational_framework", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a reference-only Qing/Joseon Shixian profile family, with version, source-edition, meridian, and true-solar-term blockers made explicit. `seasonal_constitution_calendar` is treated as an alias." }, { "key": "pancronometer", "display_name": "Pancronometer / Universal Georgian Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a reference-only calendar-reform proposal entry. Date arithmetic remains blocked until Hugh Jones's primary-source rules are normalized.", "sources": [ "docs/old-future/future_ pancronometer.md" ] }, { "key": "invariable_calendar", "display_name": "Invariable Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as an equal-quarter perennial reform proposal with 30-30-31 month structure, a year-end New Year's Day, and a midyear Leap Day outside the weekly cycle." }, { "key": "minguo_calendar", "display_name": "Minguo Calendar", "kind": "era", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as Gregorian month/day structure with Republic of China era numbering from 1912 onward." }, { "key": "revised_julian_calendar", "display_name": "Revised Julian Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a real reform-calendar surface using the Milankovic 900-year leap rule over Gregorian-style month/day structure." }, { "key": "world_calendar", "display_name": "World Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as the classic 31-30-30 equal-quarter perennial reform proposal with Worldsday and Leapyear Day outside the weekly cycle." }, { "key": "vira_nirvana_samvat", "display_name": "Vira Nirvana Samvat", "kind": "era", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a pinned Jain era-style surface over Gregorian month/day structure using the widely cited 527 BCE nirvana epoch. The fuller Jain calendar family is still future work." }, { "key": "javanese_calendar", "display_name": "Javanese Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Represented by the implemented `javanese_aboge` provider-backed surface; keep this row as the Wikipedia-list umbrella, not a duplicate converter request." }, { "key": "kerian_octal_calendar", "display_name": "Kerian Octal Calendar", "kind": "calendar", "status": "implemented", "track": "alternative_radix_calendars", "notes": "Implemented as a reference-only alternative-radix proposal entry. Conversion remains blocked until exact base-8 rules and string-based input schema support are available.", "sources": [ "docs/old-future/future_ kerian_octal_calendar.md", "https://octarule.com/apps/kerian-calendar", "https://octarule.com/pages/about" ] }, { "key": "neolithic_lunar_tally_systems", "display_name": "Neolithic Lunar Tally Systems", "kind": "observational_framework", "status": "implemented", "track": "proto_calendars", "notes": "Implemented as a proto-calendar lunar phase/tally mapper, not an absolute artifact calendar. It maps a queried instant to a mean lunar phase and tally count while warning that artifacts did not count continuously to modern JDNs.", "sources": [ "docs/old-future/future_ neolithic_lunar_tally_systems.md" ] }, { "key": "etruscan_calendar", "display_name": "Etruscan Calendar", "kind": "observational_framework", "status": "implemented", "track": "proto_calendars", "notes": "Implemented as a reference-only umbrella for fragmentary Etruscan calendrical evidence. No universal Etruscan epoch or date converter is exposed." }, { "key": "hittite_calendar", "display_name": "Hittite Calendar", "kind": "observational_framework", "status": "implemented", "track": "proto_calendars", "notes": "Implemented as a reference-only Hittite cultic/administrative calendar framework. Source-table reconstruction remains future work." }, { "key": "icelandic_misseri", "display_name": "Icelandic Misseri System", "kind": "calendar", "status": "implemented", "track": "rare_structural_calendars", "notes": "Implemented in Wave 5 as a structural half-year calendar with summer and winter misseris anchored to the modern sumardagurinn fyrsti rule. It is intentionally separate from the historical Icelandic month-name backbone surface." }, { "key": "gaulish_calendar_variants", "display_name": "Gaulish Calendar Variants", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in the historical-backbone wave as a profile-aware Gaulish public surface with Coligny and fragmentary variant month-label families, not as a full reconstructed lunisolar algorithm." }, { "key": "old_irish_calendar", "display_name": "Old Irish Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in the historical-backbone wave as an Old Irish public surface over Julian civil structure with early Irish month labels, not as a full insular lunisolar reconstruction." }, { "key": "pictish_calendar", "display_name": "Pictish Calendar", "kind": "calendar", "status": "implemented", "track": "phase5_replacements", "notes": "Implemented in the historical-backbone wave as a cautious Pictish public surface over Julian civil structure with reconstructed month labels, explicitly not as a settled Pictish lunisolar reconstruction." }, { "key": "arian", "display_name": "Slavic Aryan Calendar (Kolyada Dar)", "kind": "calendar", "status": "implemented", "track": "external_specs", "notes": "Implemented only as a modern synthetic Kolyada Dar profile (`modern_fixed_sep20_18_local_v1`) with a fixed 2024-09-20 18:00 local anchor, nine-month structure, 16-hour day, and explicit anachronistic/approximate labels. It is not presented as ancient Slavic history.", "sources": [ "docs/future_arian.md" ] }, { "key": "british_regnal_fiscal_calendar", "display_name": "British Regnal/Fiscal Calendar System", "kind": "overlay", "status": "implemented", "track": "future_research_profiled_overlays", "notes": "Profile-gated UK personal tax, government financial-year, and current Charles III regnal overlays are implemented with explicit date ranges." }, { "key": "french_ancien_regime_fiscal_calendar", "display_name": "French Ancien Regime Fiscal Calendar", "kind": "overlay", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public fiscal surface is registered and selectable; live output awaits jurisdiction/source-profile tables." }, { "key": "chinese_imperial_reign_calendar", "display_name": "Chinese Imperial Reign Calendar", "kind": "overlay", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public reign-calendar surface is registered and selectable; live output remains blocked pending reign/era tables." }, { "key": "swedish_calendar_anomaly", "display_name": "Swedish Calendar (1700–1712 Anomaly)", "kind": "calendar", "status": "implemented", "track": "transitional_calendars", "notes": "Implemented in Wave 2 as a bounded anomaly calendar with the 1700-1712 one-day shift and the unique 1712-02-30 handled explicitly." }, { "key": "alaska_transfer_calendar_anomaly", "display_name": "Alaska Transfer Calendar Anomaly", "kind": "calendar", "status": "implemented", "track": "transitional_calendars", "notes": "Implemented in Wave 2 as a bounded local transition calendar with Julian dating through 1867-10-06, an omitted local interval, and Gregorian dating from 1867-10-18." }, { "key": "philippine_spanish_transition_calendar", "display_name": "Philippine Spanish Calendar Transition", "kind": "calendar", "status": "implemented", "track": "transitional_calendars", "notes": "Implemented in Wave 2 as a bounded dateline-skip calendar with local 1844-12-31 omitted and neighboring dates mapped explicitly." }, { "key": "titan_darian_calendar", "display_name": "Titan Darian Calendar Variant", "kind": "calendar", "status": "implemented", "track": "space_future_calendars", "notes": "Implemented as a reference-only Titan Darian variant contract. Live conversion remains blocked until interplanetary time-scale and planetary rotation-frame support exists.", "sources": [ "docs/old-future/future_ titan_darian_calendar.md" ] }, { "key": "venus_solar_calendar", "display_name": "Venus Solar Calendar", "kind": "calendar", "status": "implemented", "track": "space_future_calendars", "notes": "Implemented as a reference-only Venus solar calendar contract. Live conversion remains blocked until Venus-centric coordinate time, retrograde rotation, and illumination logic exist.", "sources": [ "docs/old-future/future_ venus_solar_calendar.md" ] }, { "key": "lunar_standard_time_calendar", "display_name": "Lunar Standard Time Calendar", "kind": "calendar", "status": "implemented", "track": "space_future_calendars", "notes": "Implemented as a reference-only lunar surface-time contract. It intentionally refuses simple UTC-offset conversion until lunar coordinate time and selenographic longitude support exist.", "sources": [ "docs/old-future/future_ lunar_standard_time_calendar.md" ] }, { "key": "interplanetary_coordinated_time", "display_name": "Interplanetary Coordinated Time", "kind": "time_scale", "status": "implemented", "track": "space_future_calendars", "notes": "Implemented as a reference-only interplanetary time-scale contract. It remains blocked for live conversion until a TCB/barycentric relativistic platform is built.", "sources": [ "docs/old-future/future_ interplanetary_coordinated_time.md" ] }, { "key": "darian", "display_name": "Darian Calendar", "kind": "calendar", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented Mars proposal calendar; adjacent Mars sol scalar tracking is separate as `mars_sol_date`." }, { "key": "discworld_calendar", "display_name": "Discworld Calendar", "kind": "meta_unit", "status": "not_standalone", "track": "wikipedia_list_of_calendars", "notes": "Reclassified on purpose as a fictional-scope tracker rather than a plain calendar ticket until the project has an explicit fiction/proposal product policy." }, { "key": "middle_earth_calendars", "display_name": "Middle-earth Calendars", "kind": "meta_unit", "status": "not_standalone", "track": "wikipedia_list_of_calendars", "notes": "Reclassified on purpose as a fictional family tracker rather than one vague calendar ticket. If implemented later, it likely needs profiles rather than a single surface." }, { "key": "stardates", "display_name": "Stardates", "kind": "serial", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a profiled TNG-style fictional scalar approximation; Star Trek stardates are not one consistent real-world chronology." }, { "key": "utc", "display_name": "Coordinated Universal Time (UTC)", "kind": "time_scale", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented core UTC time-scale surface." }, { "key": "fiscal_year", "display_name": "Fiscal Year", "kind": "overlay", "status": "implemented", "track": "future_research_profiled_overlays", "notes": "No default world fiscal year is exposed. Only the explicit synthetic Apr 1 QA/demo profile computes; missing profile returns fallback metadata." }, { "key": "accounting_360_day_calendar", "display_name": "360-Day Accounting Calendar", "kind": "meta_unit", "status": "not_standalone", "track": "standards_and_jd_variants", "notes": "Reclassified on purpose as a day-count/accounting convention tracker rather than a plain standalone calendar. It belongs with fiscal/accounting overlays and serial conventions." }, { "key": "accounting_365_day_calendar", "display_name": "365-Day Accounting Calendar", "kind": "meta_unit", "status": "not_standalone", "track": "standards_and_jd_variants", "notes": "Reclassified on purpose as a day-count/accounting convention tracker rather than a plain standalone calendar. It belongs with fiscal/accounting overlays and serial conventions." }, { "key": "iso_8601", "display_name": "ISO 8601 Date/Time Standard", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented as a UTC ISO 8601 projection surface. Full ISO parsing, durations, intervals, offsets, and expanded representations remain future work; the narrower ISO week-date converter already exists as `iso`." }, { "key": "iso", "display_name": "ISO Week Date", "kind": "calendar", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented narrower ISO week-date calendar surface." }, { "key": "decimal_date", "display_name": "Decimal Date", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented as a Gregorian decimal-year scalar." }, { "key": "jdn_calendar", "display_name": "Julian Date / Julian Day Number (JD)", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented as the app's Julian Day Number scalar surface." }, { "key": "mjd", "display_name": "Modified Julian Date (MJD)", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented as MJD = JD - 2400000.5 with midnight day boundary." }, { "key": "dublin", "display_name": "Dublin Julian Day (DJD)", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented as DJD = JD - 2415020.0." }, { "key": "rata_die", "display_name": "Rata Die", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented as a Common Era day-count scalar." }, { "key": "lilian", "display_name": "Lilian Date", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented as a day count from the Gregorian reform epoch." }, { "key": "unix", "display_name": "Unix Time", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented as non-leap seconds from 1970-01-01T00:00:00 UTC." }, { "key": "bjd", "display_name": "Barycentric Julian Date (BJD)", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented as the app's Barycentric Julian Date serial surface." }, { "key": "cnes_julian_date", "display_name": "CNES Julian Date", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented JD offset system with 1950-01-01T00:00 epoch." }, { "key": "ccsds_julian_date", "display_name": "CCSDS Julian Date", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented JD offset system with 1958-01-01T00:00 epoch; distinct from the CCSDS CUC scalar entry." }, { "key": "modified_jd2000", "display_name": "Modified JD2000 (MJD2000)", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented ESA-style JD offset from 2000-01-01T00:00." }, { "key": "mars_sol_date", "display_name": "Mars Sol Date", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented Martian sol count scalar based on JD and the 1.02749-day sol conversion." }, { "key": "javascript_date", "display_name": "JavaScript Date Timestamp", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented as milliseconds from the Unix epoch, excluding leap seconds." }, { "key": "ext4_file_timestamp", "display_name": "EXT4 File Timestamp", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented as nanoseconds from the Unix epoch, excluding leap seconds." }, { "key": "dotnet_datetime_ticks", "display_name": ".NET DateTime Ticks", "kind": "serial", "status": "implemented", "track": "standards_and_jd_variants", "notes": "Implemented as 100-nanosecond ticks from 0001-01-01T00:00 in the proleptic Gregorian calendar." }, { "key": "truncated_julian_date", "display_name": "Truncated Julian Date (TJD)", "kind": "serial", "status": "implemented", "track": "serial_missing", "notes": "Implemented as a real serial system with the NASA-style TJD epoch JD 2440000.5 and midnight-based time components." }, { "key": "reduced_julian_date", "display_name": "Reduced Julian Date (RJD)", "kind": "serial", "status": "implemented", "track": "serial_missing", "notes": "Implemented as a real serial system with RJD = JD - 2400000.0, preserving the noon-based Julian-day convention." }, { "key": "ccsds_unsegmented_time_code", "display_name": "CCSDS Unsegmented Time Code (CUC)", "kind": "serial", "status": "implemented", "track": "serial_missing", "notes": "Implemented as UTC-based scalar seconds from the CCSDS epoch, not as a full binary packet encoder." }, { "key": "julian_ephemeris_date", "display_name": "Julian Ephemeris Date (JED)", "kind": "serial", "status": "implemented", "track": "serial_missing", "notes": "Implemented as a TT-based scalar serial parallel to JD, with UTC<->TT conversion handled through the app time-scale layer." }, { "key": "libreoffice_calc_serial", "display_name": "LibreOffice Calc Serial Date", "kind": "serial", "status": "implemented", "track": "serial_missing", "notes": "Implemented as a concrete spreadsheet serial family with 1899-12-30 epoch and no Excel 1900 leap-day bug." }, { "key": "open_document_spreadsheet_serial", "display_name": "OpenDocument Spreadsheet Serial Date", "kind": "serial", "status": "implemented", "track": "serial_missing", "notes": "Implemented as the materially equivalent 1899-12-30 OpenDocument/LibreOffice serial baseline." }, { "key": "epact_number_system", "display_name": "Epact Number System", "kind": "cycle", "status": "implemented", "track": "serial_advanced", "notes": "Implemented as a Gregorian computus numeric cycle, not as a plain scalar serial." }, { "key": "golden_number", "display_name": "Golden Number", "kind": "cycle", "status": "implemented", "track": "serial_advanced", "notes": "Implemented as a yearly computus cycle index, not as a plain scalar serial." }, { "key": "julian_period", "display_name": "Julian Period", "kind": "serial", "status": "implemented", "track": "serial_advanced", "notes": "Implemented as the annual Scaliger chronology index." }, { "key": "scaliger_cycle_components", "display_name": "Scaliger Cycle Components", "kind": "cycle", "status": "implemented", "track": "serial_advanced", "notes": "Implemented as a compound chronology projection exposing solar cycle, lunar cycle, and indiction together." }, { "key": "day_of_era", "display_name": "Day of Era", "kind": "serial", "status": "implemented", "track": "serial_advanced", "notes": "Implemented as a Common Era day-count scalar anchored to 0001-01-01 CE in the proleptic Gregorian calendar." }, { "key": "continuous_week_count", "display_name": "Continuous Week Count Systems", "kind": "serial", "status": "implemented", "track": "serial_advanced", "notes": "Implemented with an ISO Monday-based continuous week-count profile as the v1 default." }, { "key": "dangi_era", "display_name": "Dangi Era", "kind": "era", "status": "implemented", "track": "eras_missing", "notes": "Implemented as a Gregorian month/day era projection with Dangi year numbering, kept separate from the broader Korean Dangi calendar public surface." }, { "key": "kollam_era", "display_name": "Kollam Era", "kind": "era", "status": "implemented", "track": "eras_missing", "notes": "Implemented as a Gregorian month/day era projection with a pinned Chingam-style mid-August year boundary. The fuller provider-backed Malayalam calendar remains a distinct surface." }, { "key": "spanish_era", "display_name": "Spanish Era (Era Hispánica)", "kind": "era", "status": "implemented", "track": "eras_missing", "notes": "Implemented as Gregorian month/day structure with Spanish/Hispanic era numbering from the 38 BCE epoch." }, { "key": "ab_urbe_condita", "display_name": "Ab urbe condita (AUC)", "kind": "era", "status": "implemented", "track": "eras_missing", "notes": "Implemented as a Gregorian month/day era projection using the conventional 753 BCE offset, intentionally separate from the Roman calendar surface." }, { "key": "anno_graecorum", "display_name": "Anno Graecorum", "kind": "era", "status": "implemented", "track": "eras_missing", "notes": "Implemented as a profiled Seleucid-era year-numbering surface with explicit Babylonian/spring and Macedonian/autumn reckonings." }, { "key": "buddhist_era_variants", "display_name": "Buddhist Era Variants", "kind": "era", "status": "implemented", "track": "eras_missing", "notes": "Implemented as a profiled comparative family over Gregorian month/day structure, separating major regional Buddhist-era year-boundary conventions." }, { "key": "era_fascista", "display_name": "Era Fascista", "kind": "era", "status": "implemented", "track": "eras_missing", "notes": "Implemented as a pinned Gregorian month/day era projection with the March on Rome anniversary as the year boundary." }, { "key": "diocletian_era", "display_name": "Diocletian Era", "kind": "era", "status": "implemented", "track": "eras_deep", "notes": "Implemented as a Gregorian month/day era projection using the Alexandrian new-year anniversary. It remains distinct from month-structured Coptic and Alexandrian calendars." }, { "key": "era_of_nabonassar", "display_name": "Era of Nabonassar", "kind": "era", "status": "implemented", "track": "eras_deep", "notes": "Implemented as a pinned astronomical chronology-era surface over Gregorian month/day structure, not as a full Babylonian calendar reconstruction." }, { "key": "olympiad_dating_era", "display_name": "Olympiad Dating System", "kind": "era", "status": "implemented", "track": "eras_deep", "notes": "Implemented as a compound chronology surface exposing Olympiad number and year-within-Olympiad rather than as a normal standalone calendar." }, { "key": "abbasid_era", "display_name": "Abbasid Era", "kind": "era", "status": "implemented", "track": "eras_deep", "notes": "Implemented as a pinned Gregorian month/day era projection using the accession of al-Saffah in 750 as the epoch for this comparative surface." }, { "key": "armenian_era", "display_name": "Armenian Era", "kind": "era", "status": "implemented", "track": "eras_deep", "notes": "Implemented as a Gregorian month/day era projection using the conventional 552-07-11 epoch, intentionally separate from the Armenian calendar surface." }, { "key": "ethiopian_incarnation_era_variants", "display_name": "Ethiopian Incarnation Era Variants", "kind": "era", "status": "implemented", "track": "eras_deep", "notes": "Implemented as a profiled era family separating Amete Mihret and Amete Alem over a shared Gregorian month/day structure." }, { "key": "medieval_world_eras", "display_name": "World Eras in Medieval Chronicles", "kind": "era", "status": "implemented", "track": "eras_deep", "notes": "Implemented as a target-only comparative profile family for Byzantine world-era, Ethiopian Amete Alem, and Hebrew Anno Mundi year-numbering surfaces." }, { "key": "islamic_prayer_time_system", "display_name": "Islamic Prayer Time System", "kind": "overlay", "status": "implemented", "track": "overlays_missing", "notes": "Implemented as a locality-aware Islamic overlay parallel to the Orthodox/Catholic overlays. Uses adhanpy prayer-time calculations, profile-aware method/jurisdiction choices, maghrib-based observance-day switching, and Hijri feast/fast context with tabular or Umm al-Qura date bases depending on profile." }, { "key": "chinese_solar_terms", "display_name": "Chinese Solar Terms (24 Jieqi)", "kind": "overlay", "status": "implemented", "track": "future_research_profiled_overlays", "notes": "Profile-gated modern China 120E dingqi overlay computes current, previous, and next solar terms; missing profile returns fallback metadata." }, { "key": "hindu_festival_overlay", "display_name": "Hindu Festival Overlay Systems", "kind": "overlay", "status": "planned", "track": "overlays_missing" }, { "key": "agricultural_seasonal_overlay", "display_name": "Agricultural Seasonal Overlays", "kind": "overlay", "status": "planned", "track": "overlays_missing" }, { "key": "astronomical_event_overlay", "display_name": "Astronomical Event Overlays", "kind": "overlay", "status": "planned", "track": "overlays_missing" }, { "key": "regnal_year_overlay", "display_name": "Regnal Year Overlay", "kind": "overlay", "status": "planned", "track": "overlays_missing", "notes": "Consolidates repeated regnal-year requests into one overlay family." }, { "key": "consular_dating", "display_name": "Consular Dating", "kind": "overlay", "status": "planned", "track": "overlays_advanced" }, { "key": "indiction_tax_cycle_overlay", "display_name": "Indiction Tax Cycle Overlay", "kind": "overlay", "status": "planned", "track": "overlays_advanced" }, { "key": "liturgical_reading_cycles", "display_name": "Liturgical Reading Cycles", "kind": "overlay", "status": "planned", "track": "overlays_advanced" }, { "key": "agricultural_phenology_overlay", "display_name": "Agricultural Phenology Overlay", "kind": "overlay", "status": "planned", "track": "overlays_advanced" }, { "key": "astrological_overlays", "display_name": "Astrological Overlays", "kind": "overlay", "status": "planned", "track": "overlays_advanced" }, { "key": "callippic_cycle", "display_name": "Callippic Cycle", "kind": "cycle", "status": "implemented", "track": "cycles_missing", "notes": "Implemented as a 27,759-day mean lunisolar correlation cycle anchored near midsummer 330 BCE, exposing period/day, mean lunation, and Metonic subcycle fields without pretending to reconstruct Attic month names or observed lunar phases." }, { "key": "saros_cycle", "display_name": "Saros Cycle", "kind": "cycle", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only Saros constants and event-required fallback are implemented; arbitrary daily Saros position remains intentionally unsupported." }, { "key": "exeligmos_cycle", "display_name": "Exeligmos Cycle", "kind": "cycle", "status": "implemented", "track": "cycles_missing", "notes": "Implemented as a reference-only triple-Saros eclipse recurrence surface. Arbitrary dates return event-required fallback metadata; relation helpers are designed for cataloged solar/lunar eclipse events." }, { "key": "olympiad_cycle", "display_name": "Olympiad Cycle", "kind": "cycle", "status": "implemented", "track": "cycles_missing", "notes": "Implemented as the repeating four-year Olympiad cycle, kept distinct from the already implemented Olympiad dating era surface." }, { "key": "roman_indiction_variants", "display_name": "Roman Indiction Variants", "kind": "cycle", "status": "implemented", "track": "cycles_missing", "notes": "Implemented as a comparative 15-year indiction cycle surface showing January-style, Byzantine September-style, and Christmas-style year-beginning conventions side by side." }, { "key": "jupiter_cycle", "display_name": "Jupiter Cycle", "kind": "cycle", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable; split historical, synodic, and orbital profiles are tracked separately." }, { "key": "trecena_cycle", "display_name": "Trecena Cycle", "kind": "cycle", "status": "implemented", "track": "cycles_missing", "notes": "Implemented as the direct 13-day Aztec trecena cycle derived from the same pinned Tōnalpōhualli anchor already used elsewhere in the project." }, { "key": "tzolkin", "display_name": "Tzolkʼin", "kind": "cycle", "status": "implemented", "track": "cycles_missing", "notes": "Implemented as a first-class Maya 260-day cycle aligned to the same GMT-style anchor used for the project's Long Count and Maya Calendar Round relationship." }, { "key": "mayan_calendar_round", "display_name": "Maya Calendar Round", "kind": "cycle", "status": "implemented", "track": "cycles_missing", "notes": "Implemented as the combined Tzolkʼin + Haabʼ repeating designation. It is intentionally tracked separately from the linear Long Count because Calendar Round is not uniquely identifying by itself." }, { "key": "epact_cycle", "display_name": "Epact Cycle", "kind": "cycle", "status": "not_standalone", "track": "cycles_advanced", "notes": "Reclassified on purpose because the concrete public surface already exists as `epact_number_system`. A separate Epact Cycle key would just duplicate the same computus family work." }, { "key": "great_year", "display_name": "Great Year", "kind": "cycle", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable; competing Great Year definitions are documented instead of normalized into one converter." }, { "key": "precession_cycle", "display_name": "Precession Cycle", "kind": "cycle", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable; arbitrary date projection is blocked until an explicit epoch/model profile is chosen." }, { "key": "solar_anomaly_cycles", "display_name": "Solar Anomaly Cycles", "kind": "cycle", "status": "research_required", "track": "cycles_advanced", "notes": "Blocked on stronger astronomical-source framing. This belongs with future solar/astronomical primitives and event overlays rather than as a generic standalone cycle." }, { "key": "tithi_cycle", "display_name": "Tithi Cycle", "kind": "cycle", "status": "not_standalone", "track": "cycles_advanced", "notes": "Reclassified on purpose as a Hindu calendrical component rather than a standalone public cycle ticket. It should come back together with deeper Panchangam/festival work." }, { "key": "karana_cycle", "display_name": "Karana Cycle", "kind": "cycle", "status": "not_standalone", "track": "cycles_advanced", "notes": "Reclassified on purpose as a Hindu calendrical component rather than a standalone public cycle ticket. It should come back together with deeper Panchangam/festival work." }, { "key": "zodiacal_cycles", "display_name": "Zodiacal Cycles", "kind": "cycle", "status": "not_standalone", "track": "cycles_advanced", "notes": "Reclassified on purpose as an umbrella/meta cycle tracker. Concrete zodiacal logic already appears inside implemented systems, and broader zodiacal cycle work needs cleaner family splitting first." }, { "key": "yoruba_week", "display_name": "Yoruba Four-Day Week", "kind": "cycle", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable; live cycle position remains blocked without a locality/week-anchor profile." }, { "key": "korean_five_day_market_cycle", "display_name": "Korean Five-Day Market Cycle", "kind": "overlay", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable; market-cycle output remains blocked pending locality-specific market tables." }, { "key": "javanese_pasaran_cycle", "display_name": "Javanese Pasaran Cycle", "kind": "cycle", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Represented inside the implemented `javanese_aboge` surface." }, { "key": "roman_nundinal_cycle", "display_name": "Roman Nundinal Cycle", "kind": "cycle", "status": "research_required", "track": "wikipedia_list_of_calendars", "notes": "Needs stronger historical anchor discipline before implementation. The nundinal letters are real, but a clean public cycle surface should not quietly choose an arbitrary proleptic anchor." }, { "key": "burmese_eight_day_week", "display_name": "Burmese Eight-Day Week", "kind": "cycle", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a separate weekday-split cycle surface, distinct from the broader Burmese calendar entry." }, { "key": "celtic_eight_day_week", "display_name": "Celtic Eight-Day Week", "kind": "cycle", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable. Live conversion remains blocked without locality/source-profile anchoring." }, { "key": "baltic_nine_day_week", "display_name": "Baltic Nine-Day Week", "kind": "cycle", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable. Conversion stays blocked because the guide does not provide a secure continuous anchor or source-backed reconstruction." }, { "key": "chinese_ten_day_xun", "display_name": "Chinese Ten-Day Xun", "kind": "cycle", "status": "research_required", "track": "wikipedia_list_of_calendars", "notes": "Needs stronger Chinese calendrical-context framing before implementation. A clean Xun surface should be coordinated with sexagenary and Chinese-family structural work rather than guessed as a bare ten-day loop." }, { "key": "egyptian_decans", "display_name": "Egyptian Decans / Ten-Day Periods", "kind": "cycle", "status": "research_required", "track": "wikipedia_list_of_calendars", "notes": "Needs stronger astronomical/historical framing before implementation. Egyptian decans are more than just a neutral ten-day week label and should not be flattened too early." }, { "key": "french_republican_decade", "display_name": "French Republican Décade", "kind": "cycle", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as the ten-day week component derived from the already implemented French Republican calendar surface, with complementary Sansculottides days handled explicitly." }, { "key": "old_high_german_month_names", "display_name": "Old High German Month Names", "kind": "naming_layer", "status": "planned", "track": "naming_layers_missing", "notes": "Deferred on purpose. A simple Gregorian month swap would be misleading; this should follow fuller Germanic/historical calendar work." }, { "key": "anglo_saxon_month_names", "display_name": "Anglo-Saxon Month Names", "kind": "naming_layer", "status": "planned", "track": "naming_layers_missing", "notes": "Deferred on purpose even after Wave 3, because the implemented `anglo_saxon_calendar_full` now covers the historical backbone surface and any separate naming-layer should be justified as a distinct linguistic layer, not a duplicate." }, { "key": "germanic_calendar_month_names", "display_name": "Germanic Calendar Month Names", "kind": "meta_unit", "status": "not_standalone", "track": "wikipedia_list_of_calendars", "notes": "Reclassified on purpose as an umbrella/family tracker rather than a plain naming-layer ticket. The concrete work belongs in narrower entries such as Old High German and Anglo-Saxon month-name layers or fuller historical Germanic calendar surfaces." }, { "key": "lithuanian_calendar_names", "display_name": "Lithuanian Calendar Names", "kind": "naming_layer", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a direct Lithuanian public naming layer over Gregorian date structure, including month names and weekday vocabulary." }, { "key": "rapa_nui_calendar_names", "display_name": "Rapa Nui Calendar Month Names", "kind": "naming_layer", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public naming-layer surface is registered and selectable; live date naming remains blocked by lunar-month/source-profile choices." }, { "key": "xhosa_calendar_names", "display_name": "Xhosa Calendar Names", "kind": "naming_layer", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public naming-layer surface is registered and selectable; live projection remains blocked pending source normalization." }, { "key": "turkmen_calendar_names", "display_name": "Turkmen Calendar Names", "kind": "naming_layer", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a direct Turkmen public month-name layer over Gregorian date structure, reflecting the 2002 reform-era naming set." }, { "key": "slavic_calendar_names", "display_name": "Slavic Calendar Month Names", "kind": "meta_unit", "status": "not_standalone", "track": "wikipedia_list_of_calendars", "notes": "Reclassified on purpose as an umbrella/family tracker rather than a plain naming-layer ticket. Concrete Slavic naming work should continue through narrower entries such as Polish, Czech, Lithuanian, and future language-specific layers." }, { "key": "thai_zodiac_month_names", "display_name": "Thai Zodiac Month Names", "kind": "naming_layer", "status": "implemented", "track": "wikipedia_list_of_calendars", "notes": "Implemented as a Thai zodiac-derived month-name layer over Gregorian month structure, kept distinct from the implemented Thai solar and Thai lunar calendar surfaces." }, { "key": "polish_folk_month_names", "display_name": "Polish Folk Month Names", "kind": "naming_layer", "status": "implemented", "track": "naming_layers_missing", "notes": "Implemented as a direct Polish folk month-name layer over Gregorian date structure." }, { "key": "czech_traditional_month_names", "display_name": "Czech Traditional Month Names", "kind": "naming_layer", "status": "implemented", "track": "naming_layers_missing", "notes": "Implemented as a direct Czech traditional month-name layer over Gregorian date structure." }, { "key": "finnish_pre_christian_month_names", "display_name": "Finnish Pre-Christian Month Names", "kind": "naming_layer", "status": "implemented", "track": "naming_layers_missing", "notes": "Implemented as a conservative Finnish traditional month-name layer over Gregorian date structure, not as a full reconstruction of older Finnish calendrical systems." }, { "key": "japanese_poetic_month_names", "display_name": "Japanese Poetic Month Names", "kind": "naming_layer", "status": "planned", "track": "naming_layers_missing", "notes": "Deferred on purpose. It should follow fuller Japanese traditional calendar context rather than a flat Gregorian month swap." }, { "key": "arabic_pre_islamic_month_names", "display_name": "Arabic Pre-Islamic Month Names", "kind": "naming_layer", "status": "planned", "track": "naming_layers_missing", "notes": "Deferred on purpose. It needs stronger historical/Islamic naming context than the current simple naming-layer contract provides." }, { "key": "dual_naming_systems", "display_name": "Dual Naming Systems", "kind": "meta_unit", "status": "not_standalone", "track": "naming_layers_advanced", "notes": "Reclassified on purpose as a naming-engine/product-capability tracker rather than an independent naming layer. It depends on a broader naming-profile and variant engine." }, { "key": "poetic_ritual_naming_layers", "display_name": "Poetic/Ritual Naming Layers", "kind": "meta_unit", "status": "not_standalone", "track": "naming_layers_advanced", "notes": "Reclassified on purpose as a naming-engine/product-capability tracker rather than an independent naming layer. It depends on a broader naming-profile and variant engine." }, { "key": "dialectal_calendar_vocabularies", "display_name": "Dialectal Calendar Vocabularies", "kind": "meta_unit", "status": "not_standalone", "track": "naming_layers_advanced", "notes": "Reclassified on purpose as a naming-engine/product-capability tracker rather than an independent naming layer. It depends on a broader naming-profile and variant engine." }, { "key": "script_based_calendar_variants", "display_name": "Script-Based Calendar Variants", "kind": "meta_unit", "status": "not_standalone", "track": "naming_layers_advanced", "notes": "Reclassified on purpose as a naming-engine/product-capability tracker rather than an independent naming layer. It depends on a broader naming-profile and variant engine." }, { "key": "etymological_naming_layers", "display_name": "Etymological Naming Layers", "kind": "meta_unit", "status": "not_standalone", "track": "naming_layers_advanced", "notes": "Reclassified on purpose as a naming-engine/product-capability tracker rather than an independent naming layer. It depends on a broader naming-profile and variant engine." }, { "key": "polynesian_navigation_calendars", "display_name": "Polynesian Navigation Calendars", "kind": "observational_framework", "status": "implemented", "track": "observational_frameworks", "notes": "Framework-first implementation now exists with explicit navigation/star-path provenance, locality dependence, and profile notes rather than a normalized civil calendar converter." }, { "key": "micronesian_star_calendars", "display_name": "Micronesian Star Calendars", "kind": "observational_framework", "status": "implemented", "track": "observational_frameworks", "notes": "Framework-first implementation now exists with explicit star-path provenance, locality dependence, and profile notes rather than a normalized civil calendar converter." }, { "key": "andean_agricultural_calendars", "display_name": "Andean Agricultural Calendars", "kind": "observational_framework", "status": "implemented", "track": "observational_frameworks", "notes": "Framework-first implementation now exists with explicit agricultural/ecological provenance, locality dependence, and profile notes rather than a normalized civil calendar converter." }, { "key": "ancient_egyptian_lunar_calendar", "display_name": "Ancient Egyptian Lunar Calendar", "kind": "observational_framework", "status": "implemented", "track": "observational_frameworks", "notes": "Framework-first implementation now exists as an explicit Egyptian lunar reconstruction surface with profile-driven provenance rather than a normalized public converter." }, { "key": "babylonian_observational_calendar", "display_name": "Babylonian Observational Calendar", "kind": "observational_framework", "status": "implemented", "track": "observational_frameworks", "notes": "Framework-first implementation exists with explicit scholarly profiles and provenance, but not a full normalized calendar converter yet." }, { "key": "greek_parapegmata", "display_name": "Greek Parapegmata Calendars", "kind": "observational_framework", "status": "implemented", "track": "observational_frameworks", "notes": "Framework-first implementation exists with explicit scholarly profiles and provenance rather than a single normalized civil calendar." }, { "key": "islamic_regional_moon_sighting", "display_name": "Islamic Regional Moon-Sighting Traditions", "kind": "observational_framework", "status": "implemented", "track": "observational_frameworks", "notes": "Framework-first implementation now exists with explicit locality, visibility, and authority dependence rather than a normalized Hijri converter." }, { "key": "eclipse_canon_systems", "display_name": "Eclipse Canon Systems", "kind": "observational_framework", "status": "implemented", "track": "observational_frameworks", "notes": "Framework-first implementation now exists with explicit chronology/provenance framing rather than a normalized civil calendar." }, { "key": "star_calendar_systems", "display_name": "Star Calendar Systems", "kind": "observational_framework", "status": "implemented", "track": "observational_frameworks", "notes": "Framework-first implementation now exists with explicit star-phase/seasonal provenance rather than a normalized civil calendar." }, { "key": "nomadic_seasonal_calendars", "display_name": "Nomadic Seasonal Calendars", "kind": "observational_framework", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface is registered and selectable; no universal nomadic seasonal converter is claimed." }, { "key": "river_cycle_calendars", "display_name": "River-Cycle Calendars", "kind": "observational_framework", "status": "implemented", "track": "observational_frameworks", "notes": "Framework-first implementation now exists with explicit environmental/locality dependence rather than a normalized civil calendar." }, { "key": "monsoon_calendars", "display_name": "Monsoon Calendars", "kind": "observational_framework", "status": "implemented", "track": "observational_frameworks", "notes": "Framework-first implementation now exists with explicit climatic/locality dependence rather than a normalized civil calendar." }, { "key": "pastoral_migration_calendars", "display_name": "Pastoral Migration Calendars", "kind": "observational_framework", "status": "implemented", "track": "observational_frameworks", "notes": "Framework-first implementation now exists with explicit ecological/locality dependence rather than a normalized civil calendar." }, { "key": "regnal_year_notation", "display_name": "Regnal Year Notation Alone", "kind": "meta_unit", "status": "not_standalone", "track": "meta_units" }, { "key": "liturgical_year_without_base_calendar", "display_name": "Liturgical Year Without Base Calendar", "kind": "meta_unit", "status": "not_standalone", "track": "meta_units" }, { "key": "season_only_systems", "display_name": "Season-Only Systems", "kind": "meta_unit", "status": "not_standalone", "track": "meta_units" }, { "key": "agricultural_schedules_without_absolute_dating", "display_name": "Agricultural Schedules Without Absolute Dating", "kind": "meta_unit", "status": "not_standalone", "track": "meta_units" }, { "key": "event_almanacs", "display_name": "Event Almanacs", "kind": "meta_unit", "status": "not_standalone", "track": "meta_units" }, { "key": "chronological_frameworks", "display_name": "Chronological Frameworks", "kind": "meta_unit", "status": "not_standalone", "track": "meta_units" }, { "key": "relative_dating_systems", "display_name": "Relative Dating Systems", "kind": "meta_unit", "status": "not_standalone", "track": "meta_units" }, { "key": "uncertain_ranges", "display_name": "Uncertain Ranges", "kind": "meta_unit", "status": "not_standalone", "track": "meta_units" }, { "key": "mythological_time_systems", "display_name": "Mythological Time Systems", "kind": "meta_unit", "status": "not_standalone", "track": "meta_units" }, { "key": "event_relative_time", "display_name": "Event-Relative Time", "kind": "meta_unit", "status": "not_standalone", "track": "meta_units" }, { "key": "chinese_jupiter_year_overlay", "display_name": "Chinese Jupiter Year Overlay", "kind": "overlay", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface for Chinese Jupiter-year material; live conversion remains blocked pending source-profile and Chinese calendar integration." }, { "key": "indian_brihaspati_cycle", "display_name": "Indian Brihaspati Cycle", "kind": "overlay", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface for Brihaspati-cycle material; live conversion remains blocked pending regional source-profile choices." }, { "key": "jupiter_orbital_cycle", "display_name": "Jupiter Orbital Cycle", "kind": "cycle", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface for orbital-cycle framing; no epoch-normalized daily converter is claimed." }, { "key": "jupiter_synodic_cycle", "display_name": "Jupiter Synodic Cycle", "kind": "cycle", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface for synodic-cycle/event framing; live output requires an event/profile anchor." }, { "key": "jovian_system_calendar_profile", "display_name": "Jovian System Calendar Profile", "kind": "calendar", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface for future Jovian-system calendar design; no gas-giant civil calendar is invented." }, { "key": "earth_planetary_baseline", "display_name": "Earth Planetary Baseline", "kind": "meta_unit", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public meta surface pointing back to implemented Earth systems rather than becoming a duplicate calendar." }, { "key": "mercury_planetary_calendar", "display_name": "Mercury Planetary Calendar", "kind": "calendar", "status": "implemented", "track": "future_research_profiled_overlays", "notes": "Profile-gated synthetic J2000 mean-solar Mercury projection is available only when explicitly selected; missing profile returns fallback metadata." }, { "key": "venus_planetary_calendar", "display_name": "Venus Planetary Calendar", "kind": "calendar", "status": "implemented", "track": "future_research_profiled_overlays", "notes": "Profile-gated synthetic J2000 mean-solar Venus projection is available only when explicitly selected; missing profile returns fallback metadata." }, { "key": "jupiter_planetary_calendar", "display_name": "Jupiter Planetary Calendar", "kind": "calendar", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface; gas-giant planetary calendars remain blocked by the lack of a surface/local civil frame." }, { "key": "saturn_planetary_calendar", "display_name": "Saturn Planetary Calendar", "kind": "calendar", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface; gas-giant planetary calendars remain blocked by the lack of a surface/local civil frame." }, { "key": "uranus_planetary_calendar", "display_name": "Uranus Planetary Calendar", "kind": "calendar", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface; gas-giant planetary calendars remain blocked by the lack of a surface/local civil frame." }, { "key": "neptune_planetary_calendar", "display_name": "Neptune Planetary Calendar", "kind": "calendar", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface; gas-giant planetary calendars remain blocked by the lack of a surface/local civil frame." }, { "key": "mars_darian_calendar_alignment", "display_name": "Mars Darian Calendar Alignment", "kind": "calendar", "status": "implemented", "track": "future_research_reference_surfaces", "notes": "Reference-only public surface that points to existing Darian/Mars support and documents alignment work without duplicating it." } ] }