Every timing read begins by putting the target line into a state. The state tells you which timing rule to use.

When states stack, restore the most basic problem first. A void, broken, or bound line does not get timed as ordinary movement until that condition has been resolved.

Void Missing

The target is not fully funded inside the current ten-day cycle. It waits to be filled.

Bound Held

A combination has locked the target or its support path. It waits for a clash to release the bind.

Static Still

The target is not moving. If strong, it waits for a trigger. If weak, it may need rescue.

Moving In flight

The target is already acting. It usually lands quickly unless the transformation creates a delay.

The secondary states

Some patterns are not separate families. They are special versions of the four states.

Strong and quiet Static, but ready

The line has strength but no motion. It verifies when the calendar strikes it.

Clashed Static or moving, but unstable

The line is disturbed by clash. It waits for a stabilizing combination or support event.

Waiting frame A frame lacks one branch

The frame completes when the missing branch arrives.

Broken frame A frame member is disabled

The frame heals when the broken, void, or missing member is restored.

Transforming to void Moving into absence

The line moves, but its result cannot land until the void resolves.

Transforming to break Moving into damage

The line moves, but its result is delayed until the broken branch is restored.

Quick diagnostic

Ask first Is the target usable?

If it is void or broken, timing starts with restoration.

then
Ask second Is the target held?

If it is bound, timing starts with release.

then
Ask third Is the target moving?

If yes, time the landing. If no, time the trigger.

Trap

Do not treat a bound moving line as simply moving. If a moving line is held by combination, it is bound first. It cannot land until the bind breaks.

The same discipline applies to a moving line that transforms into void or break. Movement tells us something has started; the changed state tells us when the effect can arrive.

Void is also not just “very weak.” A weak line may need support. A void line needs filling. A Month-Broken line may need rescue or the month to change. These states can all look like weakness, but they do not resolve through the same calendar event.

Use this priority when the labels stack:

  1. Restore basic usability: void, Month Breaker, or Day Breaker.
  2. Release or stabilize: bound or clashed.
  3. Land or trigger: moving line or strong-and-quiet line.
  4. Refine with frames, support lines, and backups.

Continue to Void Timing