BaZi Basics: Build Your Chinese Astrology Chart from Scratch

BaZi Basics: Build Your Chinese Astrology Chart from Scratch: Verified Field Ledger

The engine’s verified field ledger confirms that the public API exports four-pillar computation; branch, stem, and pillar interactions; strength with score and root count; pattern; useful-god lenses; shensha with pillar placement and category; luck cycles with stems, branches, ten-god labels, ages, and years; annual, monthly, daily, and hourly ladders; cross-chart interactions; lunar conversion; and timing ratings. Outside the export boundary are bone-weight calculation, name recommendation, exam-result prediction, and deterministic event prediction. Committed worked witnesses provide concrete examples, but those witnesses never function as deterministic event predictors. For direct exploration of these verified fields, see the relevant page.

Input and Pillar-Position Check
Before reading, verify every field: birth year, month, day, hour, and the chosen calendar. The engine converts the lunar input to its solar equivalent, then computes four pillars—year, month, day, and hour—each with a stem and a branch. Check that the hour pillar matches the recorded birth time; a missing or shifted hour changes the chart. Confirm the day pillar is the chart’s reference point. The engine outputs branch, stem, and pillar interactions, strength with score and root count, pattern, useful-god lenses, and shensha with pillar placement. It also provides luck cycles and timing ratings. It exports no event predictions. For a full walkthrough, see BaZi basics.

Same-Chart Interaction Comparison: Field-by-Field Verification

To verify a BaZi reading, compare two charts sharing an identical four-pillar structure using only engine-exported fields. First, confirm the four pillars match exactly: year, month, day, and hour stems and branches. Next, align branch, stem, and pillar interactions—each should reproduce the same combination, clash, or harm labels. Verify strength is identical, including score and root count. The engine’s pattern label must match. Useful-god lenses should list the same elements. Shensha must agree on pillar placement and category. Luck cycles must show equal stems, branches, ten-god labels, ages, and years. Annual, monthly, daily, and hourly ladders must align. Cross-chart interactions and lunar conversion outputs must match. Timing ratings should be identical. Any mismatch indicates a boundary case outside the engine’s scope, not a deterministic event prediction. See relevant page for a full field walkthrough. The engine does not export bone-weight, naming, exam, or event predictors, so exclude those from comparison.

Strength and Pattern: Field-by-Field Verification

To verify strength and pattern without a chart, inspect each exported field against its defined boundary. Begin with strength: it must be an object containing score and rootCount. Confirm score is a numeric value; if missing or non-numeric, mark the chart as incomplete. rootCount must be a non-negative integer representing branch roots feeding the day master—zero is a valid weak case.

Next, check pattern. It must be a string from the engine’s pattern set; if absent or empty, do not infer a pattern. Cross-verify: a high score with zero rootCount is a boundary case where pattern may still output, but do not assume strength. For details on interpreting strong vs. weak day masters, see relevant page.

BaZi Basics: Build Your Chinese Astrology Chart from Scratch: Luck-Cycle Record: Field-by-Field Verification

Open a computed luck-cycle record and verify each field against the engine's declared exports. The top-level list must contain entries with stems and branches matching the lunar-conversion output; if a year repeats or skips, flag it as a boundary case. For every cycle, confirm the ten-god label exists in the stem interaction set and that ages and years align with the luck-cycle ladders. Check that annual, monthly, daily, and hourly ladders are present and that each ladder entry carries a timing rating—not a deterministic event prediction. If a record includes shensha, ensure each has a pillar placement and category. Finally, cross-chart interactions should appear only when a second chart is supplied; otherwise, mark the field as absent. For a field-by-field walkthrough, see relevant page.

Field-by-Field Verification of Other Reported Labels

When reviewing a BaZi report, treat every label beyond the engine’s exported fields as unverified. Start by checking whether the claim maps to an exported field: four pillars, stem/branch/pillar interactions, strength with score and root count, pattern, useful-god lenses, shensha with pillar placement and category, luck cycles with stems, branches, ten-god labels, ages, years, annual/month/day/hour ladders, cross-chart interactions, lunar conversion, or timing ratings. If it does, verify the value matches the computed output. If it does not, flag it as unsupported. For example, a bone-weight calculator, naming recommender, exam-result predictor, or deterministic event predictor is not exported. The engine exports no deterministic event predictions. Treat any "prediction" as a boundary case: disallowed. For exported fields like ten-god labels, confirm they appear in luck cycles or pillar interactions. If a report shows a ten-god label outside those contexts, mark it as unverified. Do not accept extra categories of shensha beyond the exported pillar placement and category. This field-by-field check prevents mistaking decorative text for engine output.

To audit missing capabilities, verify field-by-field against the engine exports. Check for four pillars, branch/stem/pillar interactions, strength with score and root count, pattern, useful-god lenses, shensha with pillar placement and category, luck cycles with stems, branches, ten-god labels, ages and years, annual/month/day/hour ladders, cross-chart interactions, lunar conversion, and timing ratings. For each field, confirm presence and reject unexported outputs such as bone-weight calculation, naming recommender, exam-result predictor, or deterministic event predictor. Use only committed worked witnesses as concrete examples. If a requested field is absent, mark it missing. See relevant page.

To test a BaZi engine's verifiable scope, inspect each exported object against the computed contract. Four pillars require stem-branch pairs for year, month, day, and hour; any missing pair or altered sexagenary index is a boundary failure. Interaction fields must produce only relations among branches, stems, or pillars—no standalone advice. Strength must return a score and root count, not a narrative. Pattern and useful-god lenses should output labels only. Shensha must include pillar placement and category. Luck cycles need stems, branches, ten-god labels, ages, and years. Ladders require annual, monthly, daily, and hourly steps. Cross-chart interactions compare two charts. Lunar conversion maps Gregorian to lunar. Timing ratings return ratings. Any output resembling bone-weight, naming, exam, or deterministic event prediction falls outside verified exports and should be rejected as non-verifiable.

BaZi Basics: Build Your Chinese Astrology Chart from Scratch: Reader Audit Procedure

To verify a BaZi report, check each field against the engine's exported scope. First, confirm the four pillars include stems and branches, not only zodiac animals. Next, inspect interactions between stems, branches, and pillars; if absent, flag as incomplete. Strength must show a numeric score and root count, not merely a label. Pattern must name a specific formation; vague terms fail. Useful-god lenses should list which elements or gods serve the chart, without predicting events. Shensha entries need pillar placement and category; unplaced stars are invalid. Luck cycles must include stems, branches, ten-god labels, ages, and years. Annual, month, day, and hour ladders require complete stems and branches. Cross-chart interactions must reference two charts. Lunar conversion must state the data source. Timing ratings need a defined scale. Reject any claim of bone-weight, naming advice, exam results, or deterministic events—these are outside engine exports.

Input-to-Output Comparison: Verifying the Engine’s Scope

To verify a BaZi computation, map each input field to its exported output. The engine accepts the four pillars as input and returns branch, stem, and pillar interactions; strength with score and root count; pattern; useful-god lenses; shensha with pillar placement and category; luck cycles with stems, branches, ten-god labels, ages, and years; annual, monthly, daily, and hourly ladders; cross-chart interactions; lunar conversion; and timing ratings. A boundary case: if the input is a birth date, the output includes lunar conversion, but no bone-weight calculator, naming recommender, exam-result predictor, or deterministic event predictor. Cross-check each field against the committed worked witnesses; any output beyond the listed exports is out of scope.

How to Fact-Check Your BaZi Chart Output

To verify a BaZi chart against committed engine outputs, check each field in sequence:

1. Four pillars: Confirm each pillar includes a stem and a branch, with no additional derived labels.
2. Branch, stem, and pillar interactions: Ensure only exported interaction types are listed.
3. Strength: Verify the score is present and the root count is numerically consistent.
4. Pattern: Ensure the pattern name matches one of the exported pattern outputs.
5. Useful-god lenses: Confirm only lens categories from the engine are used.
6. Shensha: Validate pillar placement and category for each entry.
7. Luck cycles: Cross-check stems, branches, ten-god labels, ages, and years against the exported ladder.
8. Annual, monthly, daily, and hourly ladders: Verify they are ladders, not event predictions.
9. Cross-chart interactions: Confirm only exported interaction types are referenced.
10. Lunar conversion and timing ratings: Check they are present and within expected formats.

Any claim resembling a bone-weight calculator, naming recommender, exam-result predictor, or deterministic event predictor fails the audit immediately.