A moving target is already in flight. The timing question is usually not “what wakes it up?” It is “when does it land?”

Moving lines tend to resolve faster than quiet lines, unless the movement creates a delay.

So the first pass is simple: look for value or combination days. The second pass is stricter: check whether the line is bound, voided, broken, or delayed by the transformed branch.

Primary Value day

The day matching the moving line's branch can be the landing date.

Primary Combine day

The day that combines with the moving branch can also produce quick verification.

Context Same-day response

If the cast date already supports or combines with the moving line, the result can be immediate.

Inherited motion Dark Moving

If Act 5 classifies a static line as Dark Moving, time it like movement rather than quiet strength.

Fast does not mean simple

Clean movement Fast landing

If the line moves cleanly and the transformed branch is usable, near timing is normal.

Bound movement Wait for release

If movement creates or enters a combination bind, use bound timing first.

Delayed transformation Wait for restoration

If the line transforms into void or break, the effect cannot land until that state resolves.

Output pattern

Primary Next value or combine day

Use the closer clean candidate when both are available.

Backup The other clean candidate

Carry it as secondary if it is close and mechanically relevant.

Scale Usually near

Moving lines often resolve on day or hour scale when the question allows it.

Exception Delay overrides speed

Transformation delay, void, break, or bind outranks the general moving-line speed rule.

Trap

Do not assume every moving line is fast. Moving is a state, but it can be modified by what the line transforms into. The transformed state may be the real timing lock.

This is why moving-line timing belongs before transformation timing in the learning sequence, but after transformation timing in the actual decision stack when a delay appears.

For Dark Moving, carry the Act 5 rule choice forward. Under the strict rule, the day-clashed static line must also be seasonally strong enough to count as Dark Moving. Under the broader working rule, static plus day clash plus not Month-Broken may be enough. Once you classify it as Dark Moving, it follows the moving-line landing rule; if you do not, it remains a different timing problem.

Also distinguish outside combination from self-produced binding. A moving line meeting a combining day can land. A moving line transforming into a branch that binds it is delayed. Same word family, different timing posture.

Continue to Near vs Far