How InnerCipher Calculates and Explains a BaZi Chart

InnerCipher separates chart calculation from report writing. A deterministic engine normalizes the birth input, calculates the chart facts, and applies the implemented BaZi rules first. Some report modules then use AI only as a writing layer, turning those established results into clear, readable prose. AI does not calculate the chart, apply divination rules, or replace stored facts.

What InnerCipher does—and does not do

InnerCipher creates a BaZi chart and a structured digital report from the birth information a user submits. The report can explain the Four Pillars, Day Master, Five Elements, Ten Gods, chart relationships, and timing themes available in the selected report mode.

It does not establish a fixed fate or guarantee an event. It does not know the full context of a person's life, and it cannot determine a health outcome, investment result, career decision, relationship decision, legal result, or any other real-world outcome. Report text should be read as interpretive material rather than an instruction to act.

Birth inputs used in calculation

The current report flow accepts:

• Gregorian birth date;
• known birth hour and minute, or an explicit “birth time unknown” choice;
• birthplace, including city, country, and optional region;
• the latitude, longitude, and IANA timezone associated with the selected place; and
• an optional gender selection used only where the current BaZi calculation rules require a gender mode.

The place search supplies coordinates and a timezone to the report request. These values matter because two places that show the same clock time may have different UTC offsets or longitudes.

How time is normalized

Timezone and daylight-saving rules

For a known birth time, the engine looks up the UTC offset for the submitted local date, hour, and IANA timezone using the JavaScript runtime's timezone data. This allows the offset to reflect the timezone rules available for that date rather than assuming the server's local timezone.

There are limits. Historical timezone data can vary between runtime datasets, and the current flow does not independently resolve every ambiguous clock time during a daylight-saving transition. If timezone lookup fails, the current engine falls back to UTC+8. A user with an unusual historical timezone case should verify the input and treat the result cautiously.

When the birth time is unknown

If the user explicitly marks the time as unknown, InnerCipher preserves that status and uses local noon (12:00) as a calculation fallback. Noon is not presented as the person's actual birth time. Because the hour pillar and some downstream interpretations depend on time, an unknown-time chart has a real precision limit.

True Solar Time

When longitude is available, the engine adjusts local civil time using the equation of time, longitude, and the UTC offset at the submitted birth time. The adjustment can move the effective calculation time—and, near midnight, the effective date—forward or backward. If longitude is unavailable, this adjustment is not applied.

After normalization, the calendar engine derives the lunar calendar context and the Four Pillars from the effective date and time. This includes the solar-term context used by the engine when it determines calendar boundaries. A small input change near an hour, day, or solar-term boundary can therefore change part of the chart.

What the deterministic engine calculates

The deterministic stage runs before any AI-assisted writing. It creates a fact snapshot that can include:

• the year, month, day, and hour pillars;
• the Day Master;
• Five Elements and Ten Gods records;
• branch relationships and Na Yin;
• calendar and zodiac context;
• Day Master strength, chart pattern, and useful-element classifications under the implemented rules; and
• luck-cycle and timing data used by enabled report modules.

These facts are stored with the report so later module generation uses the same snapshot. The report's locale is also stored with the report and controls report-module language independently of the current header language.

How AI supports report writing

AI is not involved in birth-time handling, True Solar Time adjustment, calendar conversion, Four Pillars calculation, or the application of BaZi rules. Chart facts and rule-based interpretive conclusions are completed and stored by the deterministic BaZi engine first.

For report modules that benefit from natural-language presentation, the system gives AI only the established facts, a defined scope, and specific writing slots as read-only context. AI organizes the wording, improves the flow, and makes the result easier to read. It cannot write back to chart facts, change a calculation, or introduce a new BaZi conclusion. The generated text must pass the module's structural schema before it is assembled with deterministic data.

This separation between chart calculation and written expression keeps the report's substantive content anchored to the deterministic BaZi engine. AI explains results that have already been established; it does not freely invent conclusions or participate in the divination process.

Traditional sources and interpretive choices

The InnerCipher team has studied BaZi for about five years. Its rule design draws on traditional materials including Yuan Hai Zi Ping, Di Tian Sui, Qiong Tong Bao Jian, Shen Feng Tong Kao, and Zi Ping Zhen Quan. The team has also spoken with practicing BaZi consultants about how written rules are combined in real readings.

Those sources do not form a single, universally agreed specification. Schools and practitioners can differ on rule priority, chart pattern, strength, useful elements, and interpretation. InnerCipher therefore implements a defined, internally consistent framework; it does not claim to represent the only valid school or to reproduce every consultant's judgment. The source relationship is at the framework level, not a claim that every generated sentence can be traced to one line in one text.

Review, changes, and corrections

The InnerCipher team reviews calculation rules, module definitions, public educational content, and generated-output behavior as the product changes. Individual reports are not reviewed by a human BaZi consultant before delivery.

We update this page when a material method or boundary changes. We do not change an updatedAt date merely to make a page appear fresh. If you find a possible chart error, translation problem, or unsupported claim, email support@innerciphers.com with the report link and enough detail to reproduce the issue.

Data handling is covered by the Privacy Policy. Product use, AI-output limits, payment terms, and disclaimers are covered by the Terms of Service. This page explains the method; it does not replace either policy.