BAZI KNOWLEDGE BASE
Do combinations and clashes change Fate Stars? Separate lookup from interaction
Combinations, clashes, punishments, harms and breaks do not recalculate one Fate-Star table into another. A marker matches through its anchor and target; what later happens to its carrier is a second layer. This prevents simplistic claims that a clash erases a marker or a combination makes it favorable.
A lookup match and a contact are separate records
The first record holds marker, anchor, target and matched pillar. The second records which actual stems or branches contact each other and in which time layer. The original lookup remains reproducible when the second record changes.
Discuss relevance only when the same carrier or a clear stem-branch path is involved. A clash elsewhere does not erase every Fate Star.
Month Yin is Horse and annual Shen clashes it: three steps
First confirm that the natal Year or Day Branch (the lower symbol in the birth-day column) table targets Yin and that Month Yin exists. In a Shen year, record annual Shen clashing natal Month Yin. If the question concerns travel or work change, then inspect real plans, Month-Pillar (the two-symbol column for the birth month) structure and other timing evidence.
The Horse match does not vanish from the natal record, and the Shen clash does not guarantee relocation. Without a relevant question, the contact may stay outside the conclusion.
Why a combination does not automatically resolve a marker
Combinations have participating symbols, locations, seasonal conditions and separate transformation requirements. A combination involving the carrier does not automatically make an adverse label favorable or permanently strengthen a favorable one.
Resolution is also an action word. Real risk calls for planning, communication, medical, legal or safety measures; a stem-branch combination cannot supply them.
When is a contact worth mentioning?
It earns narrative attention when the Fate-Star lookup is reproducible, the contact reaches the same carrier, the time layer is clear and the user’s question is relevant. Missing conditions call for weaker wording or a technical-only record.
A contact supplies context, not a plus-or-minus button.