Month Breaker: Detection and Qualification
Last updated 10/7/2026
A line is a Month Breaker candidate when its branch clashes the month branch. Detection is mechanical; the condition’s practical qualification requires a located rule.
Detection record
| Condition | Course record |
|---|---|
| month does not clash line | not Month-Broken |
| month clashes line | Month Breaker candidate |
| day branch equals the line | day-value condition also present |
| line moves, combines, is filled later, or belongs to a limited temporal scope | retain the condition and locate the rule before classifying it |
The “Month Breaker” chapter of Zengshan Buyi argues against treating every month-clashed line as permanently useless. It discusses movement, later filling, combination, and temporal scope. These are qualified textual arguments, not a universal rescue list.
Worked state: Case 00035 line 5
Example type: documented chart mechanics.
The month branch is Chen and line 5 carries Xu. Chen and Xu clash. The day is Mao, not Xu.
| Check | Result |
|---|---|
| Month clash | Chen–Xu |
| Day branch | Mao, not Xu |
| Line movement | moving |
| Additional relation | Mao–Xu combination |
| Permitted conclusion | Month Breaker candidate with movement and combination also present |
Keep every fact on the worksheet. To claim that movement or Mao–Xu combination qualifies the month clash, cite the applicable passage and explain why its conditions match this line. Otherwise record the effect as unresolved.
Repair contrast
Example type: invented mechanics exercise.
Keep Chen month and Xu line, but change the day branch to Xu. The month clash remains observable, and the line now also receives the day branch.
Record month clash: Chen–Xu and day value: Xu separately. If a located source or declared lineage rule treats day value as qualifying this Month Breaker condition, name that rule. The chart facts alone do not prove a universal repair.
Source boundary
Write the record this way:
month clash: exact pair → other conditions retained → located rule and locator → qualified / unqualified / unresolved
Trap and stopping condition
- Do not call a Month-Broken line literally destroyed or permanently absent.
- Do not let ordinary support silently erase the month clash.
- Do not turn one source case into a universal repair list.
- Stop if a qualifying claim lacks an applied rule and locator.
Source note
Received rule and dispute: Zengshan Buyi, “Month Breaker” (月破章), chapter 34, checked composite printed p. 50 onward. The three-way result—qualified, unqualified, or unresolved—is UAYA worksheet vocabulary, not a classical taxonomy.
Next, classify day clash without merging two rule sets: Day Breaker vs Dark Moving.