Calendar Reforms and Historical Dates in Bazi
Handle historical Bazi dates by verifying the local calendar reform, skipped dates, record provenance and time rules before calculating the chart.
Overview
Historical birth dates cannot always be entered as if they came from today’s Gregorian calendar. Calendar reforms were jurisdiction-specific, could omit a sequence of local dates, and sometimes left records marked Old Style or New Style. Safe Bazi calculation preserves the source transcription, identifies the calendar and place in force, validates that the written local date existed, and converts it to a continuous instant before applying time-zone, solar-term and Day-Pillar rules. When the evidence does not settle the calendar style, the honest result is a small set of labeled candidates, not a hidden automatic correction.
At a glance
- Required evidence
- Place, source date and calendar style
- Reform behavior
- Local dates could be skipped
- Adoption
- Different across jurisdictions and institutions
- Canonical timeline
- Continuous day and instant after validation
- Unresolved style
- Return explicit candidate charts
- Never do
- Silently rewrite the source record
Start with the document and jurisdiction, not a modern date picker
Transcribe the date exactly as recorded and capture birthplace, record location, language, institution and any Old Style or New Style notation. Those details can determine which calendar the writer intended.
A modern database may normalize an archival date without preserving its original style. Prefer the primary record or a documented scholarly conversion when available.
- Keep an image or citation for the source.
- Separate transcription from normalized fields.
Verify that the local date existed during the reform
When a jurisdiction adopted a revised calendar, one written date was followed by a later date, leaving an interval that did not exist in that civil system. The size and timing of the omission varied.
An impossible local date should trigger review rather than automatic rollover. It may indicate the other calendar style, a transcription error or a record from a different jurisdiction.
- Validate against the local reform table.
- Do not normalize a skipped date silently.
Normalize chronology before applying Bazi-specific rules
After identifying the calendar, convert the source date to a continuous day count and combine it with the best-supported local time. Then resolve historical clock rules and compare exact solar-term and day boundaries.
This ordering prevents a calendar correction, UTC offset and solar-time correction from being combined into one opaque shift. Each intermediate value remains independently testable.
- Run calendar conversion before zone conversion.
- Keep stage-by-stage audit fields.
Publish the uncertainty when the record cannot support one chart
If two calendar interpretations remain plausible and produce different pillars, show both with their source assumptions and exact differences. If they produce the same Four Pillars, explain that the chart is stable despite the unresolved label.
Do not rectify the calendar by selecting the chart that best matches a biography. Biographical comparison can be a later interpretive exercise, not evidence that rewrites the archival date.
- Limit candidates to evidence-supported possibilities.
- Never choose by narrative fit alone.
Sources and editorial basis
- U.S. Naval Observatory: Julian Date Converter美國海軍天文台的日序換算提供格里曆與儒略曆日期到連續時間軸的獨立轉換基準An official astronomical reference for converting Gregorian and Julian calendar dates to a continuous Julian Date timeline.
- IANA Time Zone Database曆法日期定位完成後，IANA 歷史規則再負責出生地鐘點與 UTC 偏移；兩個步驟不可混成單一位移The maintained reference for historical local-time rules, UTC offsets, and daylight-saving transitions by location.
- OpenFate Editorial Methodology產品保留原始文件、司法轄區與曆法版本；遇到略過日期或版本未定時停止靜默正規化並公開候選假設OpenFate separates deterministic chart calculation, traditional interpretation, and modern editorial explanation.