What Is Chasing Lu and Blocking Horse (趕祿攔馬) in BaZi?
Learn the Jia-Xu, Ding-Chou and Gui-You source example, adjacent Lu-Horse imagery, why direct Lu or Horse is not required and the method’s limits.
Overview
Chasing Lu and Blocking Horse is the workbook’s English name for 趕祿攔馬. Its source gives one compact example rather than a complete general algorithm. For a Jia-Xu year person, Jia’s Lu is at Yin; Ding-Chou is said to “chase” it because Chou stands immediately before Yin. Xu’s Traveling Horse is at Shen; Gui-You is said to “block” it because You stands immediately after Shen. The source emphasizes that the direct Lu or Horse branch need not appear: neighboring positions symbolically bring or retain them. It then calls the pattern extremely noble, but does not fully specify how to generalize stems, direction, duplicates or conflicts across every chart. OpenFate therefore documents the example without detecting the pattern or creating virtual Yin and Shen branches.
At a glance
- Source person
- Jia-Xu year
- Lu position
- Jia Lu is at Yin
- Chasing example
- Ding-Chou stands before Yin
- Horse position
- Xu Horse is at Shen
- Blocking example
- Gui-You stands after Shen
- Product boundary
- No OpenFate chasing-blocking detector
The text explains one adjacency example, not a full lookup table
The explicit chain is Jia-Xu person → Jia Lu at Yin → Ding-Chou before Yin, and Xu Horse at Shen → Gui-You after Shen. The neighboring branches supply the chasing and blocking imagery.
The source says direct Lu and direct Horse are unnecessary, so the method cannot be reduced to ordinary marker presence.
- Keep the Jia-Xu example intact and ordered.
- Do not replace neighboring positions with direct Lu-Horse presence.
Unstated generalization rules must remain unstated
The short passage does not give a complete table for all year pillars or resolve how stems, cycle direction, duplicate neighbors, clashes and Void change the result.
A responsible article may explain the recorded example and literal branch adjacency, but it must not manufacture a universal detector from one case.
- Label the evidence as one source example.
- Treat missing derivation policy or conflicts as unclassified.
OpenFate does not add the absent Lu or Horse branch
The engine preserves the four actual pillars and any independently implemented Lu or Traveling Horse marker.
There is no Chasing Lu and Blocking Horse detector. Yin, Shen or other missing branches are not injected into interactions, strength, reports or saved charts.
- Actual pillars remain the deterministic chart.
- No virtual branch, marker, score or report mutation.
Chasing and blocking imagery cannot promise wealth or control
The source calls the example extremely noble and says Lu is activated while Horse is retained. That is historical rhetoric, not a verified mechanism.
Do not infer salary, wealth, career, social rank, control, travel, relocation, legal outcomes, safety, health or lifespan. Use direct evidence for consequential decisions.
- No wealth, salary, rank, career or control guarantee.
- No travel, legal, safety, health or lifespan prediction.
Sources and editorial basis
- 《三命通會》 (Sanming Tonghui)《古今圖書集成》藝術典第609卷所錄《三命通會》「趕祿攔馬」：甲戌年人甲祿在寅、丁丑居寅前為趕祿，戌馬在申、癸酉居申後為攔馬，正祿正馬不必直接出現的一則相鄰位置命例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.