Common Mistakes in Hidden-Stem and Root Analysis
Avoid the most common Bazi hidden-stem and rooting errors, from counting characters and fixed percentages to deleting roots and mixing natal with transit layers.
Overview
Common mistakes in hidden-stem and root analysis include treating each branch as one element, assigning one Ten God to a multi-stem branch, using fixed percentages as universal truth, confusing exposure with rooting, deleting roots after any interaction, and merging natal and timing layers. A reliable workflow keeps canonical data, policy, adjustments, and interpretation separate.
At a glance
- Data error
- Collapsing a multi-stem branch into one symbol
- Formula error
- Treating one percentage table as universal
- Concept error
- Confusing exposure, roots, and strength
- Interaction error
- Deleting a root after any combine or clash
- Time error
- Overwriting natal facts with luck-cycle states
- Safety error
- Turning technical labels into life guarantees
Do not corrupt the hidden-stem table
Keep every hidden stem, its polarity, and its ordered layer. A branch with three stored stems can produce three different Ten God relations.
Translation, UI compression, and scoring must never change canonical membership.
- Test all twelve branches.
- Preserve each hidden stem independently.
Separate existence, exposure, rooting, and strength
A hidden stem can exist without being exposed; a visible stem can be rootless; a rooted stem can still be weak; and a strong element can be unfavorable to the question.
Use a staged analysis instead of one label that silently combines all four concepts.
- One field per concept.
- Do not infer strength from visibility.
Never apply all-or-nothing interaction shortcuts
Combination, clash, punishment, break, Harm, Void, and timing each have different conditions. None should automatically erase the base branch table.
Keep natal data immutable, resolve interaction topology, apply bounded adjustments, and show remaining support.
- Use relation-specific rules.
- Preserve an audit trail.
Keep interpretation proportional and safe
Technical root language does not diagnose personality, health, family, money, or future events. Avoid fear-based translations such as “uprooted means loss.”
Explain limitations, link to definitions, and use real evidence and qualified advice for consequential decisions.
- No deterministic biography.
- Make uncertainty visible.
Sources and editorial basis
- 《淵海子平》 (Yuanhai Ziping)月令、旺衰、透藏與行運諸論支持先固定原局資料，再按條件比較根質，而不是只數根或用運改寫原局A foundational Ziping reference for branch months, hidden stems, roots, and stem-branch relationships.
- 《三命通會》 (Sanming Tonghui)卷二有根無根、支中藏氣、合沖刑害及行運例顯示各機制須分開驗證，不能一律作刪除或固定比例A historical compilation covering stems and branches, Ten Gods, Nayin, Shen Sha, and multiple classical pattern systems.
- OpenFate Editorial Methodology常見誤區頁把資料、方法、時間層與解釋分離，禁止由根氣直接診斷人格、健康、財富、關係或未來事件OpenFate separates deterministic chart calculation, traditional interpretation, and modern editorial explanation.