Clashed Timing
Last updated 5/21/2026
A clashed line is unstable. The clash has disturbed it, opened it, struck it, or split its force. Timing asks when that instability settles.
The mirror rule is simple: clash creates instability; combination can stabilize it.
This does not mean every combination is useful. The stabilizing branch must either neutralize the branch doing the clashing or directly steady the target branch.
The target is struck by a branch that opposes it. The line cannot be treated as calm.
A combining branch can neutralize the attacker or support the target's own branch family.
Two stabilizing routes
If a day combines with the branch doing the clashing, it can tie up the disturbance.
If a day combines with the target itself, it can steady the line directly.
When both routes exist, choose the earlier and stronger route, then tag confidence honestly.
This state is not the same as Month Breaker. A line can be clashed and shaken without being seasonally broken. Month Breaker belongs to the line-usability layer and outranks ordinary clash timing. Ordinary clashed timing is for a usable line whose immediate instability needs to settle.
Example
Suppose the target is Rabbit and Rooster day clashes it.
The target is disturbed by the day branch.
Dragon combines with Rooster, so it can bind the attacker.
Dog combines with Rabbit, so it can stabilize the target.
Use the earlier clean date as primary and carry the other as backup if it is relevant.
Traps
A second clash can activate in some contexts, but it is not the usual stabilizer for an already clashed target.
The combination must actually neutralize the attacker or support the target. A decorative combination is not timing.
A strong clashed line and a weak clashed line do not carry the same confidence.
When both stabilizing routes are available, choose the earlier mechanically clean date as primary and carry the other as a backup. If the target is weak, lower confidence; a weak clashed line may be damaged rather than productively activated.
Watch for the bound trap. A date that “stabilizes” the target by combining with it may simply bind it into the next problem. If the combination would lock the target, treat that candidate as a bound-state transition, not a clean resolution.