BaZi Cue

Who we are

About BaZi Cue

A small, focused tool for exploring BaZi in your language—with the calculation, interpretation and uncertainty kept in view.

Understanding before prediction

Traditional BaZi has a rich vocabulary, but a page full of symbols can leave a newcomer with more questions than answers. BaZi Cue starts with a readable chart and builds toward explanations that show their reasoning.

We aim to explain what the tool computes, what a traditional interpretation adds, and where neither provides a reliable basis for decisions.

The product is designed for readers in all supported languages who want to learn the vocabulary without first accepting a prediction. A free calculation gives you a starting point; guides explain the parts; the complete sample lets you examine the reading format before deciding whether a personal explanation would help.

Quiet study scene with four stone columns, an open notebook and a leafy branch.
A chart is a starting point for learning. Its labels, assumptions and limits should remain easy to inspect.

What we make visible

How the explanations are assembled

  1. Start with a defined calculation. Calendar and time rules produce the pillars and relationship labels. The method and dependency versions remain visible.
  2. Keep observations traceable. Report sections refer back to chart facts. Counts, hidden stems and traditional meanings are explained as different kinds of information.
  3. Keep examples identifiable. The public sample uses fictional birth details and fixed explanatory rules. It is not a customer testimonial or an undisclosed AI output.
  4. State the limits beside the explanation. Reflection prompts are optional. Technical checks can catch some inconsistencies but do not prove the meaning of an interpretation.

This describes the product’s content structure. It is not a claim that every report is personally reviewed by an editor or practitioner. Questions about a specific result belong in the correction channel below.

Who is behind BaZi Cue?

Service operator

samlink

samlink is a BaZi enthusiast who collects and organizes related content and maintains this website.

BaZi Cue is the service brand. For product, order and privacy questions, contact support@bazicue.com.

Software, not a practitioner consultation

BaZi Cue is a software product. We do not claim a team of masters, personal practitioner consultations or expert review that has not taken place. The free preview and public sample use fixed rules; any AI-assisted report is identified as such.

BaZi is presented as a cultural framework for reflection. It is not a scientifically validated method for predicting health, finances or relationships.

How Our BaZi Chart Is Calculated

A chart is only useful when you know how it was calculated. Here are the calendar choices, time rules, verification limits and versions used by this tool.

The short version

Gregorian input · historical IANA time zones · solar-term year and month boundaries · midnight civil day · no solar-time correction. Software calculates the chart before any interpretation.

Calendar and boundary rules

Enter a Gregorian date between 1900 and 2099 and the local time recorded at birth. The year pillar changes at the exact start of spring (Lichun), rather than January 1 or Lunar New Year. Month pillars change at the twelve “Jie” boundaries; not every one of the twenty-four solar terms starts a new month.

The engine expresses solar-term times in a fixed UTC+8 reference clock. We convert that reference to an instant before comparing an international birth time. Your local calendar date remains the reference for the civil day.

Our day changes at 00:00 local civil time. At 23:00 the hour branch changes into Zi, but the day stem continues until midnight. The hour stem follows that same day stem. A school using a 23:00 day boundary can produce a different result near midnight.

Inputs are recorded to the minute, while astronomical references can differ by seconds. Within two minutes of a month-changing solar-term boundary, this version pauses the calculation for review. Do not change your birth time to bypass the message.

Landscape illustration showing one tree through spring, summer, autumn and winter.
Seasonal boundaries define the year and month pillars. The calculation uses exact solar-term instants; this illustration provides context rather than a calendar reference.

Time zones and daylight saving

Choose the IANA region for your birthplace, such as America/New_York or Asia/Shanghai. Your current time zone may not be the right one. Historical daylight-saving adjustments come from the recorded time-zone database; do not manually subtract an hour.

When clocks move forward, some local times never occur. Those inputs are rejected. When clocks move backward, a time can occur twice. You must select its first or second occurrence instead of the tool silently choosing one.

Historical time-zone records have limitations, particularly for older dates. The chart records the time zone, applied UTC offset, engine version and method version so you can inspect the assumptions.

How do I choose my birthplace time zone?

  1. Identify the town or region where the birth happened, even if you now live elsewhere.
  2. Choose its IANA time-zone region, such as America/New_York. The city in the identifier represents a region; your exact town does not have to appear in the list.
  3. Enter the local clock time as recorded. Do not convert it to UTC or manually remove daylight saving.
  4. If a repeated time requires a first or second occurrence, confirm that from the record before continuing.

The form accepts time-zone identifiers, not an automatic city-to-zone lookup. A country name or present-day UTC offset may not identify the correct historical zone. If uncertain, confirm which zone covered the birthplace on that date rather than guessing.

Return to the birth-details form

Solar-time correction

We use local civil time and do not apply true solar time or longitude corrections. A practitioner using another convention may obtain a different hour or day pillar near a boundary.

Birthplace is represented by a time-zone selection. A city name or device location is not used as a hidden longitude correction.

When birth time is unknown

This version requires a known birth time. It never replaces an unknown time with noon or another default. The hour pillar and calculations near a boundary would otherwise be uncertain.

You can read the fictional sample while looking for a record. Treat an approximate recollection as an uncertainty, especially near midnight or a two-hour boundary.

What the chart labels show

The Day Master is the Heavenly Stem of the day pillar. Ten Gods labels describe other stems relative to that reference using element and polarity relationships. Hidden stems are listed separately for each branch.

The Five Elements display counts the four visible stems and each branch’s main element: eight positions. Hidden stems are excluded. This is a distribution count, not a strength score, balance rating or recommendation to “add” a missing element.

We do not calculate automatic Day Master strength, a Useful God or a relationship score. The Four Pillars guide explains how to locate the parts.

Two-chart comparison

The comparison tool checks each of four positions in one chart against all four in another. It shows each Day Master’s Ten God label relative to the other, eight-position element counts, five stem-combination pairs, six branch-combination pairs and six opposing branch pairs.

Repeated matches belong to separate positions; they are not added into a score. No transformation, marriage verdict or prediction is inferred. Method: two-chart-pairs-v1.

Luck pillars and starting age

The luck pillar calculator requires an explicit traditional direction parameter. Under year-stem-polarity-v1, a Yang birth-year stem with the traditional male rule, or a Yin stem with the traditional female rule, runs forward to the next Jie. Other pairings run backward to the previous Jie. The parameter is not inferred from identity, and the public tool does not save it.

After conversion from the engine’s UTC+8 reference, the duration between birth and the relevant boundary is rounded down to whole minutes. The traditional three-days-to-one-year conversion maps 4,320 minutes to one year, 360 to one month, 12 to one day, and each remaining minute to two hours of starting age.

Starting years, months, days and hours are added in that order to the local birth calendar, clamping leap-day and month-end overflow. The results are civil dates, not newly resolved global instants. Ten-year periods advance from the month pillar one sexagenary pair at a time. End dates are exclusive; the pre-cycle birth interval is not cycle 1.

Method luck-pillars-utc-minute-v1 differs from two-hour rounding or dropping boundary seconds before subtraction. It provides a traditional sequence, not evidence of events during those periods.

Symbolic stars

Peach Blossom uses the year branch and day branch independently to identify a traditional target branch, then lists matching chart positions. Both reference choices remain visible. Other symbolic-star families are explained as concepts, not claimed as calculated features.

Sources and calculation checks

The calculation uses lunar-typescript; historical clock rules come through Moment Timezone’s copy of the IANA Time Zone Database. The current versions are listed below and recorded with saved charts.

Our calendar test fixtures compare selected dates with sxtwl_cpp. The libraries share astronomical roots, so agreement is useful cross-checking rather than wholly independent proof. The Hong Kong Observatory’s 2024 calendar checks the calendar date of Start of Spring; that day-level source does not establish a second-level boundary.

Regression checks cover midnight and late-Zi hours, solar-term boundaries across time zones, daylight-saving gaps and repeats, non-hour offsets, invalid dates, hidden stems and the eight-position count. Passing these checks supports the tested calculations; it does not validate traditional interpretations or guarantee every historical record.

How to compare a result

  1. Match the input. Use the same Gregorian date, recorded time and birth-region time zone. Check any earlier/later daylight-saving choice.
  2. Match the convention. Compare midnight versus 23:00 day changes, civil versus solar time, and solar-term versus lunar-calendar year/month boundaries.
  3. Locate the difference. Record which pillar or label differs. A different hidden-stem table is a different question from an hour changed by a time adjustment.
  4. Keep the method version. For a private report, include its ID and the observed difference in a support request. Do not put birth records into public screenshots or URLs.

Which part of the chart is different?

Use this table to choose the first check, not to diagnose a cause from one symptom. More than one convention can affect the same result.

First checks when two BaZi results disagree
DifferenceCheck firstOur convention
Year pillarGregorian input and the year boundary, especially near Lichun.The exact Lichun instant changes the year.
Month pillarThe month-changing solar term and its conversion to the birth instant.The twelve Jie change the month; a two-minute boundary window requires review.
Day pillarThe local date, civil versus solar time, and 23:00 versus midnight rollover.The day changes at local civil midnight, without solar-time correction.
Hour branchRecorded hour and minute, historical zone, daylight saving and time corrections.Local civil two-hour intervals, with gaps rejected and repeats explicitly resolved.
Hour stem onlyThe day stem used to derive it, especially between 23:00 and midnight.The hour stem follows the same civil day stem as the day pillar.
Element counts or interpretation onlyWhether hidden stems or weights are included, and which interpretation method is used.Eight visible/main-branch positions, no strength weights; interpretation is a separate layer.

Check the hour intervals or trace an element count to its chart positions. If the same inputs and conventions still disagree, keep the method versions and report the specific difference.

The role of AI

Software calculates the chart before requesting a personal AI explanation. The model receives chart facts and reporting instructions, not a task to invent pillars from a birth date.

The free preview and public sample use fixed explanatory rules. AI-assisted reports are labeled separately. AI can still make mistakes; structured output and fact-reference checks are not complete semantic verification or scientific validation.

Versions and corrections

Published method changes
DateChangeCharts affected
Added structural comparison, minute-based luck pillar sequences and year/day Peach Blossom identification.The corresponding public tools. The natal chart method remains unchanged; existing saved reports are not rewritten.

Current calculation versions

Methodcivil-midnight-v1
Calculation enginelunar-typescript@1.8.6
Time-zone datamoment-timezone@0.6.6/IANA-2026f
Day boundary00:00 local civil time
Solar-time adjustmentNot applied

Saved reports retain their original chart and method versions. A later method change does not silently overwrite a purchased report. A correction should identify the affected report and explain what changed.

A little more clarity

Frequently asked questions

Which part of my chart should I compare first?

First match the Gregorian date, recorded time, birthplace time zone and any repeated-time selection. Compare the eight characters before comparing interpretations. Locate the differing pillar, then check its calendar and time conventions.

Find the first checks for a differing pillar

Why can two calculators show different charts?

Compare Gregorian input, historical time-zone handling, exact solar-term boundaries, civil versus solar time, and 23:00 versus midnight day changes. A different convention is not automatically a software error.

Do you apply true solar time?

No. The tool uses local civil time in the selected IANA time zone. It does not apply longitude or true-solar-time corrections. That choice is recorded in the chart method.

Can I use an unknown or approximate birth time?

A known time is required. We do not insert noon or infer an hour. An approximate recollection may change the hour pillar or a result near a boundary; use the fictional sample while checking a record.

Does the calculator accept a lunar calendar date?

No. Enter a Gregorian date. A lunar calendar date must be independently converted before using this version.

Will a new method automatically replace my report?

No. A saved report remains tied to its recorded chart and method version. Contact support if you believe a correction is needed.

Help us make it clearer

If a calculation looks inconsistent or an explanation needs work, use the contact and correction channel. Identify the page or report, the statement you are questioning, and the method version where relevant. Share private birth details only through an appropriate private support channel.

The method history distinguishes a calculation change from a change to explanatory wording. Existing saved reports retain the chart and version used to create them.

Last updated .