Clashed Timing
Last updated 10/7/2026
Your task is to record both sides of a clash and test whether an attributed timing rule supplies a stabilization candidate. You need the selected line’s branch and the opposing branch; without either one, stop.
This lesson calculates state stabilization candidates. It does not claim that a real-world matter is resolved on one of those dates.
The clash must belong to the selected line or to an explicitly related line being followed for a stated reason. A clash elsewhere in the chart does not become this subject’s timing relation.
A bounded UAYA comparison
No public locator used in this course establishes a universal four-route order for clashed lines. UAYA therefore uses the following comparison only as a transparent worksheet. It becomes a timing rule only when a cited source or named lineage supplies the combination premise.
| Side of the clash | Branch to preserve | Possible comparison if the cited rule calls for combination |
|---|---|---|
| Selected line | subject branch | fixed partner that combines with the subject branch |
| Opposing influence | clashing branch | fixed partner that combines with the opposing branch |
Invented calculation: Mao clashed by You
Invented illustration; no outcome. Let the subject branch be Mao and the stored clashing branch be You.
subject branch: Mao
opposing branch: You
source or lineage rule authorizing combination timing: not supplied| Symbolic branch | Derivation | Timing status |
|---|---|---|
| Xu | Xu combines with subject Mao | structural comparison only |
| Chen | Chen combines with opposing You | structural comparison only |
The branch table alone does not authorize a Gregorian window. With no attributed timing rule supplied, the correct output is no window. If a later source or named lineage explicitly authorizes one of these routes, record its exact scope and then use the calendar anchor to derive dates.
Distinguish three questions
| Question | This page’s answer |
|---|---|
| Was a clash relation recorded on the selected line? | Observable chart input |
| Which branches combine with either side? | Reproducible structural comparison, not automatically a timing rule |
| What happens in the matter? | Not answered by this timing calculation |
Traps and stops
- A combination elsewhere in the chart is irrelevant unless it combines with the subject or the stored clashing branch.
- A second clash is not automatically a stabilization candidate.
- Void, bound, or transformation-delay conditions remain visible and may require separate treatment.
- Without an attributed timing rule, record
no windowrather than turning structural symmetry into authority.
Source note
The two-sided comparison is a UAYA teaching convention for exposing the branches involved. No exact public locator used in this course establishes a universal combination-based timing order for clashed lines, so the page deliberately withholds dates and ranking unless an attributed source or lineage is added.
Next step
Continue with the received value-and-clash statement for a static line: Static-Line Value and Clash.