Stem-Branch Relationships in Bazi Cases
Map every Bazi case relation by participants, positions, direction, formation, transformation, competition, layer, and structural consequence.
Overview
Stem-branch analysis in a Bazi case requires more than listing combinations, clashes, punishments, harms, or breaks. Create a relation table that names every participant, pillar position, natal or timing ownership, direction, distance, completeness, and relevant season or transformation condition. Separate detection from effect: a relation may be present but incomplete, redirected, blocked, competing, or structurally neutral. Then explain which root, revealed stem, palace, Ten-God function, or structure is affected and what evidence supports that consequence. Traditional relation names do not literally prove harmony, conflict, injury, betrayal, marriage, movement, or an event.
At a glance
- Detection fields
- Participants, positions, ownership, direction, distance, and layer
- Formation fields
- Completeness, season, support, transformation, and obstruction
- Competition fields
- Multiple relations, shared members, priority, and cancellation policy
- Effect fields
- Root, revelation, palace, Ten God, structure, or timing function
- Required separation
- Relation detected versus consequence established
- Cannot prove
- Harmony, betrayal, injury, marriage, movement, or event
Inventory every participant and relation
List all natal stems and branches with pillar positions, then add timing influences as separately owned layers. Generate each relation from a declared rule table.
Retain relations that share a member instead of choosing one silently. Record direction and distance where the method uses them.
- Publish a complete relation table.
- Keep natal and timing ownership visible.
Test completion and transformation conditions
For combinations and groups, list required members, missing members, season, support, obstruction, and transformation criteria. For clashes and other relations, identify the exact pair and scope.
Do not equate relation detection with disappearance or transformation. A member may remain active under the adopted method.
- Separate relation from transformation.
- Show incomplete and contested states.
Trace the structural consequence
Identify which root, hidden or revealed influence, Ten-God function, candidate structure, palace, or timing dependency is changed and through what rule.
If the case event is already known, do not infer the consequence solely because its wording resembles the relation name. Require the intermediate chart logic.
- One effect needs one traceable chain.
- Do not use event wording as proof.
Keep relation names non-literal
Combination does not prove harmony, clash does not prove conflict, punishment does not prove crime, harm does not prove injury, and break does not prove separation.
Use direct evidence for conduct, safety, health, law, and relationships. The chart relation can frame a technical question, not establish a real-world event.
- No literal translation into events.
- No accusation or safety decision.
Sources and editorial basis
- 《三命通會》 (Sanming Tonghui)《三命通會》的干支合沖刑害、柱位與歲運材料提供具名關係、參與符號及使用層次的傳統依據A historical compilation covering stems and branches, Ten Gods, Nayin, Shen Sha, and multiple classical pattern systems.
- 《淵海子平》 (Yuanhai Ziping)《淵海子平》的干支、十神、六親與格局材料用於把關係放回根氣、宮位及結構功能，不只列名稱A foundational Ziping reference for branch months, hidden stems, roots, and stem-branch relationships.
- OpenFate Editorial Methodology案例干支關係頁把偵測、成立、合化、競爭和作用分開，禁止把合沖刑害破直接字面化為現實事件或指控OpenFate separates deterministic chart calculation, traditional interpretation, and modern editorial explanation.