What Is Clashing Lu (沖祿) in BaZi?
Learn the two documented Clashing Lu routes, repeated Yin or Shen requirement, absent Lu target, filling rule, stem damage and product limits.
Overview
Clashing Lu is the standard English name for 沖祿. The cited rule documents two routes. A Geng-Yin day needs another Yin in the year, month or hour and no visible Shen; the repeated Yin branches are interpreted as clashing toward Shen, Geng’s Lu. A Jia-Shen day needs another Shen and no visible Yin; repeated Shen is read as clashing toward Yin, Jia’s Lu. Visible Shen on the Geng route or visible Yin on the Jia route fills the target and ends the remote premise. Bing damaging Geng and Geng damaging Jia are also named blockers. The source says other cases may be inferred, but it does not provide a complete table, so OpenFate keeps only the two explicit routes and does not guess the rest. It calculates the actual clashes and counts but has no Clashing Lu detector.
At a glance
- Route 1
- Geng-Yin day plus another Yin; Shen absent
- Route 2
- Jia-Shen day plus another Shen; Yin absent
- Count rule
- The day branch repeats elsewhere
- Filling rule
- Visible target Lu ends the remote route
- Stem blockers
- Bing damages Geng; Geng damages Jia
- Product boundary
- No OpenFate Clashing Lu detector
The source explicitly gives only Geng-Yin and Jia-Shen
Geng’s Lu is Shen, directly opposite Yin; Jia’s Lu is Yin, directly opposite Shen. In both cases, the Day Branch must be repeated in another pillar so the old model can describe a joint clash toward the missing Lu branch.
One Yin on Geng-Yin or one Shen on Jia-Shen is only the Day Branch, not the repeated condition. The phrase “infer the rest” does not supply enough evidence to build additional Day-Pillar routes.
- Require the exact Day Pillar and a repeated matching branch.
- Do not extrapolate an undocumented complete map.
The target must be absent and the Day Stem undamaged
If Shen is visible on the Geng route or Yin on the Jia route, the Lu position is filled and no longer remotely clashed out. That direct Lu can still be interpreted normally, just not under this special premise.
The source additionally rejects Bing that damages Geng and Geng that damages Jia. Month command, actual Lu, ordinary clash evidence and the full strength structure remain more reliable than the rare label.
- Separate actual Lu from an inferred target.
- Check visible stem damage and ordinary structure first.
OpenFate counts the real branches without producing Lu
OpenFate can match Geng-Yin and Jia-Shen, count Yin and Shen, detect the real Yin-Shen clash, show Bing or Geng damage, and evaluate Lu, month command and Ten Gods.
It does not add a missing branch or output Clashing Lu. A safe detector needs the two-route allowlist, exact count, absence, filling and stem-damage states plus negative fixtures. Existing reports remain unchanged.
- Only visible Yin and Shen are chart data.
- Fail closed for every unlisted route.
Clashing Lu does not predict status or disaster
The pattern cannot prove rank, wealth, job outcomes, conflict, illness, accident or timing. Classical examples are not causal evidence.
Use current facts and qualified advice for employment, finance, law, relationships, health and safety.
- Exclude status and event guarantees.
- Present the model as historical interpretation.
Sources and editorial basis
- 《三命通會》 (Sanming Tonghui)卷六「沖祿」：庚寅日他柱重寅且申不見、甲申日他柱重申且寅不見，填實與丙傷庚、庚傷甲阻斷，餘例推未給完整表A historical compilation covering stems and branches, Ten Gods, Nayin, Shen Sha, and multiple classical pattern systems.
- OpenFate Editorial Methodology僅保留兩條明載路線、精確重支與缺席填實狀態、未列路線 fail closed，不生成祿支並排除地位財富衝突疾病事故應期保證OpenFate separates deterministic chart calculation, traditional interpretation, and modern editorial explanation.