Most transformation dynamics stay inside one moving line: cause and effect.

Two patterns reach outward. The transformed branch can combine with the moving branch or another relevant branch. It can also clash with the moving branch or another relevant branch.

Transform to combine The line ties itself

The transformed branch creates a combination lock.

Transform to clash The line destabilizes itself

The transformed branch creates a clash or unstable result.

Transform to combine

The moving line produces a branch that combines with itself or with another important line.

Moving line Action begins

The line moves toward an outcome.

Transformed branch Finds a combination partner

The effect enters a harmony pair.

Result Bound until release

The matter may be delayed until a clash opens the combination.

The texture is not denial. It is action held in place.

Transform to clash

The moving line produces a branch that clashes with itself or with another important line.

Moving line Action begins

The line moves toward an outcome.

Transformed branch Creates a clash

The effect collides with the source or another relevant line.

Result Unstable landing

The matter may manifest but fail to settle.

The diagnostic question

After classifying the internal dynamic, ask:

Does the transformed branch combine or clash with any branch already active in the chart?

Include the moving branch itself. A line can bind itself through its own transformation.

These checks happen after the ordinary cause-effect read. First ask what the transformed line does to the moving line. Then ask whether the transformed branch reaches into the wider chart and creates a lock or collision there.

Do not classify every harmony pair or clash pair as self-transform. The transformed branch must actually bind or collide with the moving branch itself, or with an active relevant branch in the chart. If there is no operative partner, keep it as the internal 6.2 dynamic.

Source basis: Zengshan Buyi transformation-to-combination and transformation-to-clash cases. The point is operative binding or collision, not decorative pair-matching.

Common traps

Trap 1 Stopping at head-back generation.

A transformation can generate the source and still bind it.

Trap 2 Missing the chart-wide check.

Combination and clash require checking the transformed branch against the rest of the chart.

Trap 3 Assuming release is immediate.

A bind waits for clash; a clash may wait for combination or stabilization.

What this module establishes

Transformation can create a second-order interaction. Read the line internally, then check what the transformed branch does to the rest of the chart.

-> 6.4 Multiple Moving Lines